Lightroom Classic

Introducing Assisted Culling (Early Access) in Lightroom Classic. For providing feedback for Lightroom Desktop, click here.  TL;DR – Assisted Culling is getting faster, more powerful, and more accurate as we head to GA. If you tried in October 2025, we urge you to try the new version and give us feedback – especially for wedding & portrait photographers. We’re eager to hear your feedback!  Assisted Culling has received several updates since Early Access launched in October 2025. If you tried it then, here's what's new:  April 2026  Significantly improved handling of shallow depth-of-field for photos – a major customer ask. Images with intentional background blur are now more reliably recognized and kept rather than rejected as out-of-focus.  We’ve retrained the “Reject model” so it has more accurate identification of reject-worthy images. Additionally, an image can now be flagged under multiple reject reasons simultaneously:  Exposure Issues: includes a sensitivity slider so you

For several versions, optimizing and saving the catalog has taken a lot of time (for 85,000 photos, it now takes more than 30 minutes, whereas it took 5 minutes about 2 years ago) and the situation is getting worse.I haven't changed hardware, disk, save location, ...Do anyone see the same problem?I was told about a possible connection with the use of AI for denoising, is this a clue?

I have applied Auto in the develop module then selected denoise and this error occurs.

Hello, I haven't been able to find an answer on how to change the default values of the sliders in the presets within the masks. I can only find the option to “Save current settings as new default”I don't want to create a new preset default.Also, how can I delete or rename a mask presets? Regards  

Hi everyone,I’ve been experiencing an ongoing issue with Adobe Lightroom Classic, currently on version 15.2. This problem has been happening for the last three updates, not just this latest one.After importing RAW files, the thumbnails do not appear in the Library module. The folder and total file count display correctly, but the preview area remains blank.The only workaround that consistently works is fully restarting Lightroom. Once I relaunch the program, all thumbnails appear normally.System details: Lightroom Classic version: 15.2 Computer: Apple M3 Pro Memory: 18GB RAM GPU acceleration: Set to Auto File type: RAW “Generate previews in parallel”: Enabled Storage: [internal SSD or external drive] This happens every time after import. Restarting fixes it temporarily, but having to do that after every import is not practical.Has anyone else experienced this over the last few updates?Is this a known issue with Apple Silicon machines?Is there a more permanent solution besid

When I want to skip through hundreds or thousands of photos in Lightroom Classic (Version 15.0.1) in the film strip I mostly get this very annoying problem: after holding the arrow key to the right or left for a few seconds it doesn't stop anymore to speed through the images though I'm no more holding the arrow key. Sometimes it's going on for "just" a couple of hundred further photos and sometimes even through thousands of photos until the very last photo in the strip. I can't even stop it.This first started three months ago when I updated on a new MacBook. On my old Macbook this never happened in years. Does someone got an Idea to fix this bug?

Hi Adobe Team, I’m posting this as a clear performance regression report for Lightroom Classic v15.x — specifically the Develop module image-to-image switching latency on Mac. REALLY SLOW. Please do not merge this thread into a generic “performance” megathread and then mark it as “Solved” as if nothing happened. Multiple users are reporting the same behaviour, and it deserves a proper investigation and acknowledgement (instead of being dismissed as an “NVIDIA driver” issue — this is Apple Silicon). What’s happening On Lightroom Classic v15.2, switching between photos in Develop is several times slower than in previous versions. This is not a minor “feels slower” issue — it’s a real, repeatable regression that drastically impacts professional workflows. My setup  MacBook Pro (M3 Max) macOS v26.2 Lightroom Classic v15.2 Preferences → Performance → Graphics Processor: ALL acceleration options manually enabled (not Auto)  Proof / Reproduction To remove any subjectivity, I recorded sc

Mais alguém com problemas a exportar slideshow no adobe lightroom?

Lightroom Classic crashes consistently during its built‑in catalog backup at the “Copying catalogue” stage.Crash detailsException: EXCEPTION_ACCESS_VIOLATION (0xc0000005) Faulting symbol: AgRedeye_load Crash occurs during catalog copy only Editing itself is stableEnvironmentLightroom Classic 15.2.1 Windows 11 Pro build 26200 NVIDIA RTX 3080 (driver 32.0.15.8195) Catalog size ~5 GB Catalog on internal NVMe SSD (not OneDrive, not USB) Backup destination on local SSDReproducibility100% reproducible.What has already been testedPreferences reset Full uninstall / reinstall of Lightroom Classic All plugins disabled GPU enabled and disabled Multiple backup destinations No sync or backup software running Manual catalog copies succeed (workaround confirmed)Crash persists in all cases.RequestThis appears to be an internal Lightroom Classic defect.Please escalate to engineering — multiple identical crash reports are available.(Crash report XML available on request.)

W tym oknie jest błąd w tłumaczeniu na język polski. Powinno pisać “Usuwanie kurzu” a nie Dust Removal 

I’ve just updated to the April 2026 version of LR classic. When I launch it on Windows 11 I can see it is running when I look at task manager and it has created the .lock file. But nothing displays on my screen. When I end the task in task manager and delete the lock file and try and launch it by clicking on my last catalog file the same thing happens. I’ve tried resetting the preferences file when launching but again nothing appears on my screen. How can LR be running yet I can’t interact with it?

Issue summaryOn my Mac, Lightroom Classic 15.3 becomes unresponsive after some period of normal use. I have to Force Quit it. After that, Lightroom Classic can relaunch, but RAW files can no longer be opened properly. I cannot guarantee exact reproduction steps every time, but the issue has happened multiple times in 15.3 and has not happened for me in 15.2.1 on the same machine.Environment- Lightroom Classic: 15.3- macOS: 26.4.1- Apple Silicon Mac: M1 MaxWhat I can confirm- This issue started after updating to 15.3.- It happens after some time of normal RAW workflow use, not immediately on launch.- Once Lightroom hangs, I have to Force Quit it.- After relaunch, RAW files still cannot be opened properly.- Downgrading to 15.2.1 on the same Mac resolves the issue.  Relevant lines from the report:Process:      Adobe Lightroom Classic [12526]Version:      15.3OS Version:      Mac OS X 26.4.1 (25E253)Exception Type:      EXC_CRASH (SIGTERM)Signal Number:      15Publisher Process Name:      

This happened in Lightroom Classic, says "Generative Remove Failed. We've encountered an issue and can't complete your request at this time. Please try again later." 

Using LR Classic 14.1.1 on MacBook Pro 15.1.1 with 64 GB sometime in the last couple of updates I noticed two things.Frirst the Right arrow (orCtrl R arrow ) does not work to advance in the Develop module.  The film strip advances but the full screen display does not.Second, the full image had not been updated with the prior edits.Once I went back to Library and advanced the images,  THEN opened the Develop module often the edit history would not be applied or there was a noticeable lag - the original raw image displaying and then the edits would be applied. A good percentage of the time, I would have to go back and click on the history to update the image in the Develop module.Once the edits were applied from the history, the right and left arrows worked in the develop module. It may be that the R & L arrow problem in the Develop module is due to a disconnect in finding and applying the edit history.I worked with Adobe support and nothing they did fixed th

Windows 11 x64Two monitors attached via DisplayPorts on same graphic cardLr > Preferences > Display > Secondary window > Right side monitor selectedLr primary window opens on left monitor and secondary loupe view open on right monitor as expected.If Lr main window is minimized or another app is brought in front of Lr on the main (left) monitor and other app is opened on the right monitor, when focus returns to Lr the secondary Lr window moves to the main left monitor.  There is no way to access the main Lr window to disable the second display menu.  The Lr secondary window sticks in front of the primary window on the left side monitor.

The Zoom feature in lightroom has started to behave strangely.  If I click on the 100% option, rather than zooming it reduces the image so that it fills approximately 50% of the workspace.  If I then select a lower zoom level (say, 50%), the image is reduced further.  I can only zoom by selecting a value such as 200% or higher, but it is hard to say what zoom level that actually corresponds to. What's going on here?  Thanks.

The behavior of importing with LRC seems to have changed (for the worse) recently.   I want to import a TIFF file that surely is somewhere in my catalog, though I do not know exactly where.   A copy of the TIFF file is in a folder on my desktop  but what I need is a JPEG file.   I want to derive a JPEG file from that TIFF file. But when I try to import that TIFF file, the new import dialog simply provides me no way to import it , apparently because it is already somewhere in my catalog (thought it does not say where).  In what seems to be a new import dialog, it does not even display the file extention (which would be a big convenience).  If I filter for files ending in .tif, no files are displayed though I know for certain there are several .tif files in the folder.  

Lightroom has become cripplingly slow. I have tried a number of things to no avail. My set-up:Dell PC xps 8940 Intel Core i9-10900cpu @2.80 32g ram Intel uhd graphics 630 Nvidia GeForce RTX 2060 super I keep my photos on an external WD drive. It's 5 Tb. I use 2.95 and have 1.58 free. Things I have already tried:Created a new catalog Reset my preferencesUpdated all drivers. Tested all the drives/processors I could for any issues. Everything returns as being good. I even refreshed my PC and then reinstalled everything. Still nothing.  I can't help but think that the issue has to do with conflicts between LRC and LR Mobile. I don't have much to base that on other than I have been using a tablet to cull photos and the my system seemed to slow when I did that. It really broke when I tried to import ~1k photos from LR mobile into my old catalog a few weeks ago. I ended up creating that new catalog. It was so bad that that is why I created the new catalog. Right now, for example, I'm trying t

HELP updated LR classic yesterday to newest update now can't view or edit anything in my catalog and images can't be viewed all greyed out can't import any either won't shut down I have to force it  using Mac studio 

Hello,Am I the only one having issues with LrC's masking? As shown in the screenshot that's attached, the mask no longer fully covers the object. There also seems to be an issue with the feathering of the mask, making a distinct line between what is and isn't part of the mask. I've been having various problems for months (this is not my first posting regarding masking), This is what I believe keeps getting my stock images refused. I'm getting frustrated. Everything started going wrong after a recent update. Please fix this issue, Adobe!This image has only been processed in Lightroom Classic, the most recent version as I'm a monthly subscriber. Not sure what other info you might need, but I use a windows based desktop.Thanks for any insight you can provide.

Since the latest versions of Lightroom Classic and MacOS the masking of people always shows “No people found” – even on photos where it was working before. Lightroom Classic version: 15.2 [ 202602111402-ec4112e8 ]License: Creative CloudLanguage setting: en-DEOperating system: Mac OS 26Version: 26.3.0 [25D125]Application architecture: x64Logical processor count: 24Processor speed: 3,3GHzSqLite Version: 3.36.0Adobe GSDK Version: 1.4.0.171Built-in memory: 196.608,0 MBDedicated GPU memory used by Lightroom: 4.743,3MB / 16.368,0MB (28%)Real memory available to Lightroom: 196.608,0 MBReal memory used by Lightroom: 3.040,3 MB (1,5%)Virtual memory used by Lightroom: 55.303,7 MBMemory cache size: 62,7MBInternal Camera Raw version: 18.2 [ 2482 ]Maximum thread count used by Camera Raw: 5Camera Raw SIMD optimization: SSE2,AVX,AVX2Camera Raw virtual memory: 631MB / 98303MB (0%)Camera Raw real memory: 644MB / 196608MB (0%)Cache1: Final1- RAM:519,0MB, VRAM:1.818,0MB, ALP05331.ARWNT- RAM:519,0MB, VRAM

OM System has HR modes.  Hand held (HHHR) and tripod (THR).  HHHR uses camera movement to create a composite whereas THR is true sensor shift.  For both modes, the camera can produce a HR jpeg and a HR raw (.ORF).  It also produces a normal resolution raw tagged as .ORI.This was problematic for LrC but it appears to be resolved albeit partially.  LrC will import the jpeg, the ORF and the ORI. However, if “Copy as DNG” is specified, the normal res ORI is converted to a DGN but the HR ORF remains as an ORF.  This is strange in itself but often, not always, the thumbnail of the HR raw is tagged with “Photo is missing” and an exclamation mark.  Sometimes this crashes the app.  Attempts to read the missing file fail.

I am using lightroom classic 14.3.1 right now and recently I want to rebuild my catalog so I created a new one and trying to import the photos from NAS (local network). For the first several thousand it was okay, but after that, the import seems impossible anymore. I break the job and trying to just sync one folder with several hundreds photos. Everytime it might work for the first several and then stucked (no matter whether i restart the application or restart the job or optimize the catalog, nothing helps).  Does anybody know why and how to solve this? The attached screenshot shown when there was no progress anymore how the import bar looks like.

For the past several months, when I auto-process images in Develop, I get unwanted color highlights, usually bright red or blue, in the image.  If I save the images outside Lightroom, these highlights disappear, but they’re still very annoying when examining images inside Lightroom.  The only way I’ve found to mostly get rid of them is to adjust White and Black tonal values to zero.  Even then, some stray color may persist.  But...maybe I want blacks or whites? Any suggestions for killing this “improvement” in Lightroom Classic?