Path Finder legacy vs modern alternatives: where Path Finder users go in 2026

Path Finder shipped its first version in 2002 and its last in 2023. Twenty-one years of accumulated features and a dedicated userbase that's been quietly looking for a successor since. This post is the migration map — what Path Finder did, where each feature now lives, and which combination of modern apps comes closest.

Path Finder's signature features and their 2026 destinations

The realistic successor combinations

Three combinations cover most Path Finder users:

Combo A — Forklift only

For users who used Path Finder mainly for dual-pane local + FTP.

brew install --cask forklift

What you keep: dual-pane, tabs, preview, FTP. What you lose: Drop Stack, modules, custom commands, quad-pane (PF didn't have this anyway).

Cost: $19.95.

Verdict: solid 70% replacement. Good for users whose PF use was straightforward.

Combo B — mq-dir + Forklift

For users who want quad-pane plus the SFTP polish.

brew install --cask mq-dir
brew install --cask forklift

What you keep: dual-pane (in either), preview (mq-dir is better), tree view (mq-dir), tabs, FTP (Forklift).

What you gain: quad-pane parallelism (PF didn't have this), religious state persistence.

What you lose: Drop Stack, modules, custom commands.

Cost: $19.95 (mq-dir is free).

Verdict: best for users who outgrew Path Finder's 2-pane and wished for 4. Most ex-PF power users.

Combo C — mq-dir + Hex Fiend + Hammerspoon

For users who used Path Finder's modules heavily and want open-source replacements.

brew install --cask mq-dir
brew install --cask hex-fiend
brew install --cask hammerspoon

What you keep: navigation, preview, tree, hex viewing.

What you gain: quad-pane, full state persistence, scriptability via Hammerspoon.

What you lose: SFTP (add Forklift if needed), some Path Finder integration polish.

Cost: free entirely.

Verdict: best for the open-source-leaning ex-Path-Finder user.

Migration playbook (any combo)

Day 1 — install + run alongside

Don't uninstall Path Finder. Install your chosen alternatives. Use them for new tasks.

Week 1 — port favorites + projects

Drag your Path Finder favorites to the new tool's sidebar. If you used PF's tagged sets, replicate the most-used 5-10 in your new tool's bookmarks.

If you had multiple PF windows for different projects, set them up as named Projects in mq-dir (only mq-dir has this feature among the alternatives).

Week 2 — exercise the gaps

Try to do something you used Drop Stack for. Notice the friction. Decide:

• Wait for mq-dir batch ops (v0.2).
• Write a custom shell script for the workflow.
• Stay on Path Finder for that specific task.

For modules: try macOS Preview, Hex Fiend, Terminal.app for the equivalent jobs. Most are fine.

Week 3 — decide

If 80% of your PF workflow is now in the new tools, migrate. Uninstall Path Finder. Trust the migration.

If too much is missing, stay on PF and revisit in 6 months (mq-dir batch ops will have shipped, more options will have emerged).

What no current alternative gets right

Honest list of Path Finder strengths that no 2026 alternative has matched:

1. Drop Stack with cross-folder accumulation.
2. Modules-as-tabs integration (terminal, hex, image, process — all in one window).
3. Per-folder column customization (memory of column visibility/order/width per folder).
4. The sheer surface area of accumulated 21-year features.

For users who depended on items 1 or 2, no 2026 successor matches. You're choosing which gap to live with.

What 2026 alternatives offer that Path Finder didn't

For balance:

• mq-dir's quad-pane: Path Finder was 2-pane; mq-dir is 4.
• Forklift's polished SFTP: PF's was basic; Forklift's is industry-leading.
• Modern macOS integration: PF wasn't keeping up with security/sandboxing changes.
• Yazi's terminal image preview: PF had previews but couldn't compete with Sixel-rendered terminal previews.
• Open-source options: PF was always closed; mq-dir is MIT.

Use case routing

Verdict

Path Finder users in 2026 face a real choice. There is no 1:1 successor. The realistic paths are:

1. Forklift if your use was primarily dual-pane + remote.
2. mq-dir if your use was navigation-focused and you'd benefit from quad-pane.
3. Forklift + mq-dir + companion apps for users who used a broader slice of Path Finder.

The "stay on Path Finder forever" path will end eventually — macOS will hard-block unnotarized binaries in some future major version. Plan now; you don't have to migrate today, but have a destination in mind.

mq-dir is free, MIT-licensed, no telemetry. The best open-source step toward "what would Path Finder have looked like in 2026 if Cocoatech had kept building it."