raycastvsalfred

what each one actually is

Raycast is a mac launcher and productivity tool built by a well-funded startup that launched in 2020. the core proposition is a spotlight replacement that's free, extensible through a real TypeScript/React SDK, and increasingly AI-native. the extension marketplace has 1,500+ extensions covering everything from linear issue creation to Vercel deployments to GitHub PR review. they make money on raycast pro ($8/month for AI and cloud sync).

Alfred is the original mac power launcher, built by Andrew and Vero Pepperrell and sold independently since 2011. it runs as a small, fast, self-contained app with a powerpack that unlocks its full capability. alfred has no VC behind it — it's indie software that's survived 15 years on word of mouth and a dedicated user base. the development pace is deliberate, the feature set is stable, and the workflow system is powerful enough that some people have built entire automation pipelines inside it.

pricing, honestly

raycast core: free forever, no limits on extensions or features. raycast pro is $8/month (or $96/year) for AI assistant, advanced window management, and cloud sync. the AI features are genuinely useful but not necessary for most use cases.

alfred base: free. alfred powerpack: £29 (approximately $36 USD) for a single user, or £49 for a mega supporter license that includes all future updates. this is a one-time payment — no subscription. if you'll use alfred for 5+ years, the lifetime math is excellent. if you're not sure, the free tier is functional for basic launching.

for most people evaluating both tools today: raycast is free, alfred requires payment for full functionality. that's the decision.

what it's actually like to use them

raycast's UI is the best-looking launcher on mac. results are well-ranked, the command palette is clean, and the extension APIs are modern enough that third-party developers ship genuinely polished integrations. the onboarding walks you through setting it up as spotlight replacement and importing hotkeys. clipboard history, window management, and snippets work well out of the box.

alfred's interface is more utilitarian — it's been the same basic design for years, which is either comforting or dated depending on your perspective. where alfred shines is in the workflow editor: a drag-and-drop node system for building automation pipelines that runs shell scripts, AppleScript, Python, or PHP. complex workflows are easier to build in alfred's visual editor than in raycast's scripting approach. if you want to automate macOS at a deep level and you're comfortable with alfred's idiom, it's still excellent at that specific job.

who raycast is for

• anyone starting fresh with a mac launcher in 2024–2026
• developers who want integration with modern tools (linear, github, vercel, jira, figma)
• teams where everyone should be on the same launcher and extension set
• anyone who wants AI features baked into their launcher
• people who don't want to pay for a launcher

who alfred is for

• mac power users with years of existing alfred workflows
• people who want a stable, offline-first, indie-developed tool with no subscription risk
• anyone who runs complex AppleScript/shell automation through workflows
• users who specifically need the alfred remote iOS app or deep macOS automation integration

when to avoid each

don't start on alfred today if you're picking a launcher for the first time. the extension ecosystem is smaller, development is slower, and the initial cost (powerpack) is a friction raycast doesn't have. alfred's advantage is for people who are already there.

don't expect raycast to handle very deep Alfred-style automation workflows without some reconfiguration. raycast's scripting model is different from alfred's visual workflow editor. for heavy macro builders, the conversion isn't always 1:1.

stuff their landing pages won't tell you

• raycast has a "pro" tier but the freemium model is unusually generous — most power users will never need pro
• alfred's workflow community (alfredapp.com/workflows) is large and mature — thousands of free workflows, well-documented
• raycast updates frequently and sometimes breaks extensions — the marketplace moves fast and occasionally creates regression
• alfred runs more efficiently in the background — it's genuinely a smaller process than raycast
• raycast's AI features require internet; alfred is fully offline by default
• raycast requires an account; alfred does not — a meaningful difference if you care about data privacy

the call

raycast. the free, active development, and modern extension ecosystem make it the obvious default for anyone new to mac launchers. the AI integration is a real differentiator as of 2026.

stay on alfred if you've been using it for years and your workflow is working. migration pain is real. if you're not hitting alfred's limits, there's no forcing function to switch. but if you're starting fresh or evaluating both for the first time, raycast is where you should be.