ForkLift alternatives: what you can drop

Most searches for a ForkLift replacement do not begin with a missing feature. They begin on the morning after a macOS upgrade, when the app either refuses to launch or announces that the license key no longer covers this version. That is a licensing condition, not a fault, and it sends people looking for software when the actual question is about how the software is held. Before comparing anything, it helps to take the application apart, because a single window is quietly doing seven unrelated jobs, and only two or three of them are usually being used.

The trigger is the update window, not a missing feature

A ForkLift license sits between a one time purchase and a subscription. Whatever version the license covers stays usable indefinitely. The right to install newer builds runs out after the period chosen at checkout, and any build released after that date runs in trial mode.

With the ForkLift lifetime license, you get free software updates for one or two years, depending on your choice. Once that period ends, you can keep using the latest version of ForkLift covered by your license indefinitely. Source: binarynights.com

That condition only bites when the operating system moves. Builds earlier than 4.3.4 do not run on macOS Tahoe, which the vendor attributes to a system level change from Apple, and 4.3.4 shipped on 24 June 2025. Anyone whose update eligibility ended before that date reaches a fork in the road the moment Tahoe is installed: buy a fresh license, or stay on the older macOS. There is a floor as well as a ceiling. ForkLift 4.4 and later require macOS Sonoma 14.6, so a Mac still on Monterey can only run the 4.3 series.

If that is the situation, the thing to shop for is not a different application. It is a different payment shape. Keeping those two questions apart saves a week of comparing feature grids that were never the problem.

Seven jobs living in one window

Read the published feature list and the work splits into seven categories that have almost nothing in common with each other.

• Reaching remote storage. Twelve protocols are supported: SFTP, FTP, WebDAV, Amazon S3, Backblaze B2, Google Drive, OneDrive, Dropbox, Rackspace Cloudfiles, SMB, AFP and NFS, with several servers connected at once and drag and drop between them.
• Reconciling two locations. Two folders, local or remote, are compared into matching, modified, new and deleted, then synchronised one way or both ways.
• Renaming in bulk, with the rule set saved as a preset and reapplied later.
• Browsing archives as though they were ordinary folders, including search and filtering, on remote servers as well as local disks.
• Removing applications along with the files they leave behind.
• Showing version control state per file, with add, commit, push and pull available.
• Carrying position across. The app can be set as the default file viewer, and the current local path can be opened in Terminal, iTerm, Hyper, Kitty, Warp or Ghostty.

These seven split people cleanly. For someone who never touches a server, the first item is dead weight. For someone who uploads every day, the other six are packaging. So the first useful exercise is counting: of the seven, how many get used at least once a week?

What each job can move to

Once counted, hand the jobs out individually. Trying to find one application that absorbs all seven is what makes the search feel impossible.

Job in the bundle	Where it can go	What that gains	What it costs
Reaching remote storage	Connect to Server in the Finder, or a dedicated transfer client	Nothing extra to buy for SMB and WebDAV	Object storage such as S3 or B2 is not reachable from the Finder
Reconciling two locations	rsync behind a shell alias	Conditions are explicit and can be scheduled	The step where differences are reviewed by eye disappears
Renaming in bulk	Finder rename, or a shell loop	Numbering and substitution are already built in	No saved preset to recall next month
Browsing archives	Expand, then open	Nothing to install	Everything unpacks to read one file
Removing applications	Delete by hand	The leftover locations become known rather than assumed	The list has to be assembled every time
Version control state	git on the command line, or the editor	Stops duplicating what the editor already shows	The file list and the history sit in different windows
Carrying position across	Retype the path	One fewer dependency	A path is typed for every single operation

Three of those hand off without pain: archives, application removal and version control state. Each has a standard replacement, or belongs to a tool that was already open. The other four hurt for one shared reason. The replacement lives in a different window, so every operation now includes a trip between windows, and the number of trips scales with the number of files.

Buying it outright against renting it in a bundle

Bought directly, the listed prices are 19.95 dollars for personal use with one year of updates and 34.95 dollars with two years. A household tier covers every Mac in the home at 29.95 and 49.95 dollars. A small business tier covers up to five office Macs at 69.95 and 119.95 dollars. An existing license key entered at checkout adds 100 days of update eligibility. Students, teachers and lecturers can apply for an educational discount by writing to support with proof.

The other shape is a bundle. The vendor support page confirms that ForkLift 4 is available through Setapp, whose Mac plan is listed at 14.99 dollars a month billed monthly, before tax. These two are not comparable on total spend alone. A bundle keeps the newest build permanently available, so an operating system upgrade never produces the license message described above. A direct purchase costs less in absolute terms and then reopens the question every time the update window closes and macOS moves on.

The deciding variables are how quickly new macOS releases get installed and how long the Mac is kept. Upgrading every autumn means crossing at least one system release during the update period, which argues for the longer term or the bundle. Staying on the same macOS for years makes a single one year license the cheapest outcome by a wide margin, because the expiry never causes a problem.

What travels with you and what does not

If a move is going ahead, the accumulated configuration matters more than the feature list. Saved connections live in one file at ~/Library/Application Support/ForkLift/Favorites/Favorites.json, which is plain text, so hostnames and paths can be read straight out of it. Passwords are not in that file. They sit in the Keychain, which means a migration has two separate stages: exporting the list, then re entering credentials one connection at a time.

Two things do not travel at all. Multi rename presets and saved sync configurations cannot be imported between ForkLift 3 and ForkLift 4, because the vendor states those features work differently across the two versions. Data that will not move between generations of the same product is unlikely to move to a different product either, so assume those rules get rewritten by hand. If the rule set is elaborate enough that rewriting it is the expensive part, that is the honest reason to stay.

Nothing forces a clean break, either. ForkLift 3 and ForkLift 4 are documented as installable side by side, which is the same pattern worth using with any candidate: install it, point the default file viewer at it for a week, and switch back if it does not hold. One caution from the vendor applies when removing one of two installed copies. Do not use an application deleter for that, because shared support files get taken with it and the remaining copy loses its settings. Dragging the app to the Trash is the safe route.

The cost of switching is mostly not the purchase price

Whatever the replacement turns out to be, the spend is the small part. Three other costs land in the first week and none of them appear on a comparison page.

The first is permissions. Any file manager that reaches the Desktop, Downloads and Documents folders, or an attached drive, needs Full Disk Access granted before it behaves normally. Granting it is a minute of work, but evaluating a candidate before granting it produces a false verdict, since folders read as empty and drag and drop misbehaves. That single step accounts for a large share of the reports that a replacement is broken.

The second is credentials. Connection passwords are held in the Keychain rather than in any exportable configuration file, so every server gets its password typed again in the new application. Twenty saved connections is most of a morning. This is the cost that most often stops a migration halfway, leaving two file managers installed and neither one authoritative.

The third is muscle memory, and it is the one that gets underestimated. ForkLift documents keyboard control over every operation with customisable shortcuts, plus workspaces that store layouts of open tabs and locations. Anyone who has built those up has encoded part of a daily routine into one application's key map. A replacement with a different key map is slower for several weeks regardless of how its feature list compares, and the honest way to measure that is to switch the default file viewer for a full working week rather than trying the candidate for an hour.

Checking that the product itself has not moved

Price is only one of four things worth verifying before switching either direction. The others are whether the product has been discontinued, whether new sales have stopped, and whether ownership has changed.

On the published evidence, none of those have happened here. Version history shows ForkLift 4.0 released on 5 September 2023, with 49 releases up to 4.7.5 on 1 September 2026, an average of one release every 22 days, and roughly monthly through 2026. The developer is still listed as BinaryNights LLC, with no notice of a transfer. ForkLift 3 remains downloadable from the support page. What has changed across generations is the payment shape: ForkLift 2 was sold through the Mac App Store, while the current direct sale carries the update period described above. Anyone working from a remembered price is working from the wrong generation.

What to change first

Count how many of the seven jobs get used weekly before opening any download page. Two or fewer, and the standard tools plus a couple of shell aliases will cover it. Four or more, and consolidating into one window beats splitting the work across four. If the count is high because the day is spent moving between a file list, a terminal and somewhere to write the rules down, that is a window problem rather than a feature problem, and a file manager with folders, a terminal and an assistant in the same window removes the trips; Atriens sets out how that arrangement differs from what is on the list above.