Free alternatives to ForkLift worth trying

Searching for a free ForkLift alternative on a Mac usually starts the same way. The trial ran out, or a license from an older version stopped covering updates, and the question became whether $19.95 is worth paying again for something that mostly moves files around. That is a fair question. It is also the wrong first question, because ForkLift is not one tool. It is roughly five tools stapled together, and the free landscape covers some of those five very well and others not at all.

The useful move is to work out which of the five jobs actually gets used during a normal week, then find the free tool that covers that job properly. Replacing the whole application with one free download tends to fail, because nothing free covers the whole surface.

What the license is actually buying

ForkLift 4 is sold by BinaryNights at $19.95 for a single user with one year of updates, $34.95 for two years, $29.95 or $49.95 for a family license, and $69.95 or $119.95 for a small business license. The model is a perpetual license with a bounded update window. Once the update period ends, the last covered version keeps working indefinitely, but installing a newer build means buying again. A free trial is available before any of that.

What the money covers breaks down into distinct jobs:

• Dual pane local browsing, with keyboard driven navigation and remappable shortcuts
• Remote volumes mounted as if they were local disks, across SFTP, FTP, WebDAV, Amazon S3, Backblaze B2, Google Drive, OneDrive, Dropbox, Rackspace Cloudfiles, SMB, AFP, and NFS
• One way and two way synchronisation between folders, local or remote
• Archive browsing, file comparison, and Git status shown in the file list
• Saved workspaces, so a layout for one project can be recalled without rebuilding it

Most people who search for a free replacement only use two or three of those. Someone who ships to a web server every day lives in the remote half. Someone wrangling video assets on a local drive lives in the dual pane half and has never opened the connection manager. The free market splits along exactly that line, so knowing which half matters is what makes the rest of this decision easy.

The free options, and what each one drops

There is no single free application that matches the list above. There are several that match one column of it well.

Tool	Cost	Dual pane	Remote protocols built in	Terminal inside the app
Marta	Free download from marta.sh	Yes	No	Yes
Nimble Commander	Free, GPL-3.0, on the Mac App Store	Yes	FTP, SFTP, WebDAV	Yes
Commander One	Free core, Pro Pack $29.99	Yes	In the Pro Pack only	In the Pro Pack only
muCommander	Free, open source, Java	Yes	FTP, SFTP, SMB, WebDAV	No
Double Commander	Free, open source	Yes	Via plugins	No
Cyberduck	Free download, donation prompted	No	SFTP, FTP, WebDAV, S3, and more	No
Finder	Included with macOS	No	SMB, AFP, NFS, WebDAV, FTP	No

Marta is the closest thing to a native feeling free replacement for the local half. It is written for macOS specifically, it is keyboard driven, it ships five themes, it reads RAR, 7Z, XAR, TAR, ISO, CAB, and LZH archives while writing ZIP, and it exposes a Lua API for plugins. It also has a built-in terminal that keeps its working directory in step with the active pane, which is the single feature most people miss when they drop back to Finder.

Nimble Commander is open source under GPL-3.0 and free on the Mac App Store, with a terminal emulator and FTP, SFTP, and WebDAV support. The Mac App Store build runs sandboxed, which constrains some operations that the directly downloaded build can perform. That distinction matters for anyone who works across system directories.

Commander One gives away the dual pane core and puts the connection manager, cloud storage access, terminal emulator, and process viewer behind a $29.99 Pro Pack for a single Mac, or $99.99 for five. At that point the arithmetic against a $19.95 ForkLift license is worth doing honestly rather than by reflex.

Splitting the job rather than replacing the application

The pairing that works for most people is one free local browser plus one free transfer client. Marta or Nimble Commander handles the folders. Cyberduck or FileZilla handles the server. Both halves are free, both are actively maintained, and each does its own job at least as well as the corresponding half of a paid suite.

What breaks in that arrangement is the thing ForkLift is genuinely good at: treating a remote server as a pane, so a file can be dragged from local to remote in one gesture without a separate window and a separate mental model. Splitting the job means that gesture becomes three steps. For someone who deploys twice a month, three steps is nothing. For someone who deploys twenty times a day, three steps is the whole reason the license exists.

The honest test is to count. Over one working week, note every time a file crosses the boundary between a local folder and a remote server. If the number is under ten, the free pairing is fine. If it is over fifty, a paid tool that collapses the boundary is not a luxury, and the comparison worth reading is not free against paid but which paid tool collapses it best. A side by side of the current options is laid out on the comparison page.

Two smaller things break in the split arrangement as well, and both tend to be discovered late. Synchronisation rules do not survive the split. A folder pair that ForkLift kept in step on demand becomes a manual comparison, or a shell script, or a habit that eventually lapses. And credentials end up stored in two places, since the local browser and the transfer client each keep their own connection list. Changing an SSH key then means editing it twice, and forgetting the second one produces a failure that looks like a server problem rather than a configuration problem.

Neither is fatal. Both are worth knowing before the switch rather than three weeks after it.

Checking whether a free project is still alive

Free tools fail quietly. They do not send a cancellation notice. They simply stop shipping builds, and the failure only becomes visible on the morning a macOS update lands and the app refuses to open.

Four checks take about five minutes each and catch almost every case before it costs anything.

Look at the date of the most recent release, not the copyright line in the footer. A file manager that has not shipped anything in eighteen months is unlikely to be ready for the next macOS release. Look at whether the release notes mention the current macOS version by name. Compatibility work for a new system release is specific and visible, so a changelog that names the latest system is a strong signal that someone is still testing against it.

Check whether the build is notarised by Apple. An unnotarised application still opens, but it takes extra steps every time Gatekeeper is involved, and it suggests the developer has drifted away from the distribution process. For an open source project, look at the issue tracker rather than the download page. A tracker with recent replies from the maintainer means the project is attended. A tracker with a hundred open issues and no comment in a year means the download works today and nothing more should be assumed.

None of this makes a free tool a bad choice. It makes an unmaintained free tool a bad choice, and the two are easy to tell apart with a few minutes of looking.

Where free stops being free

Three costs hide inside the word free, and none of them appear on a download page.

The first is maintenance risk. macOS ships a major release every autumn, and file managers sit close enough to the system that each release breaks something. A funded project fixes that within weeks. A single maintainer working evenings may take months, or may stop. Before committing to any free tool, look at the date on its most recent release, not the date on its homepage.

The second is runtime friction. muCommander runs on Java, which means a Java runtime has to be present and kept current. That is trivial for a developer and genuinely annoying for anyone else.

The third is the cost of the switch itself. Muscle memory for a file manager takes about two weeks to rebuild. Two weeks of slightly slower work, priced at any reasonable hourly rate, exceeds $19.95 by a wide margin. This is not an argument for paying. It is an argument for switching once, deliberately, rather than three times while sampling.

The terminal is often the real requirement

A large share of ForkLift alternative searches are not really about ForkLift. They come from people who spend the day moving between a folder window and a shell prompt and have started to notice how much of the day that movement consumes. The file manager is simply where the irritation surfaces.

If that is the actual shape of the problem, the feature to filter on is a terminal that lives inside the file manager and follows the current directory. Marta has it. Nimble Commander has it. Commander One puts it behind the Pro Pack. Finder does not have it, though macOS can add a New Terminal at Folder service through the Keyboard settings, which covers the simplest version of the need.

The next layer past that is a window where the folder view, the shell, and an AI assistant all read the same working directory, so that describing a task in words and watching it run against the files in front of you happens in one place. That is a different category from a classic dual pane manager, and it is worth understanding before settling on a free tool that solves only the first half. The shape of it is described under what it does, and the way work continues from a phone is covered in continuing from iPhone and iPad.

A two week test that actually settles it

Guessing at this from feature lists does not work. Running it does.

Pick one free candidate, not three. Install it, set it as the default handler for folders if the tool supports that, and use nothing else for ten working days. Keep a note, even a rough one, of every moment the tool forced a detour: a protocol it could not speak, a permission dialog it could not clear, an archive format it refused, a keyboard shortcut that did not exist.

At the end of the ten days, that note is the answer. A short list means the free tool has covered the real workload and the license was never needed. A long list, particularly one dominated by the same complaint appearing daily, means the cost of the workaround is now measurable, and comparing that number against a one time license price is a two minute calculation rather than a matter of taste. Current pricing across the options sits on the pricing page.

What to change first

Stop looking for one free application that replaces all of ForkLift, because it does not exist. Decide instead whether the local half or the remote half is where the day actually goes, take the strongest free tool for that half, and give it ten uninterrupted working days. If the note from those ten days keeps circling back to switching between folders, a shell, and an assistant, the tool to look at next is Atriens, which puts those three in one window.