// troubleshooting guide · capture one
Why Is Capture One So Slow? (Catalog Lag Fixes)
- Status
- Workaround available
- platforms:
- macOS, Windows
- updated:
- November 16, 2026
- reports:
- 5
- Method
- how we research
RUNBOOK · capture-one/slow-performance6 FIXES
// quick answer
Capture One slows down mostly with large catalogs, unfinished previews, catalogs on network or external drives, and GPU problems. Let previews finish, verify the catalog, move it to an internal SSD and split it or use Sessions if it is very large.
Most likely fix: Let previews finish generating
How to fix it
// try these in order, the most common fix is first
FIX 1Let previews finish generating
- 01After a big import, check the activity indicator and wait until preview generation completes
- 02Avoid heavy editing or searching while previews are still building
Did this fix it?FIX 2Verify the catalog
- 01Close Capture One
- 02Hold Option (Mac) or Alt (Windows) while launching to open the catalog picker
- 03Select the catalog and choose Verify, then let it repair any errors it finds
Did this fix it?FIX 3Move the catalog to an internal SSD
- 01Close Capture One
- 02Copy the .cocatalog / catalog folder from the network or external drive to your internal SSD
- 03Open the copy with File > Open; image files can stay where they are
Did this fix it?FIX 4Rebuild into a fresh catalog
- 01Create a new catalog with File > New Catalog
- 02Use File > Import Catalog to import the slow catalog into it
- 03Work in the new catalog and keep the old one as a backup
Did this fix it?FIX 5Split huge catalogs or switch to Sessions
- 01Create separate catalogs by year or client
- 02For job-based work, use File > New Session so each shoot has its own small database
Did this fix it?FIX 6Clear filters before batch metadata edits
- 01Turn off active filters or switch to a plain folder/album before applying keywords, ratings or labels to many images
Did this fix it?
Symptoms
Spinning beach ball or 'not responding' when switching albums, folders or tool tabs; slow search and filtering; editing metadata while a filter is active becomes extremely slow; browsing lags after import.
Why it happens
- C-01Previews for newly imported images are still being generated
- C-02Very large catalogs (tens of thousands of images)
- C-03Catalog stored on a network drive or slow external disk
- C-04Catalog database errors or cruft built up over years
- C-05Metadata edits while a filter or smart album is active
- C-06GPU (hardware acceleration) problems
// this guide also covers
- capture one slow
- capture one catalog slow
- capture one lagging
- capture one not responding
- capture one performance
Still not working?
If Capture One keeps failing, you're not alone. See every Capture One 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 →
Lightroom Classic Running Slow (Adobe Lightroom)
Why Is Affinity Photo So Slow (Affinity Photo)
Other Capture One errors
- Capture One Tethering Not Working (Camera Not Detected)
- Capture One Activation Limit Exceeded
- Capture One Crashing on Startup
- Capture One Export Not Working (Process Queue Stuck)
- Capture One Black Images and GPU Artifacts
- Capture One Images Offline (Missing Files)
- Capture One Not Reading RAW Files From New Camera
- Capture One Lightroom Import Missing Edits and Keywords