mq-dir vs Forklift: which macOS file manager wins in 2026

Forklift has been the polished commercial answer to Finder on macOS since 2011. mq-dir is a 2026 entrant that picks a different fight — parallel work, not server transfers. Both are excellent at what they do; the question is which fits your daily.

This is the comparison without the marketing.

TL;DR

• Pick Forklift if you spend half your file-management time hitting servers (SFTP/S3/WebDAV) or running sync.
• Pick mq-dir if you run 3+ projects/AI agents in parallel and the dual-pane ceiling actively bottlenecks you.
• Many serious users run both — Forklift for remote, mq-dir for local quad-pane work.

The 10-axis comparison

Where Forklift is genuinely better

Remote servers

Forklift's SFTP client is one of the best on macOS. Connection management, error recovery, multi-file uploads with retry, drag-from-Finder-to-server — it all just works. Server transfers are first-class, not bolted on.

If your workflow includes "I need to sync this folder to staging" or "edit a remote config file" weekly, Forklift saves real time. mq-dir doesn't compete here today; it's local-first by design.

Sync engine

Beyond simple SFTP, Forklift offers folder-pair sync (one-way, two-way, archive). This is a CLI rsync wrapper at heart, but the GUI affordance is well-done. For backups and mirroring workflows, it's strictly better than the alternative scripts.

Mature ecosystem

Ten-plus years of polish. Edge cases handled. Niche features (workspaces, transfer queue, FTP+TLS variants) are all there.

Where mq-dir is genuinely better

Quad-pane parallelism

The whole reason mq-dir exists. Two panes is fine when you copy from A to B. It's wrong when you have:

• Project repo open
• Generated artifacts watched
• Reference docs pinned
• Cmux session output streaming

That's four contexts. Forklift forces you to juggle two of them at a time and alt-tab through windows for the rest. mq-dir gives you all four at once, with ⌘1–4 to focus.

Per-tab preview (and per-tab tree view)

Forklift's preview is window-level. One pane is the focus, preview belongs to it. mq-dir's preview is per-tab — you can have 4 different files open simultaneously, all rendering. For comparing two screenshots, two PDFs, two markdown files visually, this saves dozens of clicks daily.

The per-tab tree view (VS Code-style file tree inside a tab) is also unique to mq-dir among the macOS contenders.

Full state persistence

Forklift's state persistence is shallow. Tabs survive a relaunch; scroll position and sort sometimes don't. mq-dir's persistence is religious — folder, sort, scroll, focus, hidden state, tabs, layout, project — all of it survives force-quit, schema bumps, and macOS migrations. Every Codable type has a hand-rolled init(from:) with decodeIfPresent defaults. There's a testMigration_vN_to_vN+1_preservesAllFields for every schema bump.

Result: you treat the app like a state container, not a navigator. Open a layout six months ago, close, open today — same scroll, same selection.

Open source + zero telemetry

Forklift's privacy is fine in practice — they're a small reputable team. But you're trusting a closed binary. mq-dir's source is on GitHub, MIT-licensed, every commit DCO-signed, zero telemetry by brand promise (the README, CLAUDE.md, and code all enforce this). You can audit it.

For some users this is irrelevant; for others it's a hard requirement.

Where they're roughly tied

• Performance: both handle 10k+ file directories without lag.
• Keyboard: both serious about keyboard navigation.
• Native polish: both feel like real Mac apps (no Electron).
• Memory: both ~80-150 MB resident at idle with a few panes open.

Use case routing

Coexistence

A pattern many users settle into:

• Forklift as default for SFTP/S3/WebDAV (set as default app for sftp:// URLs).
• mq-dir as the daily driver for everything local.
• Default Folder X across both for Open/Save dialog speed.

This is not a "winner takes all" category. The two apps overlap on ~40% of features and diverge on the high-value 60%.

Honest weaknesses

For honesty, what each tool currently fails at:

Forklift:

• 2-pane ceiling is real and not changing.
• Tabs are per-window, not per-pane (means you can't have a project's 5 tabs in a single pane while keeping a separate context in pane 2).
• State persistence is good but not religious.

mq-dir (alpha as of writing):

• No remote server support.
• No batch rename with preview yet.
• No plugin/scripting API.
• Smaller ecosystem (it's v0.x).

Verdict

Forklift is the right answer if your workflow centers on copy/move/sync between two locations, especially when one is remote. It's mature, polished, well-supported.

mq-dir is the right answer if your workflow is parallel — multiple projects, multiple AI sessions, multiple contexts open at once. The quad-pane is the feature; everything else is in service of it.

For most developers running AI agents on macOS in 2026, the answer is "mq-dir as primary, Forklift kept around for the SFTP days." Both free or cheap enough to try; spend an evening with each and trust your hand.

mq-dir is free, MIT, no telemetry. Forklift is $19.95 one-time. Neither is wrong; they're different shapes for different work.