Why is Raycast using CPU or memory on my Mac?
Last reviewed: 19 November 2026. Behavior and settings taken from the Raycast Manual; not installed on the Mac used for checking.
Raycast is a launcher that opens apps, files, extensions, clipboard history and AI features from one hotkey, and it runs in the background so it is ready instantly. It uses the most CPU while File Search builds its own index of your home folder and Applications, and memory grows with extensions and features such as clipboard history. It is safe; File Search settings let you narrow or pause indexing.
Raycast at a glance
| Raycast | |
|---|---|
| Made by | Raycast |
| Type | Launcher app |
| Runs as | your user |
| Can you quit it? | Yes. Its hotkey, snippets and clipboard history stop working until you open it again. |
What is Raycast?
Raycast is a third-party launcher for Mac that replaces or sits alongside Spotlight. It stays open in the background, which is why it is always listed in Activity Monitor, and it handles snippets, quicklinks, clipboard history, window management, extensions from its store and AI features.
For finding files by name, Raycast keeps its own local index, which the Raycast Manual says is stored on your device and never synced or uploaded. By default it indexes your home folder and /Applications. Searching inside file contents uses macOS's own Spotlight index instead.
Is Raycast safe?
Yes. Raycast is a commercial app. It asks for access to folders before indexing them, and you can grant access to specific folders only.
Why does Raycast use so much CPU, disk, memory and network?
- Building the File Search index. On first launch, after resetting File Search settings, or when you choose Index Files, Raycast scans your home folder and Applications. This is the heaviest work it does and settles when the scan finishes.
- Folders that change constantly. Folders that an app keeps rewriting cost indexing work. Raycast stops indexing some of these on its own and lists them under Excluded Automatically.
- Extensions. Each extension you run adds its own work. The Raycast Manual lists an extension that crashes or behaves unexpectedly, and Raycast using a lot of memory, among common troubleshooting cases.
- AI and cloud features. AI chat, AI commands and Cloud Sync send and receive data over the network when you use them.
How much CPU is normal for Raycast?
When idle, a launcher like Raycast typically sits near 0% CPU and wakes only when you press its hotkey. CPU during the first file scan, or after you add a large folder to Search Scopes, is expected and temporary.
Memory use varies with the extensions and features you use; a steady level is normal, steady growth over days is not.
How do you stop Raycast from using so much CPU?
- Let the first index finish. After installing Raycast or resetting File Search, give the scan time to finish. You can pause it with the Stop Indexing action and restart it later with Index Files.
- Narrow Search Scopes. In Raycast Settings > File Search, remove folders you never search from Search Scopes, and leave Index Network & Removable Drives off unless you need it.
- Ignore busy folders. Add patterns such as
*.logunder Ignore Patterns, or put a.rayignorefile in a folder to skip paths inside it. Raycast already respects.gitignorefiles and skipsnode_modulesand common caches. - Check your extensions. If memory or CPU rose after adding an extension, disable it and watch Activity Monitor. The Raycast Manual's troubleshooting page covers memory use and misbehaving extensions.
- Send logs to Raycast. Use the Send Feedback command inside Raycast to report the problem with its logs attached.
When should you worry about Raycast?
Look closer if Raycast keeps indexing for hours, or its memory grows steadily while you are not using it. Check Excluded Automatically and recently added extensions first.
Content search depends on the Spotlight index; if it misses files, the problem may be Spotlight indexing rather than Raycast.
How do you check Raycast in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), and type Raycast in the search field. The CPU tab shows its % CPU. The Disk tab shows its Bytes Written and Bytes Read. The Memory tab shows its Memory. The Network tab shows its Sent Bytes and Rcvd Bytes. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every Raycast process with its PID, user, CPU and memory (RSS is resident memory in kilobytes). fs_usage prints each file it reads or writes until you press Control-C; it needs an administrator password. nettop shows its live network traffic.
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'Raycast' | grep -v grep
sudo fs_usage -w -f filesys Raycast
nettop -p Raycast
How can Thrum help with Raycast?
Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when Raycast is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. Click Raycast in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.
Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.
Questions about Raycast
Does Raycast use Spotlight?
For file names, no: it builds its own local index. For searching inside files, it uses the operating system's index, so Spotlight indexing must be healthy for content search.
Does Raycast upload my file index?
No. The Raycast Manual says the File Search index is stored locally and never synced or uploaded to Raycast's servers.