Lightroom Classic

MacBook Pro M3 Pro and MacBook Pro M5 Max MacOS 27.0.1 aka Golden Gate I have a catalog i made for test purposes this June containing 109 Nikon Z8 non compressed photos.When i tick the Denoise box runtime is 3 seconds, great!However, if i make a new catalog with the same 109 photos then runtime is 11 seconds :-(I did many test and catalogs and same happen, denoise time is 11 sec on the M5 Max and 17 sec on the M3 Pro what is not surprising.It seems to me that the catalog who does denoise in 3 seconds have the photos only in a collection as but no photos are shown on disk. See the attached screenshotNow i am a bit confused about why i can edit photos if the original is not on the disk but in a collection ?Exporting the edited photo i get a warning window saying, but export works perfectly fineSo from what i understand in this case i work with smart previews instead of the original file.What i am wondering why is the Denoise time for Smart Preview so much faster; 3 seconds instead of 11

Version: Lightroom Classic 15.5.0.8OS: Windows 11 Pro (build 10.0.26100)GPU: NVIDIA RTX 3090, driver 32.0.16.1088 (22/07/2026)RAM: 32 GBRepro: Run Assisted Culling / auto-stack-by-similarity on a large batch of photos. Crashes reproducibly — 5 identical crashes since 2026-08-09.Crash signature: Windows Application Error log shows Lightroom.exe faulting in ntdll.dll, exception code 0xc0000374 (STATUS_HEAP_CORRUPTION), consistently at the same fault offset (0x112165) across all occurrences.Context: App log shows the last command before each crash was ag.library.stacking.generateAutoStacksBySimilarity. Lightroom's process memory usage reached 13.5–14.6 GB (41–45% of system RAM) just before crashing, suggesting a memory-handling bug in this feature on larger culling batches. 

Assisted Culling is now generally available in Lightroom ClassicTL; DR: Assisted Culling has graduated from Early Access to General Availability. It gives you a fast, reviewable first pass on large shoots: it surfaces your strongest frames and sets aside the obvious rejects, so you spend less time comparing near-duplicates. You stay in control: review everything, adjust the thresholds, and override any call. If you tried it back in October 2025, it's substantially more accurate now, especially for wedding, event, group, and portrait work. We'd love for you to give it another look and tell us what you think in this thread.  What it does Open an album or collection, run a cull, and Assisted Culling analyzes your images against the criteria you choose: Subject Sharpness, Eye Sharpness, Eyes Open, exposure, and more. It marks Selects and Rejects, shows you why behind every call, and leaves the final decision to you. How far it's come since Early Access  February 2026: Expanded from individ

Since a few weeks, my Lightroom Classic (15.3.1 release on macOS Tahoe 26.5.1) gets stuck or stops responding on simple tasks like:Building standard or 1:1 previews (it gets stuck on ‘Building previews: 3 of …’ but never actually creates one preview) Photo Merge (HDR, Panorama or HDR-Panorama, here the cursor immediately starts spinning and the merge preview does not even pop up) Importing (I can select a source (for example an SD card) but it gets stuck on Checking for duplicates, even when I turn off 'Don't import suspected duplicates’) Exporting (in export I can select all the settings and hit Export but the progress bar remains stuck at zero.I have to use Force Quit to quit Lightroom when it’s not responding.This happens 9 out of 10 times I open up Lightroom, the occasional 1 time everything works fine and I can go on for hours merging huge panoramas or building previews of 100s of photos without problems. But whenever I close and reopen Lightroom the next time it doesn’t work anym

I am using Lightroom Classic 15.6, it prompts me to download AI models. The progress bar shows 100% but when I use AI Edit Update it says (in a red banner) that AI models failed to download and I should try again. I have restarted LR and downloaded the AI models again. The problem remains.

Lightroom Classic 15.5.1 — Technical Performance ReportSubject: Progressive Develop performance degradation, unusually large .lrcat-data, and possible memory/resource-management problemsApplication: Adobe Lightroom Classic 15.5.1Operating System: Windows 11CPU: AMD Ryzen 7 8700GGPU: NVIDIA GeForce RTX 4060 Ti 8 GBCatalog: Approximately 20,000 photographsCamera: Sony α1 II, 50.1 MP RAW filesTypical RAW file size: Approximately 60 MBExecutive SummaryI am reporting a progressive performance problem in Lightroom Classic 15.5.1 that I believe warrants investigation as a potential application resource-management problem rather than simply a hardware-performance limitation.The principal symptoms are: Develop responsiveness progressively deteriorates during extended Lightroom sessions. CPU utilization can rise substantially simply from navigating from one photograph to another, even when no processing operation has been initiated. GPU utilization is often very low during the periods when D

I updated to LrC 15.5 a few hours ago.  Since then LrC has problems with video files.  The first problem I noticed was that when I tried to synchronize a folder that had two new video files.  After a couple of minutes I got the error message “An unknown error occurred while reading the video file. (2)”.  I had just completed those files with DaVinci Resolve so I went back and produced the same files again to check if DR had made an error.  When I tried again with the new files but got the same errors.  I was able to play both videos without any issue using VLC Media Player, so they seem to be OK.  I then shutdown LrC and did a backup including optimizing the catalog, and then restarted it to see if that made any difference, but same error.  Then I started looking at other videos that were already in LrC and found that when browsing them in the Library module, most of them pop up a message “There was an error working with the video”.  They will not play in LrC but work fine with VLC Med

Exporting a portrait video at Quality: Max (up to 4K) chooses a target resolution that is much less than 4K, with a lower frame rate than the source. To reproduce on LR 15.5.1 / Mac OS 26.6.2: 1. Open the attached catalog. 2. Select the video Portrait.mov and do File > Export. 3. In the Video section, select Quality: Max (up to 4K) and observe that the Source resolution is 2160 x 3840, 60 FPS (correct), but the target resolution is 1920 x 1080, 30 FPS (incorrect) -- it should be 3840 x 2160 (or similar horizontal 4K resolution), 60 FPS:  4. Do the export and observe that the resolution of the output is indeed 1920 x 1080, 30 FPS (incorrect), with the portrait video inserted as letterbox (black borders on the left and right).  The exported video should be 3840 x 2160, 60 FPS (or similar horizontal 4K resolution), with the video inserted as letterbox. 5. Select Landscape.mp4 and export it with Quality: Max, and observe the Source resolution is 3840 x 2160, 60 FPS and the Target resolu

Lightroom Classic 15.6 does not enable RTX 5060 Ti GPU on Windows 11 Description of issueLightroom Classic 15.6 / Camera Raw 18.7 does not enable GPU acceleration on my Windows 11 PC with an NVIDIA GeForce RTX 5060 Ti.The GPU is detected in Lightroom Classic System Info, but Lightroom disables all GPU acceleration. In Preferences > Performance, both GPU options are greyed out and Lightroom reports: “Graphics processor acceleration is not supported by your system.”Lightroom Classic versionLightroom Classic 15.6 [202609251514-f839cde9]Camera Raw 18.7 [2743]Operating systemWindows 11 Home, version 11.0.26200, 64-bitGPU and driverNVIDIA GeForce RTX 5060 TiDedicated GPU memory: 16,050 MBNVIDIA Studio Driver 616.92OpenGL renderer: NVIDIA GeForce RTX 5060 Ti/PCIe/SSE2OpenGL version: 4.6.0 NVIDIA 616.92Relevant Lightroom System InfoInitial status: GPU not supportedGPUDeviceEnabled: falseDirect2DEnabled: falseGL_RENDERER: NVIDIA GeForce RTX 5060 Ti/PCIe/SSE2GL_VENDOR: NVIDIA CorporationGL_VE

HeeeeyFor quite some time now, I’ve been getting the error “No retouchable areas could be found” when using the Retouch feature in Lightroom Mobile. I’ve restarted and updated my phone, deleted and reinstalled the app, and made sure everything is up to date, but the error still persists, even when there are clearly suitable areas in the photo that should be retouchable. 

Lightroom Classic tether function was finally working without issue, but after latestest update (14.1.1) will no longer fire via the tether shooting panel when camera (Nikon 850) is in mirror lock-up mode. The other functions work fine, i.e., shuutter speed, aperture, ISO.. all communicate with camera and adjust, but after first click of shutter release (via tether panel) camera just locks with "PC" on LCD. OS: Win 11

In LrC, German version 15.5.1, Camera Raw 18.5.1, the tool tip for “Punktfarbe”, “Hue Range”, the lower triangle, says “Geringere Abfallkante”. I presume the tool tip in the English version is something like “lower edge”, “lower threshold” or “lower limit” or “lower ramp”. In any case, you would not translate “lower” into “geringer” in such a situation. You would use “Untere” instead, which matches “Obere” for the upper end. Geringer would translate to smaller or less in this context, in the sense of “not as high as something else”, which is arguabely not what you want to say. Note that my mother tonge is German and I am an electrical engineer. Feel free to contact me if you need further input or insight at <Email redacted by Mod> Kind regards, Markus

I have more external USB drives than USB sockets on my PC.  This requires me to occasionally swap the main USB drive holding my RAW files to another socket or to reconnect after it has been removed. Lightroom often doesn’t recognize that it is the same drive and allocates a new drive letter, consequently it says files not found and I have to re-sync all of the files which loses the history of which files have been edited.  Could you have Lightroom recognize the drive and allocate it the original drive letter and retain it even after removal.

One feature I still find lacking after switching from Apple Aperture is the ability to “split folders based on shooting time.”This feature splits the folder if the interval between shots exceeds a specified duration.

Hello,Reflection Removal (Remove > Distraction Removal > Reflections) produces a heavily corrupted image on my Intel iMac. The result is a saturated pink/magenta image with yellow, cyan and black artifacts. The image is unusable at any Amount value. A screenshot is attached.SystemLightroom Classic 15.6, and the same result in Camera Raw (Photoshop) iMac Retina 5K, 27-inch, 2019 CPU: 3.7 GHz 6-core Intel Core i5 GPU: AMD Radeon Pro 580X 8 GB RAM: 64 GB macOS Sequoia 15.8.1 (this Mac is not supported by macOS Tahoe)Test fileRaw DNG, Nikon Z camera, NIKKOR Z 24-70mm f/4 S at 70 mm, 1/80 s, f/4, ISO 640What I tried, without any change in the resultSetting Use Graphics Processor to Custom, with GPU for display only Setting Use Graphics Processor to Off in Lightroom Classic Disabling the GPU in Camera Raw preferences Restarting the applications Reapplying the effect from a clean stateOther AI features, like noise reduction, are not affected .Expected result: Reflections removed from th

Hi,after the latest update to v15 of LR for Windows, the behaviour of the cropping tool changed. It's really annoying: It is very difficult to create a selection in portrait format with the mouse in this case. Simply dragging diagonally downwards is no longer sufficient – see my screen video here:https://youtu.be/NYfgYOV3IXE Any idea to get back the old behaviour – not by using the previous version of LR 😉 Thanks!mycc

Since updating to Lightroom Classic 15, the behavior of the Crop tool when drawing a new crop box with the mouse has changed.I am a high-volume photographer and process around 50,000 photos per year, often in batches of 1,000–3,000 images. For many years, my workflow has been to press R and immediately draw a completely new crop box with the mouse. I do not resize the existing crop by dragging its corners.Previously, when working on a portrait image with a locked aspect ratio (for example 2:3 / As Shot), I could simply start dragging a tall, narrow rectangle and Lightroom would immediately recognize that I wanted a portrait-oriented crop.Now, when I start drawing a new crop box, Lightroom keeps the crop in landscape orientation. It only switches to portrait orientation after I drag the mouse a very long distance vertically. In many cases I have to drag almost to the bottom edge of my screen before it finally switches from landscape to portrait. When the area I want to crop is relativel