// troubleshooting guide · quicksilver
Quicksilver High CPU Usage and Spinning Wheel
- Status
- Ongoing
- platforms:
- macOS
- updated:
- November 18, 2026
- reports:
- 4
- Method
- how we research
RUNBOOK · quicksilver/high-cpu-usage5 FIXES
// quick answer
High CPU in Quicksilver usually means the catalog is too large or a known process-monitor bug. Remove deep or network catalog sources, clear clipboard history and the cache, and check the Process Manipulation plugin.
Most likely fix: Shrink the catalog
How to fix it
// try these in order, the most common fix is first
FIX 1Shrink the catalog
- 01Open Quicksilver Settings > Catalog
- 02Remove custom sources with infinite depth or your entire home folder
- 03Uncheck Find All Applications if it scans network drives
- 04Click Rescan
Did this fix it?FIX 2Clear clipboard history
- 01Check the size of ~/Library/Application Support/Quicksilver/Shelves/QSPasteboardHistory.qsshelf
- 02If large, clear it from the Clipboard History panel, or quit Quicksilver and delete the file
Did this fix it?FIX 3Check the Process Manipulation plugin
- 01Open Settings > Plugins
- 02If you don't need running-app actions, disable the Process Manipulation plugin and restart
Did this fix it?FIX 4Clear the cache and restart
- 01Quit Quicksilver
- 02Delete ~/Library/Caches/Quicksilver
- 03Relaunch
Did this fix it?FIX 5Look for a conflicting app
- 01Quit Karabiner-Elements or similar keyboard tools temporarily
- 02One user found Karabiner made Quicksilver sluggish and miss keystrokes
Did this fix it?
SANDBOX · quicksilver RUNS IN YOUR BROWSER
Try it: a launcher with snippets and clipboard history
A hands-on Quicksilver-style sandbox, including the spots where users get stuck. See where problems like this one start. 1-2 minutes, nothing is saved.
Symptoms
Quicksilver uses 30-95% CPU while idle, the scanning indicator never stops, the beachball appears, memory climbs, and the hotkey responds slowly.
Why it happens
- C-01Catalog sources with infinite depth, the whole home folder or network drives
- C-02Process monitor reloading every time an app (often Safari web processes) launches or quits
- C-03Huge clipboard history file
- C-04Sorting large sources in the catalog drawer
// this guide also covers
- quicksilver high cpu
- quicksilver using a lot of memory
- why is quicksilver so slow
- quicksilver spinning wheel
Still not working?
If Quicksilver keeps failing, you're not alone. See every Quicksilver problem users report or the alternatives people switch to.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to usThe same problem in other apps
All slow, laggy or resource-hungry guides →
Raycast High Memory and CPU Usage (Raycast)
Alfred Slow to Open or Lagging (Alfred)
LaunchBar High Memory Usage (LaunchBar)
Other Quicksilver errors
- Quicksilver "Interface Could Not Be Loaded. Switching to Bezel"
- Quicksilver Not Working After macOS Update (Tahoe, macOS 27)
- Quicksilver Keeps Crashing
- Quicksilver Keeps Asking for Permissions
- Quicksilver Not Finding Applications
- Quicksilver Not Finding Files
- Quicksilver Hotkey Not Working
- Quicksilver Actions Not Working (Finder, Mail, AppleScript)