Bug Reports

Save Metadata To File will unnecessarily write a huge .acr sidecar for a JPEG that’s been exported from LR and reimported. This affects users who regularly export with the Add To Catalog option. See here for a motivating use case:https://www.lightroomqueen.com/community/threads/exported-jpgs-with-an-acr-file.54565/ To reproduce  on LR 15.2.1 / Mac OS 26.2: 1. Download and open the attached catalog, which contains a single raw, DSC08981.ARW, with Denoise applied. 2. Ensure the option Catalog Settings > Metadata > Include Develop Settings In Metadata is enabled (the default). 3. Select the raw and export it as a JPEG to the desktop, with Quality = 70 and the option Metadata > Include: All Metadata. 4. Import the exported JPEG with the Add Option. 5. Select the JPEG and do Metadata > Save Metadata To File. Observe that DSC08981.acr is created, about 10.3 MB (three times the size of the .jpg) (incorrect). 6. Delete DSC08981.acr from the desktop. 7. Edit DSC0891.jpg in Develop a

Issue:List of camera models and their associalted raw standards shows only 6 entries without scrolling. A scrollbar is only added after 8 entries. The last entry does not apper in the list. Versions:Lightroom Classic Version 15.2.1. Camera Raw 18.2.2. .OS Windows 11 Pro, 25H2, Build 26200.8037, German DE-DE To reproduce:Create 6 Raw Standards for different camera models. They appear all in the list. Add a 7th Raw Standard for a new camera model. They last entry ist not shown. No scrollbar abailable. Add a 8th Raw Standard for a new camera model. The scrollbar is available. The last entry is missing.Note: The list ist sorted alphabetically.

The update to the Generative Remove AI model in Lightroom Classic 14.5 has ruined it, as it now changes elements outside the painted mask, making it more or less unusable in many situations.

When Rename Photo is applied to a virtual copy, the Example line in the dialog uses the virtual copy’s metadata, but the actual rename uses the original’s metadata.  They should both use either the virtual copy’s metadata or the original’s metadata. (I think it’s more useful and less confusing for the actual rename to use the virtual copy’s metadata, but assuming the current behavior is “as designed” rather than “as coded”, then the Example line should be fixed to use the original’s metadata.) To reproduce on LR 15.2.1 / Mac OS 26.2: 1. Download and open the attached tiny catalog. It contains the original x.jpg and a virtual copy of x.jpg.  All the editable metadata fields of the original contain “j” (for JPEG) or the number 1, while those fields of the virtual copy contain “v” (for virtual copy) or the number 2. 2. Select the virtual copy and do Library > Rename Photo. 3. Edit the template to contain just the token Title. Observe that Example: says “v.jpg” (since the virtual copy’s

Issue: When I save metadata from Lightroom Classic via "Save Metadata to File", I lose subsecond EXIF metadata that was originally there in the file. This is new behavior, did not happen in previous versions (though I'm not sure exactly when it started).   Lightroom Classic version: 13.5 [ 202408062022-6258095b ] System version: macOS 13.6.9   To reproduce:   1) Import a photo that has a subsecond creation date—for my test, I used an iPhone photo imported via mobile sync.   2) Check SubSecTimeOriginal from the command line: $ -> exiftool -G -s -SubSecTimeOriginal /Volumes/Media/Photos/Import/Mobile\ Import/IMG_6067.HEIC  [EXIF]          SubSecTimeOriginal              : 389   3) In LrC, run the "Save Metdata to File" command   4) Check SubSecTimeOriginal from the command line: $ -> exiftool -G -s -SubSecTimeOriginal /Volumes/Media/Photos/Import/Mobile\ Import/IMG_6067.HEIC  Warning

1. Platform and Version Lightroom Classic version: 15.2.1 OS: Windows 11 Pro 2. System Environment (Multi-monitor & Scaling) Display Setup: 4 monitors (Mainly using two 2560x1440 and one 1920x1080). Windows Scaling: All monitors set to 125% scaling. GPU: NVIDIA GeForce RTX 4070 Ti [cite: 2026-02-02]. 3. Steps to reproduce Open Lightroom Classic on a multi-monitor system with Windows Scaling set to 125%. Enable the Secondary Display (F11) in Full Screen mode on any additional monitor. In either the Library or Develop module, cycle through the "Lights Out" modes by pressing the 'L' key (Lights On > Dim > Lights Off). 4. Expected result The UI should dim (Lights Dim) or turn black (Lights Off) on all monitors, while keeping the image/grid area fully visible and unaffected by the dimming layer. 5. Actual result The dimming behavior is erratic and inconsistent: Total Blackout: Frequently, the photo area itself is dimmed or completely blacked out on either the main or sec

When you change the year in Metadata > Edit Capture Time to before 2001, the milliseconds goes negative and one is added to whatever value you enter for seconds.  This is likely related to the Cocoa timestamp epoch of 1/1/2001.  If instead you change the year to 2018, the milliseconds gets decremented by one (also incorrect). To reproduce on LR 15.2 / Mac OS 26.2: 1. Open the attached tiny catalog. 2. Select the photo and do Metadata > Edit Capture Time. 3. Click in the year and type 2019 (quickly, to avoid another Edit Capture Time bug).  Observe that the milliseconds field stays at 22 (correct). 4. Click cancel, do Edit Capture Time, click in the year, and type 2018. Observe that the milliseconds field gets changed to 21 (incorrect) 5. Click cancel, do Edit Capture Time, click in the year, and type 2001. Observe that the milliseconds field gets changed to 21 (incorrect). 6. Click cancel, do Edit Capture Time, click in the year, and type 2000. Observe that the milliseconds field

When viewing a film strip which is filtered to only show flagged image if I click on the flag to "unpick" the selected image and then click on the next image that image is also unpicked. It's a little complicated to explain but the attached video shows it happening and it's very easy to duplicate using these steps:Set the pick flag on multiple imagesGo to Develop Filter only so only images with the flag are displayedSelect an imageClick the flag on the thumbnail to remove it from the filtered listQuickly click on another thumbnailA second image will be removed (UNDO will return it)It seems like the time it takes for the preview for the next image that's automatically displayed when the last image is filtered out is the window for when a click on a thumbnail means the 2nd image will also lose it's flag.I believe it's a bug, it's been happening for quite a few versions now but I've posted in discussion as per the preferred method of reporting. It's become more apparent and annoying in 14

Typing into the year field in the Edit Capture Time dialog is too fussy, making it difficult for people who are slow typists (hunt-and-peck or disabled) to enter the year. If you type just a little slowly, then after 1-3 digits, the dialog thinks you've finished entering a year, and the next digit you type will erase the previous ones. Screen recording: https://www.dropbox.com/s/ks09r4f5847zwx0/capture-time-digits.2019.04.05.mov?dl=0A perhaps related problem was reported fixed back in 2015.4, though it had somewhat different symptoms. Another user just wasted a bunch of time tripping over this:https://forums.adobe.com/message/11010712#11010712The fix should be trivial: the timeout for entering digits just needs to be increased a fair bit.Tested on LR 8.2 / Mac OS 10.14.3.

Invoking the Library Filter bar’s Restore Default Presets creates duplicates of the built-in filter presets.   To reproduce in LR 15.2 / Mac OS 26.2: 1. Set the option Preferences > Presets > Store Presets With This Catalog. 2. Open the attached catalog “filter-presets-bug”. 3. In the Library Filter bar, click the drop-down menu and do Restore Default Presets. Observe that the built-in presets Default Columns, Filters Off, and Location Columns have been duplicated.  Examining those presets’ .lrtemplate files, the contents of the duplicates are identical. Before and after of the drop-down menu: 

Same  Problme  help me, please

When closing LightRoom Classic, this application creates a bakckup file. Sometimes, it does work ...Two cases1) backup stored on internal disk (APFS format) : OKThe zip file contains 2 elements : the catalog, a file named Photos 2022 et +.lrcat, a folder Photos 2022 et +. lrcat-data 2) backup stored on an external disk ‘SSD disk as Sandisk Extrem Pro or hard disk as La Cie USB 3) (ExFAT format) : WRONGThe zip file contains 4 elements : a catalog file named Photos 2022 et +.lrcat, a folder Photos 2022 et +. lrcat-data 2 additional fles (temp files) Photos 2022 et +.lrcat-shm et Photos 2022 et +.lrcat-wal  At end of closure operation, catalog folder is correct : a file named Photos 2022 et + Helper.lrdata, a file named Photos 2022 et + Previews.lrdata, a catalog file named Photos 2022 et +.lrcat, a folder Photos 2022 et +. lrcat-data  Informations systèmeNom du modèle : Mac miniPuce : Apple M4  - Mémoire : 24 Go Informations sur le logiciel LightRoom ClassicVersion Lightroom 

LR fails to normalize the Unicode text of keyword names and allows the creation of two keywords that are canonically equivalent, with the same appearance and meaning under the Unicode standard. To reproduce on LR 15.2 / Mac OS 26.2: 1. Open the attached file “keywords.txt” in a Unicode-compliant text editor (e.g. Textedit or Notepad). 2. In LR’s Keyword List panel, click + to create a keyword, and copy/paste the first line from the file into the keyword’s name. 3. Repeat for the second line of the file. 4. Observe there are two keywords with the same name, as defined by the Unicode standard: The two lines of the text file use different canonically equivalent Unicode representations for the same letter: U+00F6 (LATIN SMALL LETTER O WITH DIAERESIS)U+006F (LATIN SMALL LETTER O) + U+0308 (COMBINING DIAERESIS) Such keywords tripped up this user’s catalog upgrade from LR 14 to LR 15:In that case, we were unable to construct a test case that failed other than on his computer. There is a simil

LR 15.0.1 / Windows incorrectly rounds a capture date/time of 11/13/25 10:30:03.99974 PM to 1/1/1601 4:00:00.477 PM.  But LR 15.0.1 / Mac correctly rounds it to 11/13/25 10:30:04.000 PM.   Tested on LR 15.0.1 / Windows 11 Intel, Windows 11 ARM, and Mac OS 15.7.1. To reproduce:   1. Download and open this catalog: https://www.dropbox.com/scl/fi/3psajur7hfth6ezly98vk/subsec-bug.2025-11-18.zip?rlkey=e3ww25awh8wf3rmrf1nr6x8am&dl=0   It contains two photos with these capture date/times: subsec.dng: 2025:11:13 22:30:03.99974 subsec-smaller.dng: 2025:11:13 22:30:03.99900   2. Right-click the folder "pics" and do Synchronize Folder.   3. On Mac, observe the capture/date times of the two photos have been rounded correctly:   But on Windows 11, observe that the capture time of "subsec.dng" has been mangled to 1/1/1601 4:00:00.477:    

I start with an edited version (lightroom adjustments only) of a photo in lightroom. I make a copy of it and then click reset on the new copy. This copy is essentially no modifications at this point. I then edit that copy in photoshop. When I am done editing in PS, I save it. I then open that PS-modified version in lightroom and paste ALL settings I have copied from the original to this new TIFF version. I expect the changes to work but it looks wrong. I notice the REMOVED tool item masks are strange. It looks like the REMOVE masks in the version that I pasted to are 90 degrees rotated - clockwise. Basically, copy/paste of masks does not work from a raw file to a tiff version. It’s like PS messed up the orientation indicator or something and LR got confused?

Upgraded to 11.3 this morning. 11.2 and previous worked without problems.   I notice the following: Using the hand tool to reposition the image within the print frame: Up and down are reversed.    For example I am printing a photo of a model on white background. If I reposition the photo so that the model is in the center of the frame I have to click and drag the image in the opposite direction to which I want the image to move.    So with the model in the center of the frame and with ample padding around the image the print comes out with her toes cut off????    If I then reposition the image on screen so that the models toes are cut off the print comes out with the model centered nicely with ample padding around the image!!!!   Richard

LR 15.2 introduced inconsistent names for the Backspace and Delete keys in the French in-program shortcut help. WindowsLibrary Help:Map Help:“Supprimer” is French for the Delete key. But on Windows, the Backspace key is called “Retour arrière”. MacLibrary HelpMap Help: On Mac, the Delete key is called “Supprimer”. So the two instances of “Arrière” should be replaced by “Supprimer”. 

Hello: I just updated to the 15.0 release and I think I just discovered a bug. When I click Edit Capture Time via the Metadata tab, whatever time I enter is one hour off from the time that shows up in the EXIF data panel (and how it sorts the photo if "Capture Time" is used to sort the library); therefore to get the EXIF information to show up correctly, I must purposely enter the information one hour behind the time I want it to be (see screenshot where I want 5:31pm to be the edited time, but I must enter 4:31pm to get 5:31pm).  -- Scott, MacBook Pro, Apple M3 Pro chip, macOS Sequoia 15.6.1.

Using the Copy Settings Subset option of modifed doesn't recognise the cropping if the image angle or aspect ratio haven't been modified. Please delete this post or merge with my later post here: https://community.adobe.com/t5/lightroom-classic-discussions/copy-settings-gt-subset-modified-ignores-crop/m-p/15501384

When calling the LrApplication.addDevelopPresetForPlugin with the settings below, which don't include any white balance settings, the temp is adjusted to 2000 and Tint to 150.local photoPresetTable = { Exposure2012 = -0.43, Whites2012 = 2}Full code examplelocal LrDialogs = import 'LrDialogs'local LrTasks = import 'LrTasks'local LrFunctionContext = import 'LrFunctionContext'local LrApplication = import 'LrApplication'local LrFileUtils = import 'LrFileUtils'LrFunctionContext.postAsyncTaskWithContext("Test apply preset", function(context) LrDialogs.attachErrorDialogToFunctionContext(context) local catalog = LrApplication.activeCatalog() local activePhoto = catalog:getTargetPhoto() -- Create preset local photoPresetTable = { Exposure2012 = -0.43, Whites2012 = 2 } local newPhotoPreset = LrApplication.addDevelopPresetForPlugin(_PLUGIN, "Test preset", photoPresetTable) -- Apply preset catalog:withWriteAccessDo("Apply preset", function() activePhoto:applyDevelopPreset(newPhotoPreset, _PLUGI

catalog:getCurrentViewFilter() doesn't report the new Stack options in Library Filter's Attribute bar.  This affects the popular commands Back To Previous and Forward To Next Source/Filter/Selection of my Any Source plugin.   When this is fixed, be sure to test catalog:setViewFilter() as well.   To reproduce on LR 15.0 / Mac OS 15.7.1, run my Debugging Toolkit's Debug Script command:    

Lightroom Classic crashes when backing up catalog and looking at preferences, and doing an integrity check. I'm running Lightroom Classic on a new MAC with Sonoma and I've recently upgraded all my external hard drives.  I'm a photographer for the USA Today and have an enormous catalog. My crash report header is below - the full report is beyond enornmous. My catalog is over 4 gig. Lightroom Classic crashes during the integrity check. I've reset preferenes during startup.   I've uninstalled Lightroom today and reinstalled the latest from Adobe CC.   Neither of those options have helped.  I've tried backing up my catalog to 3 other external hard drives and also to the local MAC hard disk - no luck and no success with any of that. Restart, Reboot - nothing works.   Help, please.   -------------------------------------Translated Report (Full Report Below)------------------------------------- Process: Adobe Lightroom Classic [694]Path: /Applications/Adobe Light

I have a Macbook Pro M4 Pro chip, using MacOS Sequoia 15.5 with 48GB of memory. I am using version 14.4 of Lightroom classic with Camera Raw 17.4. My Lightroom keeps crashing, with no particular pattern that I can pick up.   Is there any fix or anything I can do to resolve the issue? Your help would be appreciated.

Windows 11 21H2   If you shut down Lightroom Classic 11.3.1 with the Library Module showing, then re-launch later, the Map Module works fine.   If you shut down Lightroom Classic 11.3.1 with the Map Module showing, and then re-launch later, the Map Module is not usable. The exact form of the error changes, its not always the same, sometimes I get JavaScript error, sometimes the Map Module just freezes, other times it has other errors, but the Map Module simply doesn't work in this situation.

I just updated my LrC to v 12.4 this morning and now when I try to copy/paste settings in the develop tab to a new photo, the new photo is hazed out and flat looking. If I reset the settings and put them in manually, it looks correct, so it has to be an issue with the copy/paste. Please help this is slowing down my work flow tremendously.   PC, Windows 10