ForkLift not working: what to check, in order

The awkward thing about ForkLift failing is that four completely unrelated causes produce almost the same picture. It will not launch, folders look empty, a server will not connect, a view refuses to refresh. Any of those can come from a license state, from a build that does not match the installed macOS, from a missing permission, or from a quarantine flag left on the app bundle. Working through them in a fixed order finishes faster than opening settings panels and changing whatever looks plausible, because three of the four are invisible from inside the app's preferences.

First, separate a fault from a license state

This is the most common misdiagnosis. A ForkLift license covers a specific set of builds permanently, while the right to install newer ones expires at the end of the term chosen at purchase. Install a build released after that date and it launches in trial mode, with a message saying the key is not valid for this version. Nothing is broken. The key simply does not extend to that build.

The answer is inside the app. Open the ForkLift menu and choose About ForkLift, and the update eligibility date appears below the name and license type. Anything released after that date is out of scope. Two routes lead out. Download the last build released before that date from the vendor download page and install it in place of the current one, or buy a fresh license, entering the old key at checkout to add 100 days of eligibility.

Skipping this step is expensive. Permissions and preferences can be adjusted all afternoon without moving a symptom whose cause is a date.

Second, check the build against the installed macOS

If the trouble started the morning after a system upgrade, this is almost certainly it. Two boundaries apply at once.

ForkLift 4.3.4 and later are compatible with macOS Tahoe (macOS 26), while earlier versions are not. Source: binarynights.com

The vendor attributes that break to a system level change introduced by Apple, and 4.3.4, released on 24 June 2025, was the build that addressed it during the Tahoe beta period. The other boundary runs the opposite way: version 4.4, released 26 August 2025, raised the requirement to macOS Sonoma 14.6, so a Mac still on Monterey 12.4 cannot install anything newer than the 4.3 series.

These two sections connect. If Tahoe is installed and the update eligibility from step one ended before June 2025, there is no build that is both compatible and covered. That is not a defect to troubleshoot. The only exits are buying a new license or reverting the operating system.

Third, check permissions, which fail loudly and look like breakage

Launches fine, but folders appear empty, external drives will not open, and dragging does nothing. That combination is a permission problem, and the documentation is blunt about 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

The prompt appears at first launch. Dismissing it and carrying on produces exactly the symptoms above, and an evaluation made in that state is measuring the permission rather than the application. It can be granted afterwards from the privacy section of System Settings. A locked Photos library that refuses to copy is the same permission surfacing in a different place.

A related behaviour surprises people and is not a fault. The first operation that needs elevated rights triggers a request to install a helper tool, followed by an administrator password prompt. Applications run as the logged in user, and Apple requires elevated privileges to be handed to a separate helper only while they are needed, so creating an item outside the user's own area cannot proceed silently. Being asked for a password there is the system working as designed.

Fourth, if launching itself is unstable, suspect quarantine

A read only update error together with a Dock icon that disappears after every reboot points at the quarantine attribute macOS attaches to applications first launched from outside the Applications folder. Running it straight out of the Downloads folder is the usual cause.

The documented fix is to make sure only one copy exists, place it in the Applications folder, quit it, then run sudo xattr -d -r -s com.apple.quarantine /Applications/ForkLift.app in the Terminal, enter the account password, and add the app back to the Dock. Doing this while duplicate copies are scattered around the disk produces confusing results, so consolidate to a single copy first.

Worth noting alongside this: ForkLift 3 and ForkLift 4 can live on the same Mac deliberately. When removing one of them, the vendor specifically warns against using an application deleter, because shared support files get taken with it and the remaining copy loses its settings and saved connections. Drag the unwanted copy to the Trash instead.

When only remote connections fail

Local browsing fine, servers not. At that point the cause is usually specific to one destination rather than to the app.

• OneDrive returning a message about data not being in the correct format comes from stale authentication cookies in the browser used to log in. The documented fix is removing website data for live.com and microsoftonline.com in the default browser, then reconnecting.
• Dropbox Smart Sync not being reflected is not a setting. The vendor states that no API exists for that feature, so it cannot be implemented.
• S3 compatible providers such as Wasabi or DigitalOcean Spaces connect by setting the protocol to Amazon S3 in the Connect panel and supplying the credentials for that service.
• A hang against an unresponsive server was addressed in 4.7.5, released 1 September 2026, so an older build may be part of the picture if update eligibility allows moving up.
• An SFTP authentication problem specific to the Setapp distribution was fixed in an earlier release, which is worth knowing if the app arrived through the bundle rather than directly.

The split is simple. Every destination failing at once points back at permissions or the network. One destination failing points at that destination's credentials or settings.

Symptoms that are settings, not faults

Several reports that read like breakage are single preferences. These all come from the vendor's published answers.

What is happening	What to change
Clicking a favourite changes both panes	Right click the favourite, choose Edit, clear the Local Path field, save
Clicking an application opens its contents instead of launching it	Press Command-J for View Options and deselect Treat packages as folders
Sorting by a column header leaves folders in place	In View Options, turn off Always sort alphabetically and Show folders on top
New files on a server do not appear	View > Refresh, or Command-R, or add the Refresh button through Customize Toolbar
A disconnected external drive stays in the list	Fixed in 4.7.5 for drives removed without ejecting first

The first two rows account for most of the reports that read as regressions. Both are one checkbox. Open View Options and the favourite editor before changing anything larger.

When favourites or settings have vanished

After restoring from a backup, saved connections sometimes come back empty. The list lives at ~/Library/Application Support/ForkLift/Favorites/Favorites.json, and replacing that file from the backup restores the entries. Passwords are not in it. They are held in the Keychain, so unless Keychain syncing through iCloud was already enabled, each connection needs its password entered again through the favourite's edit panel.

Favourites left behind in ForkLift 3 can still be imported later. The documented sequence is disabling iCloud favourite sync, quitting the app, optionally deleting the relevant folder under ~/Library/Group Containers/, running defaults delete com.binarynights.ForkLift.plist setupDone in the Terminal, then relaunching and accepting the import offer in the welcome window. Multi rename and sync favourites are the exception and cannot be imported at all, since those features are built differently across the two versions.

Changes that were deliberate and read as regressions

A separate category deserves its own check, because nothing in the app signals it. Some behaviour differences are intentional changes shipped in a point release, documented in the version history and nowhere else.

Version 4.7.5 is a clear case. When a transfer source contains items with conflicting names, the transfer now refuses to start rather than proceeding, which the release notes describe as preventing files from being overwritten unintentionally. Anyone who had been relying on the previous behaviour sees a transfer that will not begin and reasonably reads it as a fault. Version 4.2 is another: it added a setting to open remote connections in a fixed pane instead of whichever pane happens to be active, so a server can land somewhere unexpected after an update, and the control for it sits under General in Settings.

The rule that falls out of this is simple. Before reporting a behaviour change as a bug, read the notes for the versions between the last known good build and the current one. With releases arriving roughly every 22 days, a gap of a few months can cover half a dozen builds.

Collect four facts before contacting support

If all four checks come back clean and no setting matches, the remaining path is the vendor, and the report is far more useful with four specific items in it.

The first is the exact version number from About ForkLift, along with the update eligibility date shown there. The second is the macOS version, since so many of the boundaries above are stated in terms of it. The third is the exact wording of any message, copied rather than paraphrased, because several messages differ by only a few words and point at different causes. The fourth is whether the problem reproduces against a second destination, which is the single fastest way to separate an application level fault from one specific server or account.

Two built in views help assemble that. The activity view shows operations while they are running, including copying, renaming, deleting and compressing, which is where a stalled step becomes visible instead of silent. The log view records what those operations resulted in afterwards, which is what to read when something reported success but produced nothing. Support is reached at the address published on the vendor support page, and a report carrying those four facts plus a log excerpt generally avoids an entire round trip of clarifying questions.

What to change first

Check the About date, then the build against the macOS version, then Full Disk Access, then the quarantine attribute, in that order, before touching any preference. Only when all four come back clean does it make sense to work through individual settings and destinations. If the diagnosis itself is what feels slow, because each check means leaving the file list for a terminal and coming back, folders, a terminal and an assistant in one window removes those trips, and Atriens covers what that setup does and does not include.