Some links below are affiliate links; buying through them supports the site at no cost to you.
You click the next photo in Develop and the loading spinner sits there. You drag the exposure slider and the image catches up a second later. You import a card and the grid fills in one thumbnail at a time… and the first thought is that the computer is too old. Sometimes it is. Most of the time it isn’t, and Lightroom Classic is running on defaults that were never meant for the catalogue you have now.
Fix where the catalogue lives, the size of the Camera Raw cache and the way previews get built before you spend a dollar on hardware. Those three settings are free, they take ten minutes, and they’re the first three items in my order below. When they don’t fix it, the slowdown points at one specific part, and that part is the only thing worth buying.
TLDR
- Put the catalogue and its previews on an SSD, with at least 20 percent of the drive free. Never on a network drive.
- Raise the Camera Raw cache from the 5 GB default to 20 GB or more, on a fast disk.
- Build previews before you cull: 1:1 previews on import, and a Standard Preview Size close to your screen’s long edge.
Those three, in that order, then the graphics driver and File > Optimize Catalog. If Lightroom is still slow after all five, it’s hardware, and the section on hardware below tells you which part from the symptom.
Find out which slow it is
“Lightroom is slow” covers five different problems, and each one shows up in a different place. Match the symptom before you change anything.
- Catalogue: the whole app drags, in every module, and it got worse slowly over months of imports.
- Cache: Develop is slow to load each new photo, but a photo you edited a minute ago opens fast.
- GPU: sliders lag behind the mouse, the image flickers or draws wrong, or Denoise takes minutes per frame.
- Storage: everything that touches the disk stalls (imports, previews, exports), and the drive is close to full.
- RAM: Lightroom is fine alone and falls apart the moment Photoshop and a browser are open next to it.
The first two cost nothing to fix. The GPU one sometimes costs nothing (a driver), and the last two are where a purchase might come in.
The fixes, in the order I’d run them
Every step below is from Adobe’s own Optimize Lightroom performance page, in Adobe’s wording where the wording matters. The order is mine: biggest effect for the usual complaint first. That page was last updated June 17, 2025, so where it disagrees with Adobe’s newer requirements page, I say so.
1. Put the catalogue, previews and photos on an SSD
Adobe wants the catalogue, the previews and the image files on a solid-state drive. The catalogue is a database Lightroom reads constantly in small pieces, and a spinning disk is slowest at exactly that kind of read. Two rules come with it. The catalogue can’t live on a network drive (your photos can), and the drive holding it needs at least 20 percent free space. A drive at 95 percent full is slow no matter how fast it was new.
Keep the catalogue file and its Previews.lrdata folder together in the same folder. If you move one, move both, then open the catalogue from its new location.
2. Raise the Camera Raw cache
The Camera Raw cache holds the partly processed data Develop needs to open a raw file. The default is 5 GB. Adobe’s steps say to set it to 10.0 GB or more. I’d go straight to 20 GB or higher if the drive has room. Put the cache on the fastest internal disk you have, not an external. The same page says why the bigger number is worth it: “some Lightroom Classic users find that increasing the Camera Raw cache to 20 GB or more can dramatically speed up performance in the Develop module.”
3. Build previews before you cull
If Lightroom builds previews while you scroll, every click waits on a render. Build them up front instead. Choose 1:1 in the import dialog. For photos already in the catalogue, run Library > Previews > Render 1:1 Previews and go make coffee.
Then size the Standard previews to your screen. Adobe’s example is 2048 pixels for a 1920×1200 display: the setting closest to the long edge of your monitor, with preview quality on Low or Medium. Bigger than the screen is wasted render time. Set 1:1 previews to discard after 30 days, or Never if the disk has the space.
4. Update the graphics driver, or switch the GPU off
Lightroom Classic leans on the graphics card for the Develop display and the AI tools, so a stale driver is a common cause of lag and drawing glitches. Update it first. If the card is incompatible, Adobe’s fix is to uncheck Use Graphics Processor in Preferences > Performance. Lightroom then runs without the card, which beats a card it can’t drive.
5. Optimise the catalogue
Run File > Optimize Catalog. Then make it automatic: when the backup prompt comes up on exit, tick Test Integrity Before Backing Up and Optimize The Catalog After Backing Up. A catalogue that’s been through years of imports and deletions carries a lot of dead weight, and this clears it on every backup without you thinking about it.
6. Pause sync while you work
If Sync With Lightroom is on, it uploads in the background while you import and edit. Adobe’s advice is to pause it during those sessions and let it catch up later.
7. Leave XMP auto-write off
With automatic XMP writing on, Lightroom writes a sidecar file every 10 seconds for the photo you’re working on, and pauses those writes during import. Leave it off unless another app needs to read your edits, and write XMP by hand when it does.
8. Clear the History panel and trim your presets
Adobe’s advice is to clear the History panel on images you’ve finished with. Presets add load too, and Adobe says the slowdown is strongest past 2,000 presets. If you bought five preset packs and use two, remove the other three.
9. Edit in Adobe’s order
The order you apply edits changes how much work Lightroom redoes. Adobe’s sequence starts with Denoise, Raw Details and Super Resolution. Next come Reflections Removal, Distracting People Removal, Generative Remove, Content-Aware Remove, Heal and Clone. Then Lens Blur, Lens Profile, Crop and Transform, Adaptive Profiles and global adjustments, with masking last.
One more free check: the version. Puget Systems documented a DNG export regression in Lightroom Classic 15.0 that 15.2 mostly fixed, so a slow export deserves a version check before you blame the hardware.
When it is the hardware
If all nine are done and the symptom is still there, the symptom names the part. Adobe’s Lightroom Classic system requirements page (last updated October 27, 2025) is the reference for the numbers below.
RAM: slow with other apps open
Adobe’s two pages disagree on memory. The system requirements page lists 8 GB as the minimum and recommends “16 GB or more”. The older Optimize Lightroom performance page still says 12 GB. Go by the requirements page, and treat 16 GB as the floor. In Puget’s June 2026 testing, Lightroom Classic scored 45 percent lower with 16 GB than with 64 GB. I’d buy 32 GB for a photo machine, and the reasoning plus the current kit prices are in how much RAM you need for editing. On a Mac the memory is fixed at checkout, so that decision happens when you buy the computer.
GPU: Denoise and AI masks crawl
The graphics card matters most for Denoise, Lens Blur, Reflection Removal and the AI masks. Adobe’s requirements page asks for “8 GB of dedicated GPU memory or 16 GB of shared memory for full GPU acceleration and AI features such as Denoise, Lens Blur, and Reflection Removal” on Windows. That figure is for full acceleration and the AI features. To drive a 4K or larger display, the page asks for 4 GB of GPU memory. On a Mac the same page lists an Apple silicon GPU, M1 or later, and 16 GB of unified memory. That covers full GPU acceleration and AI features such as Denoise, Lens Blur and Reflection Removal. If your card is under 8 GB and you denoise every shoot, that’s the upgrade; my GPU guide covers the cards worth buying.
Storage: the catalogue drive is full or slow
If the catalogue sits on a SATA drive that’s nearly full, or on a spinning disk because the internal one ran out, a dedicated NVMe drive for the catalogue, previews and Camera Raw cache fixes all three at once. The originals can live on a cheaper external; Lightroom only reads them when a photo opens or exports. The NVMe drive I run, and a bigger-capacity alternative, are in my NVMe SSD post. If Photoshop is complaining at the same time, the scratch disk full fix is the same problem from the other app.
The whole machine: old CPU, no upgrade path
Lightroom Classic wants a 64-bit CPU with AVX2 support. Adobe’s performance page puts the benefit at “up to six cores.” Puget’s March 2026 analysis of version 15.2 found most of the app lightly threaded. So a fast single core does more for a photographer than a big core count. Export and the AI features are where cores and the GPU pay off. If the machine fails on CPU and can’t take more memory, replace the machine. My picks: the best PC for photo editing, the best Mac for photo editing and the best laptop for photo editing.
What I changed on my machine
I edit on a Mac, so memory and GPU were settled the day I bought it. What I could change was where things live. The catalogue, its previews and the Photoshop scratch disk sit on the internal SSD, where the small database reads that make the Library module feel fast are quickest. The original raw files live on an external SSD, because Lightroom only touches them when a photo is opened or exported. It’s the same split I use for video: project files and cache inside, heavy media outside.
After that, the order is the one above. Check where the catalogue is and raise the cache. Set the Standard preview size to the display and render 1:1 on import. Then let the optimise-after-backup box run every time I quit. When a new version lands, I read the release notes before I touch anything else.
FAQ
Why is Lightroom Classic so slow on a new computer?
Usually because the catalogue came along from the old machine with its old settings: a 5 GB cache, previews building on demand, sometimes the catalogue still on an external drive. Run the first three fixes above before you suspect the new hardware.
Do smart previews make Lightroom faster?
Adobe’s performance page doesn’t list them as a speed fix. Smart previews let you edit when the originals are offline, which is handy on a laptop, but for speed the 1:1 and Standard preview settings are the ones that matter.
Should I turn off GPU acceleration?
Only if the card is incompatible or the driver update didn’t fix the glitches. On a supported card, leave it on: Denoise and the AI masks need it.
Is the cloud Lightroom faster than Lightroom Classic?
They’re built for different workflows, and the speed question is the smaller part of picking one. The trade-offs are in Lightroom Classic vs Lightroom.
And that’s it
SSD for the catalogue, a bigger cache, previews built before you cull. Then the driver and the optimise box. Only after those does the part list come out, and the symptom tells you which part. As always, what you see here is what works for me, my clients and my crew.








