ForkLift: how to decide what you need

The difficulty in choosing a ForkLift license is not the software. It is the store page, where six tiers sit across two axes at once, seat count and update length, and nothing on the page tells you which axis to settle first. Approached from the price list, every option looks defensible. Approached from three facts about the machine it will run on, the list usually collapses to a single row before the prices are even read. Those three facts are the macOS version in use, the number of Macs involved, and whether remote storage is part of the work.

Fix three things before looking at prices

Start with the operating system, because it controls which builds can be installed at all, and that constraint is independent of money.

ForkLift 4.4 and later require macOS Sonoma (macOS 14.6) or later. Previous ForkLift 4 versions require macOS Monterey (macOS 12.4) or later. Source: binarynights.com

The floor moved partway through a single major version. Version 4.4, released on 26 August 2025, raised the requirement from Monterey 12.4 to Sonoma 14.6. A Mac still on Monterey can therefore install nothing past the 4.3 series. There is a matching constraint at the other end: builds earlier than 4.3.4 do not run on macOS Tahoe. Put those together and a license meant to cover both a Monterey machine and a Tahoe machine lands in a narrow band between 4.3.4 and 4.3.5. Working this out after purchase is an unpleasant surprise, and it takes two minutes to check beforehand.

Second, count the Macs, including any that will exist within a year. Seat count is the axis that gets expensive to correct later, because moving up a tier means buying again rather than paying a difference.

Third, decide whether remote storage is genuinely part of the job. If it is not, a large share of what the price covers will sit unused. If it is, write down the destinations. SMB and WebDAV are already reachable from the Finder, while object storage such as Amazon S3, Backblaze B2 or Rackspace Cloudfiles is not, and that distinction is what makes the purchase worth making or not.

Update length follows from how fast macOS gets upgraded

The license grants permanent use of whatever build it covers, plus the right to install newer builds for a fixed window. The store offers that window in one year and two year lengths, and nothing else about the two options differs.

The right length follows from release cadence on both sides. ForkLift 4.0 shipped on 5 September 2023, and version 4.7.5 shipped on 1 September 2026, with 49 releases in between. That averages one release every 22 days, and the pace through 2026 has been close to monthly. Those releases are where macOS compatibility arrives: 4.3.4 was the build that added Tahoe support during the beta period, which is exactly the kind of release an expired window locks you out of.

So the reasoning runs like this. Installing each new macOS in the autumn means crossing at least one system release inside any update window, which argues for the longer option or for a bundle. Staying on a fixed macOS for years, which is common where a toolchain has to stay stable, makes the one year option the cheapest outcome, because expiry never produces a consequence.

One adjustment applies to returning customers. Entering an existing license key at checkout adds 100 days of eligibility on top of the chosen term. Buyers who got ForkLift 2 through the Mac App Store have no key to enter, and the support page describes contacting the vendor before purchasing to claim the same bonus. Students, teachers and lecturers can request an educational discount by writing to support from an institutional address or attaching proof.

The seat tiers, laid out

Tier Coverage One year of updates Two years of updates
Single user Personal use on your Mac 19.95 dollars 34.95 dollars
Family Every Mac in the household 29.95 dollars 49.95 dollars
Small Business Up to five office Macs 69.95 dollars 119.95 dollars

Two details in that table do the real work. The family tier is written as a household rather than a seat count, and it costs 10 dollars more than single user on the one year term. A second Mac at home therefore makes it cheaper per machine immediately. The small business tier, by contrast, states a hard limit of five, so a sixth machine means another purchase rather than a top up.

The update axis rewards the same arithmetic. On the single user tier, the gap between one and two years is 15 dollars. Buying the one year tier twice comes to 39.90 dollars against 34.95 for two years bought once, so repeat buyers pay slightly more, though the 100 day bonus on the second purchase narrows the gap. Pick two years when long term use is already settled, and one year when the decision is genuinely open twelve months out.

Where the bundle crosses over

The vendor support page confirms ForkLift 4 is available through Setapp, whose Mac plan is listed at 14.99 dollars a month billed monthly, before tax. Measured against the single application alone, 19.95 dollars is roughly one and a third months of that plan and 34.95 dollars is roughly two and a third.

Stated that way the direct purchase looks unanswerable, but the two products are not the same product. A subscription keeps the current build permanently available, so the compatibility problem described above never arrives. A direct license ends the payments and reopens the question each time the window closes and macOS moves forward.

A workable rule: if two or more of the other applications in the bundle are already in use, or plausibly will be, the bundle reads better. If this is the only target and macOS is being held steady, direct is smaller. When it is genuinely unclear, buy directly first and revisit at expiry, since owning a license does not block joining a bundle later.

Coming from the previous generation

Anyone already running ForkLift 3 has a different question to answer before price, because some features carry the same name across generations while working differently underneath.

Saved connections import through the first run window. Skipping that step is recoverable: the documented route is disabling iCloud favourite sync, quitting, optionally deleting the relevant folder under ~/Library/Group Containers/, running defaults delete com.binarynights.ForkLift.plist setupDone in the Terminal, and relaunching to take the import offer again.

Two things do not come across at all. Multi rename presets and saved sync configurations cannot be imported, because those features are built differently in the two versions. The sync filter in particular changed to an exclude filter, so any elaborate include based rule set gets rewritten by hand. The volume of that rewriting, rather than the price, is usually what decides when to move.

There is no forced cutover either. Both versions can be installed on the same Mac, and the documentation covers renaming one of them so the two are distinguishable. The one caution is to avoid an application deleter when removing one copy, since shared support files get taken with it and the surviving copy loses its settings. Drag the app to the Trash instead.

Behaviour changes arrive in point releases, so read them

One more input belongs in the decision, and it is easy to miss because it looks like maintenance. At roughly one release every 22 days, this is an application that changes underneath a working routine, and some of those changes are deliberate behaviour changes rather than fixes.

Two examples from the published release notes make the point. Version 4.7.5 changed what happens when a transfer source contains items with conflicting names: the transfer now refuses to start, specifically to stop files being overwritten unintentionally. That is a safety improvement, and it is also a workflow that behaves differently from the one someone may have relied on for two years. Version 4.2 added a setting to open remote connections in a fixed pane rather than in whichever pane is active, which changes where a server lands after a click.

Neither change is hidden. Both are written up in the version history. The practical consequence for a purchase decision is that update eligibility is not only about compatibility with new macOS releases. It is also about whether behaviour changes are wanted at all. Someone running a stable, documented routine on a fixed macOS has a genuine argument for buying the shorter term, staying on a known build, and treating the release stream as optional. Someone whose work depends on keeping pace with new system releases has the opposite argument. Both are defensible, and the store page cannot tell which one applies.

Decide what the trial is testing before starting it

A trial mode is available from the registration window without a key. Used without a plan, the feature count absorbs the time and the things that actually matter go unchecked. Write the list first.

  • Grant Full Disk Access before forming any judgement. Without it, the Desktop, Downloads and Documents folders and attached drives are unreachable and drag and drop is limited, which is easy to mistake for the app being broken.
  • Connect to the actual server, with the actual authentication method. A protocol appearing on a list is not the same as a working connection in one particular environment.
  • Run a comparison against a folder of realistic size. The vendor describes analysis as up to 20 times faster than in the previous generation, and the felt difference depends entirely on item count.
  • Confirm the terminal in use is selectable. The settings offer Terminal, iTerm, Hyper, Kitty, Warp and Ghostty.
  • Switch the interface to the language that will be used daily. Twelve are available: English, German, Hungarian, French, Spanish, Portuguese, Polish, Ukrainian, Italian, Czech, Japanese and Chinese.

Those five, run inside the trial period, catch nearly everything that would otherwise surface after payment. Themes and colour schemes can wait, and so can the archive browsing and application removal features, both of which behave predictably enough that nobody has ever regretted a purchase over them. The items above are the ones that vary by machine, by network and by account, which is exactly why a trial exists.

What to change first

Write down the macOS version, the Mac count and the list of servers before opening the store page. If the list still has more than two rows on it afterwards, one of those three facts has not actually been settled. And if the real complaint turns out to be the number of windows open at once rather than any tier on the page, folders, a terminal and an assistant in one window is the thing to compare against instead, with Atriens setting out how that is priced.

Frequently asked questions

One year or two years of updates?

Two years suits anyone who installs each new macOS release soon after it ships, since the update window will cross a system release. One year suits a machine held on a fixed macOS, where expiry never causes a problem. The gap is 15 dollars on the single user tier, and buying one year twice costs slightly more than two years once, offset a little by the 100 day returning customer bonus.

Will it run on a Mac still on Monterey?

The 4.3 series will. Version 4.4 and later require macOS Sonoma 14.6, so they cannot be installed on Monterey. Note the opposite constraint too: builds earlier than 4.3.4 do not run on macOS Tahoe, so covering an old Mac and a new one with the same license leaves only a narrow band of usable builds.

How many machines does the family tier cover?

The store describes it as every Mac in the household rather than a fixed number. Since it costs 10 dollars more than single user on the one year term, a second Mac at home already makes it cheaper per machine. Office use has its own tier with an explicit ceiling of five machines.

What should be checked first during the trial?

Full Disk Access. Without it the Desktop, Downloads and Documents folders and any attached drives stay unreachable and drag and drop behaves oddly, so an evaluation made in that state is measuring the permission rather than the application. Grant it, then connect to a real server with real credentials.

Back to all posts