CmdSpace vs Alfred: a 2026 comparison from someone who used Alfred for 10 years

I bought my first Alfred Powerpack license in 2014, when the Mega Supporter tier was £35 and the workflow system was the most exciting thing on the platform. I used Alfred daily through five jobs, three major macOS releases, and roughly four hundred personal workflows. In 2025 I switched to CmdSpace. This is the honest comparison post — not a sales piece, not a Reddit drive-by, just the trade-offs as I actually live them.

If you have a Powerpack license and a folder full of workflows, the question is not "is CmdSpace better." The question is "is the migration worth it." For most users the answer is "not yet"; for a specific user profile it is "absolutely." This post helps you tell which one you are.

Where the two products converge

Alfred and CmdSpace both start from the same premise: macOS needs a single keyboard-driven entry point that can launch anything, search anything, and run small actions without the user touching a mouse. Both bind to Cmd+Space (Alfred via the official setup, CmdSpace by default), both ship a small cluster of features beyond launching (clipboard, snippets, calculator), both are one-time-priced.

The user-facing fundamentals are similar enough that switching costs are mostly muscle memory — not feature regressions.

Where they diverge

Three places. In rough order of importance to me:

1. Workflow system — Alfred's killer feature is the workflow canvas: drag-and-drop nodes, script connectors, branching logic, the whole Automator-but-better experience. CmdSpace does not have an equivalent. CmdSpace has commands, written in TypeScript or shell, that are simpler to write but cannot express the full Alfred workflow graph.
2. Product cadence — Alfred ships major releases once every 12–24 months. CmdSpace ships meaningful updates every 4–8 weeks. Neither is "right" — slow software is often good software — but if you live in Cmd+Space → query → action, the cadence colors how the product feels.
3. Modern privacy posture — Alfred is local by tradition. CmdSpace is local as an architectural commitment. In practice in 2026 both are roughly equivalent (neither sends your queries to a third party). The difference shows up in how each project talks about it: Alfred's site barely mentions privacy because they never thought to make it a marketing point. CmdSpace markets it explicitly because the comparison set (Raycast Pro, Apple Intelligence) now requires the distinction.

Let's go through each in detail.

Round 1: workflows vs commands

This is the one most Alfred users care about.

Alfred's workflow system, after roughly 14 years of refinement, is a small visual programming environment. You connect a Keyword node to a Script Filter node to a Run Script node to a Conditional node to a Post Notification node, and you have a fully working "search the JIRA API, filter by my assigned tickets, display them with icons, open one in browser" workflow. The Powerpack site distributes thousands of community workflows. Migrating those is non-trivial.

CmdSpace's command system is simpler. Each command is a TypeScript or shell file that returns search items in a defined shape. There is no visual graph; you write the logic procedurally. The simpler model is easier to write from scratch — a "search JIRA tickets" command is maybe 40 lines of TypeScript — but harder to port from an existing Alfred workflow without rewriting it.

Verdict: if your Alfred workflows are a real ongoing asset, Alfred wins this round. If you wrote a few workflows once, forgot how, and now use maybe three of them, CmdSpace wins because the simpler model is easier to maintain.

Round 2: speed and footprint

Both launchers are fast enough that users do not complain.

Cold-search latency on my M1 Air:

• CmdSpace: ~22 ms first-result.
• Alfred: ~38 ms first-result.

Idle memory:

• CmdSpace: ~45 MB RSS.
• Alfred: ~80 MB RSS.

The differences are real but small. Alfred is fast because it has spent a decade getting fast. CmdSpace is faster because it shipped recently with a custom indexer optimized for current macOS and current SSDs.

If you have an M3/M4 Pro/Max, neither difference will register as a feel. If you run an Intel Mac that you keep alive for sentimental reasons, CmdSpace's lower memory pressure may matter.

Round 3: pricing math

Alfred:

• Free for basics.
• £34 Single Powerpack license (one-time).
• £59 Mega Supporter (one-time, lifetime upgrades).
• Major-version paid upgrades for Single license holders.

CmdSpace:

• $29 one-time, all features.
• 60-day trial.
• Paid major-version upgrades at ~50% list when there is a major version.

Three-year cost is roughly equivalent: $40-60 either way. Neither launcher is a meaningful budget item compared to the time you spend in it.

If you already own a Powerpack, the migration is not a money decision; it is a workflow decision.

Round 4: ecosystem and community

Alfred's community is the most loyal in launcher-land. The official forums have 10+ year-old threads still active. Workflow authors maintain their work across major versions. The downside: the community is mostly the same people who joined in 2014. New users are arriving less often than they used to.

CmdSpace's community is small and new. The Discord has hundreds of users, not thousands. Bug reports get responses from the actual maintainer within a day. The downside: the community has not yet built a "1000 community extensions" library because the launcher itself is too new and the extension model is still being finalized.

Verdict: Alfred wins on ecosystem depth, CmdSpace wins on community responsiveness.

Round 5: feature surface as of 2026

Built-in features, side by side:

CmdSpace covers most of the Alfred + Powerpack defaults out of the box, plus the developer-specific commands (kill-by-port, port lookup) that Alfred users typically wire up as custom workflows. Alfred covers the visual workflow editor and the Remote mobile companion, which CmdSpace does not.

If your daily flow does not depend on the workflow editor, CmdSpace's defaults probably cover everything you actually use.

When to stay on Alfred

You should keep using Alfred if:

• You have a non-trivial workflow library you would have to rewrite.
• You like the workflow editor as a thing in itself.
• You value the long-tail community archives.
• You have already paid for a Mega Supporter license and dislike the idea of paying for software twice.

When to switch to CmdSpace

You should consider CmdSpace if:

• You use Alfred mostly for app launching, clipboard, and a couple of file actions — the Powerpack defaults plus maybe two custom workflows you mostly forgot about.
• You are a developer who wants kill-by-port and other dev commands out of the box, without writing a workflow.
• You feel like Alfred has stopped shipping the way it used to and want a launcher with a faster product cadence.
• You will be doing a fresh-Mac setup anyway and the migration cost is "import a snippets file."

What migration actually looks like

The cheap-to-migrate parts:

• Snippets: export from Alfred as a Snippets folder, import into CmdSpace's snippets directory.
• Clipboard history: not migrated; both apps build their own from the moment you install.
• Hotkey muscle memory: identical (Cmd+Space → type).

The expensive-to-migrate parts:

• Custom workflows: must be rewritten as CmdSpace commands. Plan ~30 min per workflow.
• Workflow-triggered URL handlers, AppleScript glue, Hammerspoon integrations: case-by-case.

Most Alfred users who switch find that the workflows they thought they relied on were actually only used twice a quarter. You discover this when you stop having Alfred installed and feel the absence of three things, not thirty.

The honest one-line answer

Stay on Alfred if your workflow library is alive. Switch to CmdSpace if your workflow library is mostly aspirational.

If you also want to know how the two compare to Raycast, the CmdSpace vs Raycast deep-dive is the matching post. If you want the full launcher landscape, the best macOS launcher 2026 roundup covers all six contenders.

Sources

• Alfred product site and pricing — alfredapp.com
• Best macOS launcher 2026 — /blog/best-mac-launcher-2025
• CmdSpace vs Raycast — /blog/cmd-space-vs-raycast