ForkLift: what it does and where it breaks down

ForkLift is a dual pane file manager and file transfer client for macOS, made by BinaryNights. Version 4.7.5 shipped on September 1, 2026, and the product has had roughly one release every two or three weeks through 2026. That much is easy to establish. What is harder to find, and what actually decides whether the app fits, is the list of places where it stops.

Most write-ups treat a file manager as a bag of features and count them. That framing is useless for deciding anything, because nobody adopts a file manager for its feature count. People adopt one because a specific part of the day is slow, and they abandon one because a different part of the day got slower. What follows separates the two.

The shape of the app: two panes and a transfer queue

The window is built around two file panes sitting side by side, with a sidebar on the left holding devices, connections and favorites, and a preview pane on the right. The preview pane is not only for previews. It has three modes: an info window showing details of the selected item, an activity view showing copies and deletes and compressions in progress, and a log view showing what has already happened.

Above the panes sits a path bar with a status line reporting the number and size of selected items plus remaining free space, and above that a tab bar. Panes can be arranged vertically or horizontally, or collapsed to one. Each pane can hold list, column or icon view independently.

The two pane layout is a means, not a goal. Its purpose is that the source and the destination of an operation are both visible at the same time, so copying, moving, comparing and syncing stop being a sequence of window switches. That is the whole argument for the design, and it is either worth something on a given day or it is not.

The transfer side is where the app separates from a plain file browser. It connects to SFTP, FTP, FTP TLS, WebDAV, WebDAV HTTPS, Amazon S3, Google Drive, Backblaze B2, Microsoft OneDrive, Rackspace Cloud Files, Dropbox, SMB, AFP, NFS and VNC. Multiple servers can be connected at once, and a drag between two panes can move data directly between two remote hosts rather than routing it through a local folder by hand.

The feature set, grouped by the job it replaces

Counting features says nothing. Mapping them to the tool they displace says more.

The job	What the app provides	What it replaces
Batch renaming	Multi Rename with case rules, regex replace, insert at position, dates, counters, file metadata	A rename script or a separate rename utility
Folder comparison	Sync window with one way and two way modes, orphan deletion, exclude filter	rsync invocations, or a dedicated sync app
Uninstalling apps	App Deleter that collects preference files and residual data	A separate uninstaller
Archive handling	Browse local and remote archives as folders, with Quick Look and filtering inside them	Expand, look, delete the expanded copy
Version control status	Git file status in the pane, plus add, commit, push and pull	Switching to a Git client for a one line commit
Repeated layouts	Workspaces that save tab sets and locations	Reopening the same four folders every morning

Two of these are worth a closer look because they changed recently. Multi Rename gained metadata support in version 4.7.1, released June 30, 2026. It can read fields stored inside the file and use them in the new name: title, content creation date, dimensions, device model, original date, F number, exposure time, focal length, ISO speed, authors, album, track number and year recorded. That turns a folder of camera output into dated, readable names without a script. A rename setup can be saved as a sidebar favorite, and files dragged onto that favorite are renamed with it.

The Sync window saves its configuration the same way, as a favorite in the sidebar that runs the comparison again on click. Options include sync direction, whether to descend into subfolders, whether to include hidden items, whether to delete files in the target that no longer exist in the source, and a time offset correction for locations whose clocks disagree.

Two search engines, and the trade they represent

The app ships with two separate search mechanisms, and the difference is not cosmetic.

The built in search walks files one by one inside the active pane's location. It is slower on a large tree, and it works on remote connections, because it does not depend on anything the local system indexed.

Spotlight search uses the metadata the system already maintains. It returns results almost immediately and it can match on file contents rather than names alone. It only works locally.

The practical consequence: content search is a local privilege. On an SFTP server or an S3 bucket, only name based matching is available, and it costs a directory walk. Anyone whose main pain is finding a file by something written inside it, on a remote volume, should test that specific case before deciding.

Where the terminal stops

This is the boundary that surprises people, so it is worth stating precisely.

The app has an Open in Terminal command. It opens a window in Terminal, iTerm, Hyper, Kitty, Warp or Ghostty at the current local path. That is a handoff to a separate application, not a shell inside the file window. The file pane and the shell remain two windows with two focus states.

There is a second mechanism that goes further. Under Settings, a Tools section accepts zsh scripts. A tool can be run from the Commands menu, from the right click context menu, or, since version 4.6 released March 31, 2026, from a button in the toolbar, with a chosen icon. Version 4.7.1 added the ability for a tool to inherit the $PATH environment variable from the shell, which is what makes tools that call Homebrew binaries work without hard coded paths.

Tools cover the repeatable case well. What they do not cover is the exploratory case, where the next command depends on what the last one printed. For that, the shell has to be visible, and the app's answer is to open it elsewhere. Anyone whose day alternates between looking at a folder and typing a command against it should count how many times that handoff happens before deciding whether it matters. A file manager with a built in terminal solves a different shape of problem than a file manager that launches one, and neither is a defect.

The same boundary applies to language model assistance. The published feature list, the manual and the 2026 release notes describe no such capability. That is a statement about scope, not about quality.

Conflict handling, and a change worth knowing about

Copying into a folder that already holds a file of the same name is the operation where file managers quietly differ, and where data is lost when they get it wrong.

On a collision, the app offers Replace, Replace Older, Keep Both, Skip and Stop. Replace Older compares modification dates and keeps the newer file, which is the option people reach for when merging two half synced copies of the same folder. For directories there is a sixth choice, Merge, which combines the contents and raises a fresh conflict prompt for any colliding items inside.

A less obvious case changed in 2026. If several files with the same name are selected from different places at once, for example by expanding multiple folders or by selecting across search results, the collision is not between source and target. It is among the sources themselves, and the transfer order cannot be known in advance. Version 4.7.4, released August 18, 2026, treated that as a conflict prompt. Version 4.7.5, on September 1, changed the behaviour again: the transfer now refuses to start and warns instead.

The vendor's stated reasoning is that a prompt cannot be answered reliably in that situation, because it is not clear which file would end up overwriting which, and the overwritten copy cannot be recovered from inside the app. The release notes add that other file managers checked during the investigation generally transfer one of the colliding files without saying anything.

That detail is worth carrying into any evaluation, whichever app is chosen. Selecting across expanded folders or search results is exactly the habit a person with a messy Downloads folder develops, and it is the habit that puts files at risk. Test a multi source selection with duplicate names before trusting any file manager with a cleanup pass.

The permission and version floor that decide whether it runs at all

Two gates come before any feature.

The first is Full Disk Access. The manual is explicit about the consequence of skipping it:

Full Disk Access is essential for unlocking ForkLift's full potential. Without it, you won't be able to access attached drives, your Desktop, Downloads, or Documents folders, and you will experience limitations in drag-and-drop operations, among other things. Source: binarynights.com

Downloads and Desktop are precisely the folders a person with a file backlog needs first. A trial run that skips the permission prompt will look broken for reasons that have nothing to do with the app.

The second gate is the macOS version. Versions 4.4 and later require macOS 14.6 Sonoma or later. Earlier 4.x versions require macOS 12.4 Monterey. Version 4.3.4 and later are compatible with macOS 26 Tahoe, and earlier builds are not, because of a system change Apple introduced. Anyone still on an older macOS should check which build their machine can run before evaluating anything else.

What does not carry across from version 3

Version 3 and version 4 can be installed side by side and run at the same time. If both live in the Applications folder, the Finder will ask about the name collision, and keeping both means renaming one for clarity.

The import path is narrower than it looks. Favorites transfer, but the offer appears in the welcome window on first launch, and dismissing it is easy. Recovering from that requires disabling iCloud favorite sync, quitting the app, deleting its iCloud data, removing the group container folder, and running defaults delete com.binarynights.ForkLift.plist setupDone in a terminal to make the welcome window appear again.

Multi Rename presets and sync favorites do not transfer at all. The vendor states that these features work differently between the two versions. Anyone with years of accumulated rename rules should plan to rebuild them by hand.

One more trap: the App Deleter should not be used to remove one of the two versions. It tends to collect support files belonging to both, which costs the settings and favorites of the copy that was meant to stay. Dragging the unwanted version to the Trash is the documented method.

What to check before committing

Pick the three operations that actually cost time this week. Run each one in a trial build, with Full Disk Access granted, on the real volumes involved rather than a test folder. If one of those three is content search on a remote host, or a loop between reading a folder and typing a command against it, test that case first, because those are the two places where this app hands the work back.

If the answer is that the folder and the shell need to be in the same window rather than next to each other, that is a different category of tool, and the Compared with other file managers page of Atriens lays out where the line falls.