ForkLift not working: what to check, in order

This page is about ForkLift, the dual pane file manager and file transfer app for macOS made by BinaryNights, not the warehouse vehicle. When ForkLift is not working, the symptom rarely points at the cause. The app opens in trial mode, a folder looks empty, a cloud connection fails, a new file does not appear. Each of those can come from a license that does not cover the installed build, a build that does not match the installed macOS, a missing privacy permission, or a stale state inside the app. Checking those in a fixed order is faster than changing settings at random, because two of the four cannot be seen from ForkLift's own settings at all.

Every step below is based on BinaryNights' support page, Quick Start Guide and store, all checked on October 9, 2026. The current release at that date was ForkLift 4.7.6, published September 29, 2026.

Step 1: Rule out a license date before anything else

The most common "ForkLift stopped working" report is not a fault. ForkLift sells a lifetime license with a fixed period of free updates, one or two years depending on the option bought. The vendor describes it as a hybrid between a one-time purchase and a subscription. Builds released during the update period keep working indefinitely. Builds released after it run in trial mode.

The message that shows this state is "Your license key is not valid for this version of ForkLift". It usually appears right after an automatic update installed a newer build.

To check:

1. Open ForkLift and choose ForkLift > About ForkLift.
2. Read the update eligibility date shown under the name and license type.
3. Compare it with the release date of the installed version on the version history page.

If the installed build is newer than the eligibility date, there are two ways out, both listed in the vendor's FAQ:

• Go back to a covered build. Download the last version released before the eligibility date from the downloads page, and move it into the Applications folder in place of the current one.
• Buy a new license. Entering the old key in the store adds an upgrade bonus of 100 extra days of updates on top of the new license.

Prices on the store page on October 9, 2026:

License	1 year of updates	2 years of updates
Single user	$19.95	$34.95
Family (all Macs in a household)	$29.95	$49.95
Small Business (up to 5 Macs)	$69.95	$119.95

ForkLift 4 is also available through Setapp. Moving to a new Mac needs no deactivation step: install ForkLift on the new machine and enter the same key.

Step 2: Match the build to the macOS version

The second cause is a version mismatch between ForkLift and macOS. The vendor's requirements, as stated on the support page:

• ForkLift 4.4 and later require macOS Sonoma 14.6 or later.
• Earlier ForkLift 4 versions require macOS Monterey 12.4 or later.
• Only ForkLift 4.3.4 and later are compatible with macOS Tahoe (macOS 26). Earlier builds do not work on Tahoe because of a system change Apple introduced.

This creates an awkward combination with Step 1. A Mac upgraded to macOS 26 or later needs ForkLift 4.3.4 or newer. If the license's update period ended before 4.3.4 was released, the only version the license covers will not run on that Mac. The vendor's answer is a new license, with the upgrade bonus applied.

Recent releases also contain fixes specific to the newest macOS. The 4.7.6 notes list two fixes for macOS 27 Golden Gate: dragging items from a remote location out of Column View, and a sidebar that grew wider after every restart. If either of those symptoms appears on macOS 27, the first check is whether 4.7.6 or later is installed and covered.

Step 3: Check Full Disk Access and folder permissions

If ForkLift opens normally but the Desktop, Documents or Downloads folder looks empty, an external drive does not appear, or drag and drop behaves inconsistently, the cause is almost always macOS privacy permissions.

The Quick Start Guide is direct about this: without Full Disk Access, ForkLift cannot reach attached drives or the Desktop, Downloads and Documents folders, and drag and drop is limited. The prompt appears on first launch. If it was dismissed, it has to be granted manually.

1. Open System Settings and click Privacy & Security in the sidebar.
2. Open Full Disk Access and turn ForkLift on. If it is not in the list, add it with the add button.
3. Quit and reopen ForkLift.

Apple's guide to controlling access to files and folders explains the related Files and Folders list under the same Privacy & Security pane, where access to Desktop, Downloads and Documents is granted per app.

A related prompt confuses many people: the helper tool. Some actions, such as creating an item in the Users directory, need administrator rights. ForkLift asks to install a small helper tool the first time, then asks for an administrator password each time such an action runs. This is how Apple requires elevated privileges to be handled, so the password prompt is expected and not a sign of malware.

Step 4: Clear quarantine on a moved or copied app

Before downloaded software opens for the first time, macOS checks its Developer ID signature and notarization and asks for approval. Apple describes this in its article on Gatekeeper. According to the vendor's FAQ, when an app is first started from somewhere other than the Applications folder, macOS puts it in quarantine, and that state can break updates.

The vendor's FAQ describes this symptom for ForkLift 3: a "read-only" error when updating, and the Dock icon disappearing after a restart. The documented fix:

1. Make sure there is only one copy of the app, in the Applications folder.
2. Quit ForkLift.
3. In Terminal, run sudo xattr -d -r -s com.apple.quarantine /Applications/ForkLift.app and enter the account password.
4. Add the app to the Dock again.

The path in that command is the ForkLift 3 name. For ForkLift 4, check the exact app name in Applications first, since the Quick Start Guide notes that keeping ForkLift 3 and 4 side by side often leads to one being renamed.

The same guide also warns against removing one ForkLift version with an app deleter utility. Those tools tend to remove shared support files, and settings and favorites can be lost for both versions. Moving the unwanted version to the Trash is the safe way.

Step 5: Symptoms that look like bugs but have a setting

Once license, version, permissions and quarantine are clear, what remains is usually a single setting. These come up repeatedly in the vendor's FAQ.

Symptom	Cause	Fix
A new file on an FTP server does not appear	The view has not refreshed	View > Refresh, or Command-R. A Refresh button can be added via View > Customize Toolbar
Clicking an app opens its contents	Treat packages as folders is on	View > Show View Options (Command-J), turn it off
Folders do not sort by size or date	Folders are kept on top or sorted by name	In View Options, turn off "Always sort alphabetically" and "Show folders on top"
A favorite changes both panes	The favorite is set to do so	Right-click the favorite, choose Edit
OneDrive fails with "The data couldn't be read because it isn't in the correct format"	Damaged login cookies in the browser	Delete cookies for live.com and microsoftonline.com in the default browser, then reconnect
Dropbox placeholders do not behave as expected	Dropbox Smart Sync has no API	Not supported in ForkLift
iCloud Drive is missing from the sidebar	It is not added by default	Go > Go to Folder, enter ~/Library/Mobile Documents/com~apple~CloudDocs, then Favorites > Add to Favorites

Two release notes also explain behavior that looks like a fault. Version 4.7.5 changed transfers so that a copy does not start when the source contains items with conflicting names, to prevent overwriting. A transfer that "does nothing" in that case is the safeguard working. The same release fixed the file view not updating after an external drive was disconnected without ejecting, so a stale drive in the sidebar on an older build is a known issue rather than a local problem.

Remote connections that refuse to connect

SFTP problems deserve their own check. The 4.7.6 release notes list fixes for compatibility issues with some SFTP servers, so a server that connects from Terminal but not from ForkLift is worth retrying on the latest covered build before anything else. When a server uses key authentication, the Quick Start Guide places the key in an unexpected spot: click the key icon inside the Password field of the Connect Panel and add the private key there, including passphrase-protected keys. A custom port goes under Show Advanced in the same panel. Both settings are easy to miss when a connection is recreated from another client, so check them before assuming the server or the account is at fault.

Step 6: When favorites or settings are lost

After restoring a Mac from a backup, or after deleting an extra copy of the app, favorites can vanish. The vendor's FAQ gives the location: ~/Library/Application Support/ForkLift/Favorites/Favorites.json. Find that file in the backup and put it back in the same place.

Passwords are not in that file. They are in the Keychain. If iCloud Keychain was on, ForkLift picks them up again. If not, each saved connection needs its password entered again by right-clicking the favorite and choosing Edit.

ForkLift can also sync favorites through iCloud, set during the Welcome Window or later in settings, which doubles as a backup of the favorites list. Multi-rename and sync favorites from ForkLift 3 cannot be imported into ForkLift 4, because those features work differently in version 4, so their absence after an upgrade is expected.

If ForkLift still is not the right fit

Most people who work through these steps end up with a working app. Some find that the friction is not a bug at all, but the shape of the work. ForkLift is built around two panes and remote connections. Its own feature list includes opening a Terminal, iTerm, Hyper, Kitty, Warp or Ghostty window at the current path, which is a separate window.

For work that is mostly in a terminal, such as running scripts or AI coding tools against local folders, a file manager with the terminal built into the same window removes that switch. Such tools generally do less on the remote side, so the choice depends on whether the day is spent on servers or on local projects. The comparison page and the FAQ set out where that kind of tool fits and where it does not.

What to change first

Open ForkLift > About ForkLift and compare the eligibility date with the installed version before touching anything else. Then confirm Full Disk Access. If the problem is less about ForkLift breaking and more about switching between the file manager and a terminal, Atriens is free to try on the Mac.