Path Finder: how to decide what you need

Deciding on Path Finder is not usually blocked by the feature list. It is blocked by the fact that there are two release lines under one name, that version numbers now follow the calendar year, and that payment comes in two shapes with different device counts attached. Read those three conditions first and most of the remaining questions answer themselves.

There are two release lines, and macOS picks one for you

The support documentation splits system requirements into two statements. Version 11.2 is compatible with macOS versions starting from 10.13 High Sierra. Version 26 is compatible with macOS versions starting from macOS Ventura 13 and up. Which of those two sentences describes the Mac in question determines everything that follows.

Hardware is not the deciding factor. Both Intel-based Macs and Apple Silicon M-series Macs are supported, and the app is stated to run natively on both. There is no line in the requirements that penalises one chip family, so the split is purely about the operating system version.

There is a third route for older hardware. The site carries a separate pointer for people on an old Mac who still want to run Path Finder 10. If a machine is pinned to an older macOS for reasons outside anyone's control, reading current-line pricing and feature pages is wasted effort from the start.

Do this check before anything else. Requirements read last invalidate every comparison made before them, and the version split here is unusually wide: roughly nine years of macOS releases separate the two supported floors.

The practical consequence of a split that wide is that search results and forum threads become unreliable sources. A screenshot, a menu path, or a complaint about a missing option may be describing either line, and the two are far enough apart that advice does not transfer cleanly between them. Before taking any description of the interface at face value, check which line it refers to. The same caution applies to reviews: a piece written against the older line may be accurate about that line and completely wrong about the current one.

A year-numbered version makes the upgrade rule matter more than the price

The current build is 26.1.8. With the leading number tracking the calendar year, what happens when the next year's release ships matters more to the three year total than any figure on the store page.

THIS VERSION IS A PAID UPGRADE! If your current Path Finder license is less than a year old, you can use the new version until it's been one year. Otherwise, you need to purchase an upgrade license. Source: store.cocoatech.io

Read plainly: a licence under a year old carries into the new release until that year is up. A licence past a year needs an upgrade purchase to move. The right to keep running what is installed and the right to receive the next release are tracked separately.

That structure makes purchase timing worth a moment's thought. Buying shortly before a new year's release arrives is very different from buying shortly after one. The update log is public, so the rough cadence of major releases can be read off it before committing.

There is a second cost attached to the large releases specifically. The 26.0 notes describe a visual and structural redesign across the whole application, and state that as a consequence of the redesign some settings and options were removed as obsolete and are not preserved after the update. A major year release can mean rebuilding a layout, not just paying for it.

Two payment shapes, counted differently

The product page currently lists $32.95 for a 1 Year License. A subscription is offered alongside it, and the site's purchasing section presents the choice as a subscription or a licence key.

The difference is not only the number. According to the support documentation, a licence key comes with 3 activations per licence, and extra activations cannot be purchased for the same licence. A subscription is tied to an email address rather than a key and includes 2 activations.

How the count works is documented as well. Activations are machine based, not account based, so two people sharing one Mac consume a single activation between them. The inverse is the common case: one person with a desktop, a laptop, and a work machine fills the key's three slots alone. A fourth machine means signing out on one that is no longer in use, from Path Finder then Registration, or buying a second licence.

Over a three year window the gap between three slots and two behaves differently than it looks. Three leaves room to keep an old machine registered during the weeks after a hardware change, while the new one is being set up. Two means the sign-out step lands in the middle of a migration. Pair the slot count with how often Macs get replaced rather than with how many are owned today.

Read the activation recovery steps before paying

Knowing what happens when activation goes wrong is part of judging a payment shape, not an afterthought once it does. The support documentation covers this case explicitly, and the steps reveal something useful about the design.

Three symptoms are listed: the app reports the licence as expired, the trial reports as expired despite a purchase, or a signed-in state fails to register as activated. The documented sequence is to open Path Finder then Registration and sign out, quit the app completely, open Keychain Access and search for the stored credential item, delete it, then relaunch and sign in again.

What that reveals is where the activation record lives. It is held in the Keychain, which means restoring a Mac from a backup, migrating to new hardware, or moving a Keychain between machines can leave the stored record and the server state out of step. On a machine that gets restored or migrated often, the odds of meeting this procedure go up, and the recovery is a handful of steps rather than a support ticket.

A second recovery path is documented for a different failure. When sidebar items vanish, toolbar icons disappear, or the layout resets on every launch, the fix is to quit and remove a defined set of files: a folder in Application Support, a preferences plist, a plist in LaunchAgents, a cache folder, and a saved application state folder. Reopening rebuilds them.

Both procedures are worth reading before purchase for the same reason. A tool whose failure modes are documented with named files and exact steps is one that can be recovered without waiting on anyone. A tool whose documentation stops at contact support has effectively moved that recovery time onto a queue. That difference belongs in the comparison alongside price.

The name on the statement is not the name on the app

One documented detail avoids an awkward moment later. A post on the company blog states that Distant Future is the parent company of Cocoatech, and that a charge appearing under Distant Future is the same company.

It sounds minor until an expense claim has to reconcile a software name against a billing entity that does not match. Anywhere purchases pass through approval or reimbursement, noting that pairing before buying removes a round trip.

Support routes are worth checking at the same time. The site points to email, to a Discord server where live help is available when the team is online, and to an assistant in the lower right corner of the page that visitors are asked to try before writing in. Volume purchases have a separate sales contact, and anyone buying several seats should use it rather than stacking individual purchases, since seat counting for bulk arrangements should not be assumed to match the three and two figures above.

The company's own blog also records a period when support broke down, with a backlog left by a departed support contact, followed by the hiring of a new team and an apology. If response time is a deciding factor, the current published routes are the ones to judge, not the historical ones.

Plan the 30 day trial as a single attempt

The trial runs 30 days and downloads directly from the site. One rule shapes how it should be spent: the support documentation states that reinstalling does not reset the trial, because the trial is tied to the Mac hardware rather than to the app. There is no second run.

Put permissions first. The documented fix for folders appearing empty, or files visible in the Finder but not in the app, is to open System Settings, go to Privacy and Security then Full Disk Access, switch the app off, wait five seconds, switch it back on, and relaunch. Whether that situation occurs at all depends on the machine, so it has to be observed rather than predicted.

Cloud folders come second. For iCloud Drive, Google Drive, OneDrive and Dropbox, the guidance is to confirm files are fully downloaded rather than online-only before judging display behaviour. On a Mac where most cloud content is placeholders, the experience differs sharply from one where it is not.

Module selection comes third. The documented remedies for heavy CPU or memory use are to disable folder size calculation, turn off unused modules, avoid previewing large media, and let indexing finish after an update. Test with folders of the size actually used day to day, not with a tidy sample.

Fourth, confirm that the layout persists. If the window opens small each time, or forgets dual pane, or fails to reopen the previous folder, the documented step is to arrange the preferred layout and then choose Window then Save As Default. Spending 30 days without knowing that command produces a distorted verdict on the whole app.

Check how often the translations get touched

For anyone not working in English, localisation belongs among the conditions rather than at the end of the feature list. The update log records that Japanese localisation was improved in 26.1.5, that all 20 currently supported languages were improved in 26.1.7, and that Simplified Chinese was completed in 26.1.8.

A daily-use tool is where partial translation costs the most. Menu items left in the original language add a beat to every lookup, and that beat repeats dozens of times a day. The number of languages on a feature page says little on its own. Scrolling back three or four releases in a changelog to see whether translations are being revised says considerably more.

The same test transfers to any competitor on the shortlist. Twenty languages untouched for three years and eight languages revised every release are not comparable claims, even though only the first number appears on a comparison chart.

What to change first

Answer three questions before looking at any feature: which release line does this Mac fall into, how old will the licence be when the next year's version ships, and do three activation slots or two cover the machines in use. Those answers pick the payment shape without further debate. If several tools still qualify, the deciding measure is not on any feature grid: count how many times in a day a path gets carried from a file window into a terminal window, and how often a question about a file's contents gets retyped somewhere else. The side by side sits at Compared with other file managers, payment shapes at Pricing, and what fits inside one window at Atriens.