Processor and graphics card specifications are live

Problems · Under load

Why is my laptop slow in Lightroom or Photoshop?

Photo work is several different workloads wearing one name, and they bind in different places. Browsing a catalogue is storage and cache. Rendering raw previews is processor. Layered composites and large canvases are memory. Exporting a batch is sustained processor and cooling.

Identify which of the four is slow before changing anything, because the fix for each is different and only one of them is helped by a faster processor.

First, notice when it happens

From the first minute

Sluggish browsing, brush lag and slow panel switching are storage, cache and memory problems, felt instantly and unrelated to cooling.

Only after minutes of use

Batch exports run long enough to reach the thermal limit, which is where a thin laptop settles and a well-cooled one keeps going.

The causes, ranked

1. Memory pressure on large files

most common

How to confirm it

Large layered documents, high-resolution panoramas or many images open at once, with the machine swapping. 16GB is tight for serious work.

The fix

Close other applications, flatten what you can, and treat 32GB as the target on any replacement. This is the most common single constraint in photo work.

2. Cache and scratch on slow or full storage

most common

How to confirm it

Slow catalogue browsing and long waits when switching images, especially with cache on a mechanical or nearly full drive.

The fix

Put the cache and scratch space on the fastest drive with real free space, and give the catalogue cache a generous size. Free, and often transformative.

3. Previews not built in advance

common

How to confirm it

Every image renders from raw as you reach it, which is why browsing feels slow while exporting seems fine.

The fix

Build standard previews on import and let it run while you do something else. This converts constant small waits into one large one you can ignore.

4. Thermal settling during batch exports

common

How to confirm it

The first images in a batch export faster than the last, with the fans at maximum.

The fix

Cooling ladder and mains power. Batch exports are a sustained load and behave exactly like any other.

5. Graphics acceleration misbehaving

common

How to confirm it

Brush lag, slow zooming or interface glitches that change when acceleration is toggled in the application's preferences.

The fix

Update the graphics driver first, then test with acceleration off. In photo applications this setting causes a surprising share of interface complaints.

6. A catalogue that has grown unwieldy

occasional

How to confirm it

Slowness that grew with the catalogue rather than with the images, and improves after optimising it.

The fix

Optimise the catalogue and consider splitting very large ones by year. Maintenance rather than hardware.

Measure it instead of guessing

Run the deep test if exports are your complaint, since that is the sustained part of photo work and the settled level predicts batch times directly. If browsing rather than exporting is slow, the test will look healthy, and that healthy result is itself the finding: the constraint is storage or memory rather than the processor.

What software cannot tell you here

  • We cannot see your cache settings, catalogue size or file dimensions, which the application's own preferences report.
  • We cannot measure storage speed, which a disk benchmark answers.

Asked, in people’s own words

How much RAM do I need for photo editing?
16GB is the working floor for raw editing, and 32GB is the comfortable level for large layered composites, panoramas and high-resolution work. Because memory is soldered on most laptops, buy one tier above your current work rather than planning an upgrade you probably cannot make.
Does a graphics card help with photo editing?
For specific accelerated operations and for interface smoothness, yes, but far less than memory and storage. Photo work is memory and storage bound far more often than it is graphics bound, which is why a modest machine with plenty of memory often outperforms a powerful one without.
Why is Lightroom slow but Photoshop fine?
Because they stress different things. Lightroom's catalogue browsing is storage and preview bound, so a slow or full drive and unbuilt previews hurt it specifically. Photoshop leans on memory and works from files already open. Slow in one and fine in the other is a useful clue rather than a contradiction.

Name the cause. Three and a half minutes, in the tab you have open.