Lightroom Classic

When a video is exported from Lightroom Classic, the “Capture Date” (CreateDate or DateTimeDigitized) is overwritten with the time of the export. However, the “Capture Date” must not be changed during export. It works when exporting photos.

Hi everyone,I'm having an issue with the latest version of Lightroom CC on a MacBook M5 Pro running macOS Tahoe 26.5.1. (I was experiencing the same problem on 26.5 and decided to update hoping it would fix it, but unfortunately it didn't.)Since this morning, it's been impossible to to use Noise Reduction, even though my internet connection is working perfectly. I've already updated both Lightroom CC and macOS, cleared the cache, and optimized the catalog, but I keep getting this error screen whenever I try to use Noise Reduction.Has anyone experienced the same issue or knows how to fix it? Any help would be greatly appreciated. Thanks! 🙏 

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. 

Installed this and my tethered camera setup no longer works.  It appears to work as before, but no images are transferred.  Canon R1, Windows 11.  Anyone else having tethering issues?

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

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 am a photojournalist and recently switched from a PC to a MacBook (last week). My workflow has been rock-solid for many years, and my old archive copied over to the new Mac system without any issues.My Workflow: Preview & Culling: Photo Mechanic Editing: Photoshop 27.9.1 / Adobe Camera Raw Saving: Exported/saved as DNG files Archiving: Import DNGs into Lightroom Classic 15.5.1 The Issue: For my commercial side work, I regularly apply the "Adaptive: Color" profile to my Raw files. However, since switching to the Mac, when I import these newly edited DNGs into Lightroom Classic, LrC fails to apply or read the "Adaptive: Color" profile. The images import looking completely flat.What I've Tried: I read that updating the AI settings in Lightroom might resolve this, but it did not work. Manually reapplying the Adaptive Color profile inside Lightroom does fix the image, but this is way too time-consuming and defeats the purpose of my workflow. Note: Older images processed this

W tłumaczniu na język poski znalazłem nastepujące błęd: Pokaż wskaźniki przycinania powinno być Pokaż wskaźniki prześwietleń i niedoświetleńPokaż opcję Obcięcie, gdy mysz jest nad wskaźnikiem powinno być Pokaż ostrzeżenia, gdy mysz jest nad wskaźnikiemUkryj obcięcie światła powinno być Ukryj ostrzeżenia o prześwietleniachUkryj obcięcie cienia powinno być Ukryj ostrzeżenia o niedoświetleniachPokaż obcięcie światła powinno być Pokaż ostrzeżenia o prześwietleniachPokaż obcięcie cienia powinno być Pokaż ostrzeżenia o niedoświetleniachPokaż obcięcie powinno być Pokaż prześwietlenia i niedoświetlenia   Profil Adaptacyjna powinno być Adaptacyjny

When I try to import picture files, I get a popup for assisted culling that locks the application. I need to go to task manager to shut down the application.   I turned off assisted culling under catalog settings, but this does not correct the issue. Is anybody else experiencing this issue. I cannot import new files!  

LRC 15.3Windows 11 Step to reproduceConfigure auto import. Don’t rename and don’t apply any preset. Keep is simple  Auto import settings  Copy a photo in the auto import folder. The photo is imported automaticly Launch a normal import with the "don’t import suspected duplicates" box checked Point to the initial folder were the photo was (not the auto-import one) The photo that is already in the catalog is not greyed. You can reimport it and create a duplicate even if you ask to avoid duplicates. Kind regards

If a plugin calls catalog:updateAISettings() immediately after photo:applyDevelopPreset(), the application of the preset is ignored. This bug was introduced in LR 15.3, likely with the background processing of AI commands. To reproduce on LR 15.3 / Mac OS 26.4.1: 1. Import the attached preset “_Update Bug.xmp”. 2. Put the attached file “updateaisettings-bug.txt” into the LR Scripts folder. 3. Go to Develop with a test photo. 4. Do Scripts > updateaisettings-bug. Observe that Exposure is not changed (incorrect -- it should change to 4). 5. Apply the preset “_Update Bug”. Observe that Exposure changes to 4 (correct). A workaround is to call LrTasks.sleep (0.1) before calling catalog:updateAISettings().

I have many video files imported into LrC that I want to modify the filename.  The video files were taken with the iPhone 17 Pro.  My usual method to edit the filename is to edit the filename entry in the metadata panel.  When I use the method I get an error message that the filename cannot be edited.  If I use the alternate method of using the F2 key, I get the same error message.  I have submitted another bug report about not being able to import video files into LrC 15.5.  That bug report has been “Acknowledged”.  In that case reverting to v15.4 allows imports. Unfortunately reverting to v15.4 does not fix this issue. 

As the title says, if I go to the develop module in lightroom, click on the removal tool then go down to distractions and click apply on the reflections section I can’t then send the photo to photoshop. If I send it to photoshop it opens up the photoshop app but just gives me the home screen as shown and doesn’t open the photo.   

What an awful release. Don't get me wrong, I'm glad to see new developments, but this Lightroom update is an absolute disaster. After culling just 5-10 images, the AI Assist culling tool completely hogs all my RAM, causing my Mac to freeze and throw memory errors. It’s a total nightmare.Culling images via the library module is practically impossible right now - everything just locks up. Even with previews pre-generated and trying to run AI Assist culling, the performance is still abysmal. On top of that, it frequently fails to even generate a Denoise. What is going on, Adobe?! This is absolutely unacceptable!P.S. The RAM management is completely broken and goes beyond any acceptable limits!  

After upgrading to v15.2, the Library Filters cannot be enabled. Clicking the Library menu ‘Enable Filters’ will just give Library Filters Off each time is it clicked. The check mark remains on the Enable Filters menu. Using the hotkey Ctrl-L  does not work either, just keep saying Library Filters Off. No way to enable the Library Filters. I have also restarted my Windows 11, and still cannot enable Library Filters.

Adobe LrC and CR are not recognizing Apple iPhone DNG files as being raw files. (1) When I import into LrC using Copy As DNG, the error message says: "Non-Raw Files Were Not Converted to DNG", (2) The new PS CR feature to remove reflections from shooting through glass gives error message that this applies only for RAW files (but this IS a raw file), (3) LrC Develop Basic Auto button hardly makes any changes including leaving major clipping. It appears that Apple ProRAW file format is not being recognized by Adobe products as being a RAW file.

Double-clicking the labels Feather and Edge in the masking panel doesn’t reset those sliders to their default values. But you can reset every other slider in Develop by double-clicking their labels. Clearly an oversight by the developer rather than a deliberate design decision (bug not feature). To reproduce in LR 15.5.1 / Mac OS 26.6.2: 1. Create a Subject mask. 2. Slide Feather to 23 and Edge to 30. 3. Double-click the labels Feather and Edge and observe that nothing happens. See the attached screen recording.

EnvironmentAdobe Lightroom Classic 15.5 Lightroom SDK Windows 11 and macOS 26.5 Standalone reproducer plugin attachedSummaryA dialog window created with a save_frame parameter does not always shrink to fit smaller content on reopen. When a dialog is closed and reopened with a smaller content view, the window keeps its previous (larger) frame instead of resizing down to match, leaving a strip of unpainted native window chrome along the right and/or bottom edges. Growing the content works correctly in every case tested.This affects both presentFloatingDialog() and presentModalDialog(), and is platform-dependent:Dialog type Platform Shrinks window to fit smaller content? presentFloatingDialog() Windows No — border left presentFloatingDialog() macOS No — border left presentModalDialog() Windows Yes — correct presentModalDialog() macOS No — border left  Windows + presentModalDialog() is the only combination found that resizes the window correctly to smaller content

I have been playing around with edge and feather and they help some. I surprised at how poorly LR does at masking period. You can see the clearly lighter areas between the trees that it missed. Compared to other tools this is a poor result. Also, what is the deal with the long delay in switching between images now. You click the thumbnail and 20 seconds later it is displayed. 

On Mac OS, after completing an import LR will sometimes display the message "Ejected card after import" but fail to actually eject the device.  This affects users importing from Cfexpress cards.   To reproduce on LR 12.3 / Mac OS 13.3:   1. Connect an external USB disk drive or a Cfexpress card reader containing a Cfexpress card with at least one photo on it.   2. Verify that Mac OS considers the drive non-removable by running this command in Terminal:   diskutil info "<volume>" | grep -i removable   The output should be:   Removable Media: Fixed     3. If you connected a USB disk drive in step 1, copy to it the DCIM folder from any camera memory card containing at least one photo.   4. In LR, do Import, selecting the option Eject After Import. In the Files section select the volume from step 1 and select one photo.  Click Import.   5. When the Import completes, observe that LR displays "Ejected card after impo

Lightroom Classic Version: 15.5Operating System: macOS Tahoe 26.6.2 (25G83)Steps to reproduce: Open a primary Lightroom Classic catalog. Go to File > Import from Another Catalog. Select a large secondary catalog (e.g., 16,000+ or 43,000+ images). Start the import process. Expected result: The catalog import should process all images and complete successfully.Actual result: The import process fails midway with a generic "An unknown error occurred" dialog box.Key Pattern Identified: The import process stops at exact, round batch numbers: On a catalog containing 16,623 images, the import halted at exactly 15,000 images. On a catalog containing 43,881 images, the import halted at exactly 25,000 images. Additional Diagnostic Details: Telemetry log right before crash: last_command = "ag.file.import.fromlibrary" RAM usage remains low (under 3 GB / ~8% memory total), ruling out memory saturation. The exact round numbers (15k / 25k) strongly suggest a batch transaction commit fai

Lightroom Classic version 15.4Mac OS 26, Version 26.5.1Mac Studio M4 MaxPrior to the latest upgrade to Lightroom Classic I was backing up my catalog to my Synology drive. I now get the unable to write to drive error, check permissions and available space on the drives. I can backup the file locally on my MAC and then copy that over to the Synology drive. So it does not seem as though permissions is the issue. Have 16TB of storage on the Synology and 782 GB free on a 1 TB SSD on the Mac. Only started when after the latest upgrade to Lightroom Classic.

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?

When the Fetch Altitude For Coordinates button in the Location tagset of the Metadata panel is pushed while in the Map module, it correctly sets Altitude but it doesn't display it in the Metadata panel. This appears to be an old bug filed in 2019 that didn't get migrated from the old feedback forum: https://community.adobe.com/t5/lightroom-classic-discussions/map-module-altitude-of-the-points-si-0-in-the-gps-coordinates-of-the-photos/m-p/10313076#M136897    To reproduce on LR 13.2 / Mac OS 14.2.1:   1. In Library, select a photo that doesn't have any assigned GPS coordinates.   2. In Map, drag the photo to the map. Observe that it gets assigned GPS coordinates but not Altitude (correct).   3. Click the Fetch Altitude For Coordinates button. Observe that the Altitude field remains blank (incorrect).   4. Go to Library and observe that the Altitude field is filled in (correct).   5. Go back to Map and observe that the Altitude field is filled in (correc

The option Catalog Settings > Metadata > Include Develop Settings In Metadata is not working correctly -- develop settings are still getting included in the exported metadata and .acr files (which contain develop settings) are sometimes getting exported. The   Metadata Status field is also not working correctly. Tested with LR 15.5.1 / Mac OS 26.6.2: 1. Download and open this tiny catalog and select the single photo:https://www.dropbox.com/scl/fi/f32l8iyi85gldfbd1xiew/ccbug.2026-09-01.zip?rlkey=hkwadikr9tkhdxcha1dgparms&dl=0 2. In the Metadata > EXIF AND IPTC panel, observe that Metadata Status is Up To Date. 3. In Catalog Settings, observe that both Metadata > Include Develop Settings and > Automatically Write Changes Into Sidecar are unchecked. 4. Export the photo to Desktop with Image Format: JPEG, using these settings:  5. Using Exiftool, observe that the develop settings are incorrectly included in the XMP section of the exported photo:[XMP] Exposure 2012 : -3.0