Why Lightroom is slow when you cull: cause by cause

"Lightroom is slow" is not one problem. It is at least six, they have different causes, and the fix for one will do nothing for another. This is a diagnostic: work out which slow you actually have from the symptom, then apply the specific setting that addresses it. Everything here is checked against Adobe's own performance guidance for Lightroom Classic.

Work out which slow you have

Before you change a single setting, notice precisely when the delay happens. The symptom tells you the cause, and guessing wastes an evening.

All of this describes Lightroom Classic, version 15, checked August 2026. Lightroom Classic and the cloud-based Lightroom are different products with different performance characteristics, and the settings below exist in Classic. If you want the whole method rather than the repairs, that lives in our Lightroom culling workflow.

Cause 1: it is drawing previews while you work

This is the big one and it accounts for most complaints. Lightroom cannot show you a RAW file directly, because a RAW file is sensor data rather than a picture. It shows you a preview it built. If you did not build previews at import, it builds them on demand, one at a time, at the exact moment you want to look at each photo.

Adobe's import options documentation gives you four choices in the File Handling panel. Minimal uses "the smallest previews embedded in the photos", which is why the grid appears instantly and then every photo you open makes you wait. Embedded & Sidecar uses "the largest possible preview available from the camera", which is faster than rendering because the camera already did the work. Standard renders Lightroom's own previews. 1:1 renders "a 100% view of actual pixels".

The fix

• Import with Embedded & Sidecar for a first pass. You are deciding keep or not keep, and the camera JPEG preview is enough for that decision on almost every frame.
• In Catalog Settings > File Handling, set Standard Preview Size to the value closest to the long edge of your screen resolution but not smaller than it, which is Adobe's own guidance in its performance guide. A larger setting is wasted work every single time.
• In the same panel, set Preview Quality to Low or Medium. Adobe recommends this explicitly. You will not see the difference in a culling pass.
• Build 1:1 previews only for the frames you will actually zoom into, via Library > Previews > Build 1:1 Previews on a selection, rather than for the whole card at import.

Library > Previews > Build Smart Previews is worth knowing too. A Smart Preview is a lightweight file based on lossy DNG, and it lets you keep working when the originals are on a drive you have unplugged. We go through when they help and when they cost you in the Smart Previews guide.

Cause 2: your 1:1 previews keep getting thrown away

Here is the one that makes people think their computer is failing. You cull a wedding on Sunday, it is fine. You come back to the same wedding three weeks later to finish, and it is treacle again on photos you have already viewed at full size.

Lightroom is not broken. It discarded the 1:1 previews on a schedule and is now rebuilding them from scratch. The setting is in Catalog Settings > File Handling > Automatically Discard 1:1 Previews, and the shipped behavior throws them out sooner than a photographer with a backlog would want.

The fix

Set it to After 30 Days or Never. Adobe's performance guide names those two options specifically as the way to avoid regeneration overhead. The tradeoff is honest and worth naming: 1:1 previews are large, so keeping them forever costs disk space. If you are tight on space, 30 days is the right compromise, because it covers the realistic life of a job.

If you routinely come back to shoots weeks later, this single setting is often the difference between a fast session and a lost hour, and it is a big part of why a backlog feels heavier than it is. We wrote about what that pile actually costs in the hidden cost of slow culling.

Cause 3: the Camera Raw cache is too small

Separate from previews, Lightroom keeps a cache of partially processed RAW data. It is what makes the second visit to a photo faster than the first, particularly at 100%. When the cache is too small for the size of your shoots, it fills up, throws away the oldest entries, and every photo becomes a first visit forever.

The signature symptom is very specific: you zoom into a frame, wait, decide, move on, come back to that same frame ten minutes later, and wait again.

The fix

Go to Preferences > File Handling > Camera Raw Cache Settings. Adobe's performance guide states the default is 5 GB and recommends 10 GB or more for better Develop module performance. For anyone shooting weddings, where a single job is 2,000 to 4,000 RAW frames, go well past 10 GB if you have the space. Put the cache on your fastest internal drive, never on the external you are culling from.

This costs nothing but disk space and it is the most commonly skipped item on this list, because it is buried in Preferences rather than Catalog Settings and nothing in the interface ever suggests it to you.

Cause 4: it is writing to disk on every keystroke

This one specifically punishes culling, which is why it belongs on this page and not in a general performance article. A flag or a star is a metadata change. If Lightroom is configured to push metadata changes out to XMP sidecar files as they happen, then every P and every X you press triggers a small disk write. One is nothing. Three thousand, at the speed you want to work, is a stutter between every photo.

Adobe does not hedge about this. Its performance guide says autowriting to XMP "can significantly degrade Lightroom Classic performance".

The fix

Open Catalog Settings > Metadata and uncheck Automatically Write Changes Into XMP. Your flags and ratings are still saved, in the catalog, which is where Lightroom reads them from anyway.

The caveat, stated plainly: if another application needs to see your ratings in the files themselves, or you hand RAW files plus sidecars to an editor or a second shooter, you need those sidecars. In that case leave the setting off during the cull and write them deliberately afterwards with Metadata > Save Metadata to File on the whole selection at once. One batch write is far cheaper than three thousand individual ones. If you regularly pass files between people, get the handoff itself right first, which is what culling second shooter photos is about.

Cause 5: the files or the catalog are on the wrong drive

No setting saves you from culling directly off a memory card, off a USB bus you are sharing with three other devices, or off a mechanical drive with 4 GB free. Every preview Lightroom builds has to read the original first, and that read is happening across your slowest link.

Adobe's guidance is unambiguous: put catalogs, images and previews on solid state drives, and keep at least 20 percent free on the drives holding your catalog and preview files. A drive that is nearly full is slow at everything, and preview files are exactly the kind of large, constantly rewritten file that suffers most.

The fix

• Copy from the card to a fast local drive first, then import from there. Never cull off the card. This is step one of a sane ingest routine, and it protects your files as well as your speed.
• Keep the catalog file on your internal SSD, even when the images live on an external. The catalog is small and it is read constantly.
• Check free space on both drives before a big job. Twenty percent is the number.
• Run File > Optimize Catalog occasionally. Adobe also suggests enabling Test Integrity Before Backing Up and Optimize The Catalog After Backing Up so it happens on its own.

Cause 6: something else is using the machine

If the slowdown comes and goes rather than being constant, the cause is usually contention rather than configuration.

The graphics processor

Check Preferences > Performance and confirm Use Graphics Processor is on and your drivers are current. Adobe's guide says to enable it, and also says to turn it off if your particular GPU proves incompatible. Both directions are worth testing on your own machine, because a mismatched driver produces exactly the kind of intermittent stutter this section is about.

Background analysis

Adobe's newer AI features analyze your photos in the background, and that analysis competes with the previews you are waiting on. If you have just enabled Assisted Culling or kicked off Auto Analysis on a fresh import, let it finish before judging the speed. It is a one-time cost per shoot, not a permanent tax, but it lands at the worst possible moment if you start culling the second the import bar disappears.

Memory

Adobe lists 8 GB of RAM as the minimum for Lightroom Classic and 16 GB or more as the recommendation. If you are at the minimum and running a browser with thirty tabs, the browser wins. This is the only item on the page that costs money, which is why it is last: work through the other five first, because they are free and they are usually the real answer.

The slow that no setting fixes

Work through those six and Lightroom will feel like a different application. It is genuinely worth an evening, and most photographers get the bulk of the benefit from causes 1, 2 and 4 alone. If you want the settings as a checklist rather than a diagnosis, we laid them out in order in the Lightroom culling speed setup.

Then notice what is left. A perfectly tuned Lightroom still shows you every frame you shot, one at a time, at a desk, on a night when you would rather be asleep. A wedding is typically 2,000 to 4,000 RAW frames and around 400 to 800 delivered, so most of what you are looking at was never going to make it. The software got faster. The number of decisions did not change.

That second kind of slow is a different problem with a different answer: fewer frames reaching your eyes in the first place, and the first pass happening somewhere other than the desk. It is what we are building Kepla to do. It picks your best shots and hands you a shortlist to approve, and it never deletes, moves or renames a single file, so everything it did not pick is still there. The picking app for iPhone, iPad and Mac is still in development, and the booking page is live and free today while we build it.

FAQ