Raycast alternatives: decide what you can drop

Looking for a Raycast replacement usually starts with lining up similar looking launchers. That comparison rarely settles anything, because the app in question is not a launcher. It is a launcher plus clipboard history plus snippets plus window management plus an extension platform plus an AI layer, bundled behind one keystroke. No single replacement covers all of that, so the useful first step is not choosing a destination. It is deciding which parts can be dropped.

Name the actual reason for leaving

Three reasons come up, and they lead to completely different answers.

Cost. Something pushed the account towards a paid tier, or a team discovered the per seat maths. This is worth checking carefully, because the free tier covers more than most people assume, and the paid features in genuine daily use are often one or two.

Distance from AI. Paid individual tiers ship with AI included. The published pricing FAQ addresses this directly, stating that Pro plans are only offered with AI, while noting that AI can be switched off entirely in Settings, which disables all AI features. If the objection is simply not wanting to pay for AI, the free tier answers it without a migration. If the objection is a company policy that forbids connecting to external AI services at all, an off switch inside the app may not satisfy the requirement, and that is a different problem.

Weight. Slow startup, too much running in the background, too many icons in the menu bar. This reason is the one most likely to follow a person to the next tool, because the cause frequently sits in the installed extensions rather than in the app itself.

Know the price list before deciding anything

Figures below were on the public pricing page on 10 September 2026.

Tier	Monthly	Monthly equivalent when billed annually
Free	$0	$0
Pro	$10	$8
Advanced AI add on	plus $8	plus $8
Teams Free	$0 per user	$0 per user
Teams Pro	$15 per user	$12 per user

Annual billing is marked as 20 percent off, which works out to $96 a year for Pro, $192 a year with the advanced AI add on, and $144 per user per year for Teams Pro. Enterprise pricing is custom and annual only. Verified students can apply for 50 percent off Pro, with the advanced AI add on excluded from the discount.

The free tier's boundaries are equally specific. Clipboard history is retained for three months, notes are limited to five, and AI features and cross device sync are not included. Everything else in the core set is there: application launching, calculator, snippets, quicklinks, window management, thousands of extensions, custom extension development, and developer tooling. The free Teams tier is not a trial and does not expire, but caps shared items at five commands, thirty quicklinks, and thirty snippets.

Count what is actually used, for one week

This is the whole preparation step. For one week, note every command actually invoked. Doing it from memory does not work, because remembered usage includes features that impressed once and were never touched again.

Most logs settle around ten entries. Launching apps, doing arithmetic in the search bar, recalling something from clipboard history, expanding a few stock phrases, tidying windows. Those five categories typically account for the bulk of it.

Then sort the list into daily, occasional, and never appeared. That third group is the answer to the question this article opened with. Everything in it can be dropped, and dropping it shortens the candidate list dramatically.

Check what macOS already covers

Some of the surviving items need no software at all, and removing those from the requirements shrinks the problem again.

• Launching and finding files is largely covered by Spotlight
• Stock phrases can be handled by text replacement in the Keyboard settings
• Window tiling is built into macOS from Sequoia onwards
• Emoji and symbols have a system picker with its own shortcut

How far this gets depends on depth of use. Launching an app is covered. Launching an app while opening a specific document, or passing a fixed search term to a browser, is not. Simple text expansion is covered. Expansions containing a date or an input field are not. The week of logging makes it obvious which depth applies.

The two hard cases are clipboard history and extensions. macOS has no built in equivalent for the first, so it means either a dedicated app or staying on a paid tier. The second cannot be migrated at all, because its value is the number of people building for that platform rather than any particular feature.

Extensions are what fill the menu bar

This part is easy to miss. Extensions for this platform can create persistent menu bar items. The developer documentation has a dedicated category for menu bar commands, covering items that refresh on a schedule and items that act when their icon is clicked.

The implication is direct: the more extensions installed, the more menu bar icons there can be. Stock tickers, weather, task counts, build and server status. Anything whose value is being visible at a glance is exactly the kind of extension that puts something in the menu bar and leaves it there.

So if the reason for leaving is a crowded menu bar, auditing the enabled menu bar commands is the higher yield move. Disabling them reduces the icon count without changing anything else. Skipping that check and switching tools instead usually means rebuilding the same crowding somewhere new, one useful extension at a time.

Three things a switch always costs

Whatever the destination, some things do not travel. Based on the published comparison table, three stand out.

Cross device sync. Paid tiers sync snippets, notes, and chats between Mac, Windows, and iOS. Anyone working across more than one machine should price this in, because a Mac only replacement leaves the other devices unsolved.

The iOS and Windows apps. Irrelevant to a Mac only setup, decisive for anyone else. A Mac utility replaces the Mac half and nothing more.

Team sharing. Shared commands, snippets, quicklinks, and the organisation level admin controls have no equivalent in a personal launcher. In a workplace deployment, this is usually the constraint that decides the outcome.

What is known about the alternatives

Facts only, checked on 10 September 2026. The choice belongs to the reader.

Spotlight ships with macOS. No cost, nothing extra running, and it handles launching, file search, and calculation.

Alfred is free to download, with the extended functionality sold as the Powerpack. The buy page lists a single license at £34 and a Mega Supporter license, which includes free lifetime upgrades, at £59.

LaunchBar comes from Objective Development and offers a free mode alongside paid licenses, with single and family options on its order page. That page does not display a figure before checkout, so the current price has to be confirmed during the purchase flow.

Compare candidates on one axis: how many of the entries from the logged week each one covers. Comparing on total feature count always favours whichever product ships the most features, which has very little to do with how any specific person works.

Replacing one tool with three is a real option

The instinct is to find a single product that does everything the outgoing one did. That instinct is worth questioning, because the bundle was a packaging decision rather than a technical necessity. Splitting the job across two or three focused apps is a legitimate outcome, and sometimes the cheaper one.

A common split looks like this: the system search handles launching and file finding, a dedicated clipboard manager handles history, and text replacement in the Keyboard settings handles stock phrases. Nothing else gets installed. For someone whose logged week contained only those three categories, that combination costs nothing beyond one small utility and removes an entire recurring subscription.

The cost of splitting is cognitive rather than financial. Three tools mean three shortcuts to remember, three preference windows, and three things to reinstall on a new machine. The bundled approach exists precisely because that overhead is annoying. Whether it is annoying enough to pay for is a personal call, and the honest way to answer it is to run the split arrangement for a fortnight rather than to reason about it in advance.

There is a second, less obvious cost. Separate utilities do not share context. A bundled tool can offer a clipboard entry, a snippet, and an app launch from the same search field, which is genuinely fewer decisions per action. Split tools each need their own invocation, and the difference shows up most in the middle of concentrated work. Anyone who values that unified entry point should weigh it as a feature in its own right rather than treating it as packaging.

Judge the trial on habits, not on features

Two weeks is enough for a trial, and the criterion that matters is not whether the replacement can do something. It is whether the hand reaches for it without conscious thought.

Watch for one specific failure: reaching for the old shortcut. If the fingers keep going to the outgoing app after ten days, either the replacement's trigger is wrong or its response is slow enough to break the habit loop. Neither improves with more time.

Watch also for silent abandonment. A feature that was used daily and suddenly is not being used at all usually means the replacement made it slightly harder, and the workaround was to stop bothering. That is the most expensive kind of regression, because it does not feel like a problem while it is happening. Comparing the second week's usage log against the original one catches it immediately, which is another reason the logging step pays for itself.

Where the migration actually gets awkward

The friction in a switch comes from habits, not features. Three items are worth preparing.

The trigger key is the first. After long use, the shortcut that opens the search bar lives in muscle memory rather than conscious memory. Assign the same combination in the replacement, then remove it from the outgoing app. Leaving both active makes it impossible to tell which one responded, which makes the trial useless.

Snippets are the second. Export formats differ between tools, so a large library can take hours to move by hand. Check what the outgoing app exports and what the incoming one reads. If nothing lines up, move the top handful manually and add the rest as situations call for them, rather than stalling on a bulk conversion.

Clipboard history is the third. Assume it does not transfer. On switching day, move anything worth keeping somewhere permanent, and consider leaving the old app installed for a short overlap so history stays reachable. That overlap means two utilities running at once, so decide the removal date in advance rather than letting it drift.

Start here

Log a week of actual usage before comparing anything, then check the never appeared list against the macOS features above. If the underlying complaint is a crowded menu bar, audit the enabled menu bar commands first, since that is fixable without changing launcher at all. For the icons that remain after that, the trade offs between menu bar tools are set out in Features and How it compares, and testing one on the machine with the problem is quicker than reading further: Download.