Lightroom Denoise: how to use it, and why it's so slow
Quick Answer
Lightroom Denoise is AI noise reduction for raw files. Since Lightroom Classic 14.4 it's a checkbox at the top of the Develop module's Detail panel: tick Denoise, wait for the first pass, then set Amount (it starts at 50). It no longer creates a separate DNG. It won't run on JPEG, HEIC or TIFF, and its speed depends almost entirely on your graphics card.
You shot a reception at ISO 6400, or the Milky Way at ISO 3200, and the old Luminance slider turns faces to wax before the grain goes away. Lightroom's Denoise fixes that better than anything Adobe shipped before it. It's also the feature most tutorials now describe wrong.
Adobe rebuilt it in June 2025. The Enhance dialog is gone, Denoise no longer writes a new DNG, and the result is stored with your catalog instead. Plenty of guides were written before that change and still send you to Photo > Enhance to wait for an "-Enhanced-NR.dng" that never appears. This one covers the current version, Lightroom Classic 15.6 (September 2026), plus the parts the quick tutorials skip: which files it refuses, why a batch of 300 wedding photos can still take the better part of an hour, and where all that data ends up on your disk.
What does Lightroom Denoise do, and which files does it work on?
Denoise is a trained AI model, not a blur. The manual Noise Reduction sliders average neighbouring pixels together, so grain and fine texture go away at the same rate. Denoise was trained on pairs of noisy and clean images, so it predicts what the clean detail should look like and rebuilds it. At 100% you see the difference in eyelashes, fabric weave and feather edges, the places where the sliders used to turn everything to paint.
It was built to work on raw sensor data, before Lightroom turns the file into finished RGB pixels. That's why the file type decides whether the checkbox is even clickable:
| File type | Denoise? |
|---|---|
| Bayer and X-Trans raws (Canon, Nikon, Sony, Fujifilm and most others) | Yes |
| Apple ProRAW, Samsung Expert RAW, Canon sRAW/mRAW, Nikon small raw | Yes, in current versions |
| Linear DNGs, including HDR and panorama merges made in Lightroom | Yes |
| Smart Previews (when the original is offline) | Yes |
| Monochrome raws (Leica M Monochrom), Foveon, Pentax Pixel Shift, Sony ARQ | Yes |
| JPEG, HEIC, TIFF, PSD, WebP | No - the checkbox is greyed out |
Several of those "yes" rows are recent. When Denoise launched in Lightroom Classic 12.3 (April 2023) it rejected sRAW and ProRAW files, and a lot of forum answers still say so. Adobe's current list includes them. JPEGs are still out. For those you have the manual sliders or a third-party tool (more on both below). Super Resolution in the same panel does accept JPEG and TIFF, but it doubles the resolution; it isn't noise reduction. A merged HDR is a linear DNG too, so Denoise runs on it; here is how Lightroom Classic's HDR merge works if you shoot brackets.
Where is Denoise in Lightroom Classic now, and how do you apply it?
It lives in the Develop module, at the top of the Detail panel, above Sharpening and Manual Noise Reduction. If you're hunting for it under Photo > Enhance, that's the pre-14.4 route, and the dialog it opened no longer exists.
- Select a raw photo and open the Develop module (press D).
- Expand the Detail panel in the right-hand column.
- Tick Denoise. Lightroom computes the first pass, which takes a few seconds to a few minutes depending on your graphics card.
- Zoom to 100% on a shadow area and adjust Amount. It starts at 50.
- Carry on editing. The original raw is never touched, and you can untick Denoise at any time to switch it off.
Denoise first, then masks and Remove
Adobe's own advice is to denoise before you build AI masks or use Remove, because those tools read the pixels Denoise changes. Select Subject and Select Sky find edges in the visible image. On a noisy frame the mask edge follows the grain, which gives you ragged halos around hair, fur and foliage. Run Denoise, then build the masks on the clean image. Brush masks don't care either way, since they follow your painting, not the pixels. (More on how the AI masks find edges in my guide to Lightroom Classic's masking tools.)
How much Denoise should you use?
The Amount slider starts at 50 on every photo, and Lightroom doesn't remember the value you used last. So once you settle on a number for a shoot, copy it across (next sections) instead of dragging the slider on each frame. These are the ranges I start from:
| ISO and what you see | Amount |
|---|---|
| ISO 800-3200, fine grain in the shadows | 25-40 |
| ISO 3200-6400, visible color noise | 50-65 |
| ISO 6400-25600, heavy noise | 70-85 |
| Above ISO 25600 | 85-100 |
Two caveats. Sensor size matters more than the ISO number: a Micro Four Thirds file at ISO 3200 can need what a full-frame file needs at 12800. And when skin starts to look airbrushed or leaves turn into brush strokes, you've gone too far. Back off by 10 and check again at 100%, because at fit-to-screen almost any amount looks clean.
Why is Lightroom Denoise so slow?
Because nearly all the work happens on your graphics processor. Adobe calls Denoise "a GPU-intensive feature", and photographers who benchmark it on the Adobe Community forums find that CPU and RAM barely move the result. A five-year-old laptop with integrated graphics and a new desktop with a current graphics card can be twenty times apart on the same file.
Rough times per photo, from the Adobe Community Denoise benchmark thread and similar user reports:
| Hardware | Time per photo |
|---|---|
| Fast current card (an RTX 5070 Ti, for example) | About 10-15 seconds |
| Apple M2 Max, 45 MP raw | About 15 seconds |
| Older mid-range card (Radeon RX 6700) | About 30 seconds |
| Older or entry-level graphics, 60 MP raw | 1-3 minutes, sometimes more |
Time scales with megapixels, so a 24 MP file takes roughly 40% as long as a 60 MP one on the same machine. Multiply by a 300-photo wedding and even 12 seconds a frame is an hour. A few things actually help:
- Update your graphics driver. It's the most common fix on the forums for both slow and failing Denoise.
- Check Preferences > Performance. Lightroom should list your graphics card there and not report it as unsupported.
- On Apple silicon, run 15.4 or later. The June 2026 release added Apple Neural Engine support to speed Denoise up.
- Turn off automatic XMP writing during big batches. Since 14.4 a denoised photo's sidecar can grow past 10 MB, and users have filed bug reports that writing those files bogs down large Denoise runs. Untick Catalog Settings > Metadata > "Automatically write changes into XMP", run the batch, then switch it back on.
How do you denoise many photos at once?
There's no batch Denoise button anymore. Since 14.4, Denoise is an ordinary develop setting, so you batch it the same way you'd batch any slider:
- Auto Sync, Adobe's documented route: select the photos in Develop, flip the switch on the Sync button to Auto Sync, then tick Denoise. Every selected photo gets it.
- Sync: set up one photo, select the rest with it as the active photo, click Sync and make sure Denoise is included.
- Copy and paste: Cmd/Ctrl+Shift+C on the finished photo, then Cmd/Ctrl+Shift+V on the selection. I cover the dialog in how to copy develop settings in Lightroom Classic.
- A develop preset with Denoise saved in it, applied in the Library or at import.
One catch with import presets: the AI part doesn't run during import. Select the photos afterwards and choose Photo > Develop Settings > Update AI Settings to compute it.
Every photo still gets its own full GPU pass, so batching saves clicks, not time. What did change is waiting: since 15.3 (April 2026) these batch runs work in the background, so you can keep culling or editing while they grind. On 14.4 through 15.2 a big batch held up the whole app until it finished. To find every photo you've denoised later, use the Library Filter's Metadata filters (under Develop, choose Has Denoise) or a Smart Collection with the same rule.
Does Lightroom Denoise still create a DNG?
No. From 12.3 to 14.3, Denoise wrote a brand-new linear DNG next to the original, with "-Enhanced-NR" added to the file name, and stacked it with the raw. You then edited that DNG, not the raw. Since 14.4 (June 2025) Denoise is non-destructive: the raw stays untouched, there is no second file, and the computed result is stored with your catalog.
Lightroom Classic 12.3 to 14.3
Noisy raw
Original file
Lightroom Classic 14.4 and later
Noisy raw
Never modified
Adobe hasn't published exactly where that data goes. Photographers who measured it on the Adobe Community forums found it in the .lrcat-data folder next to your catalog (the same place AI masks and Remove results live), in the .lrcat itself, and in the XMP sidecar when automatic XMP writing is on.
What it costs in storage
Much less than the old DNGs, which were full-resolution linear files and usually far bigger than the raw. But not nothing. Numbers users posted after upgrading:
- Sony A7R III (42 MP): about 11.6 MB of Denoise data per photo in
.lrcat-data, and XMP sidecars averaging about 15 MB. - A 24 MP shoot: sidecars went from about 14 KB each to about 13 MB.
- One catalog went from 320 MB to 8 GB after a backlog of photos was denoised on 14.4.
I build Lightroom Classic plugins, so I spend more time than most people inside catalogs and sidecars, and this is the part I'd act on first. Three things follow from it:
- Back up the
.lrcat-datafolder with the.lrcat. If it goes missing, your settings survive, but Lightroom has to recompute every Denoise and AI mask, and on a big catalog that's hours of GPU time. My catalog backup guide covers the rest of what a backup should hold. - Keep the catalog out of Dropbox, iCloud Drive and OneDrive folders. Forum threads about AI masks that keep needing an update often trace back to a synced folder corrupting
.lrcat-data. - Check your old -Enhanced-NR DNGs. Files from 12.3-14.3 are still on disk. If you've since run Denoise on the original raw, the DNG is a duplicate; check it carries no edits you want before you remove it.
Need a file with the Denoise baked in, for Photoshop or another app? Export a TIFF or JPEG, or use Edit In, which renders it for you. Since 15.5 (August 2026) you can also right-click a photo and choose Render to DNG, which writes a new DNG with all your current edits locked in.
Lightroom Denoise not working? The usual causes
| What you see | Cause and fix |
|---|---|
| Denoise checkbox greyed out | The file isn't raw (JPEG, HEIC, TIFF, PSD). Check the file type in the Metadata panel. Use Manual Noise Reduction instead. |
| Denoise disappeared after an update | It moved. Look for the checkbox at the top of the Detail panel, not under Photo > Enhance. |
| "Denoise model version mismatch" error | Camera Raw 18.4 shipped new Denoise models, and Lightroom Classic 15.3 or earlier can load them by mistake. Update Lightroom Classic to 15.4 or later (Adobe's note on it). |
| Fails or crashes on every photo | Update the graphics driver first. Adobe staff on the forums also suggest emptying Camera Raw's "ModelZoo" folder and restarting, so the models download fresh. |
| Applied with an import preset, nothing changed | Photo > Develop Settings > Update AI Settings. |
| Lightroom crawls during a batch | Your GPU, plus automatic XMP writing (see above). On 15.2 or earlier, update for background processing. |
AI Denoise vs the manual Noise Reduction sliders
Manual Noise Reduction (Luminance, Detail, Contrast, Color, Smoothness) still sits right under Denoise in the same panel. It renders instantly, adds no data to your catalog, and for ISO 800-1600 on a modern sensor it's often indistinguishable from Denoise at normal viewing sizes.
| Situation | Use |
|---|---|
| ISO 3200 and up, visible color noise | Denoise |
| Low light with fine texture (hair, fabric, feathers) | Denoise |
| ISO 100-800, mild grain | Manual, or nothing |
| You want to keep a film-grain look | Manual |
| JPEG, HEIC or TIFF | Manual (Denoise won't run) |
| Thousands of photos and limited disk space | Manual for the keepers that don't need more |
My rule is simple: if the manual sliders visibly smear texture at 100% before the noise is gone, that photo gets Denoise. Everything else doesn't need it.
Lightroom Denoise vs Topaz and DxO
Lightroom's Denoise is good enough that most photographers can skip a separate app. The two main alternatives earn their keep at the edges:
- DxO PureRAW processes raws with its DeepPRIME models and applies lens-specific optical corrections. Many reviewers still rate it a notch ahead at very high ISO, and it's a one-time purchase. The catch is the round trip: it writes a new DNG that you then edit in Lightroom, which is the extra file Adobe just got rid of.
- Topaz Photo (the old Photo AI) handles denoise, sharpening and upscaling, and unlike Lightroom it works on JPEGs. It has been subscription-only since September 2025.
Start with Lightroom's Denoise. Reach for DxO or Topaz only when a specific frame still falls apart at 100%, or when all you have is a JPEG. I compare both alongside other editing add-ons in my roundup of Lightroom Classic plugins.
And if you came here from a pre-14.4 version, do one thing today: open your backup folder and check that the .lrcat-data folder is in it.