Bug Reports

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

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

Hello,I recently posted on Intel's forum regarding problem with heavy gpu tasks on my laptop.They asked me to post here to see if people on Adobe's side have any idea on how to fix this, and to cooperate. My laptop is an Asus Zenbook (UX3405CA) : - I9 285H - Intel Arc 140T 16Go updated with the latest available driver (32.0.101.8331) - The problem is still there with older drivers - Windows 11 pro up to date - Lightroom classic version 15.1 - Tried with older versions of Lightroom - The BIOS has been updated- Cleanded drivers with DDU in recovry mode then reinstalled through intel utility tool - Recleaned them with DDU in recovery mode then reinstalled through MyAsusThe problem persists.I get a LiveEventKernel with the code 141 in the event viewer every time the problem arises.I have attached some relevant files, but can't add the dump because the format is not accepted.I need your help to fix this problem permanently.Thank you

After starting LR, clicking the GPS badge of a photo centers the map on the last-displayed location rather than the coordinates of the clicked photo. To reproduce on LR 15.5 / Mac OS 26.4.1: 1. Open the attached catalog. 2. Go to Map view. 3. In the filmstrip, click on the GPS badge of "miami.jpg". Observe the map centers on Miami (correct). 4. Go to Library. 5. Restart LR. 6. Click on the GPS badge of "san francisco.jpg". Observe that the module switches to Map view and the map centers on Miami rather than San Francisco (incorrect). 7. Go to Library. 8. Click on the GPS badge of "san francisco.jpg" and observe the map moves to San Francisco (correct).  

Steps to Reproduce: 1. Select an Ai mask2. Move any of the Refinements sliders from form the current value to another one and back to the current value but NEVER releasing the slider.Actual Result: A step is recorded in history but nothing changed from step 1 and step 2, the value chosen in UI is the same.Expected Result: Moving AI masks "Feather" or "Edge" sliders DOES NOT record an history step when the UI value is the same as before.Addendum: There is floating point difference in the values when moving a slider back and forth to the same value but it should not matter.Feather at 30 Feather moved from 30 to 30 again 

Lightroom bug - hit a folder limit and unable to select the newly imported folder.452497 photographs across many drives in one catalog.The S drive has 214341 photos. It's the largest drive and so had many more folders than the previous drives.S:\Master Photos\ contains ~1633 folders. I know that's a lot but that is how her filing system was started. Those are the sequential numbers from 2220 - 3853 but there may be a sub folder or two or deleted folder in there so that's why the number is ~ approximate.Folders are labeled "sequential number"-"date" so 3853-20150316Adding one more folder caused Lightroom 4 to not allow the last folder to be clicked on and not show any images. The T:\ drive (offline, collapsed and below the S:\ drive) was collapsed and the label was overlaid on top of the "Collections" section label. Updated to latest version of Lightroom 5 via her new cloud account, had it rebuild the catalog and the same problem occurred.Created a sub folder S:\Master Photos\2012 and m

EnvironmentMac mini M4 24 GB unified memory macOS Tahoe 26.5.2 Lightroom Classic 15.5 Apple Silicon / arm64 Lightroom Classic catalog with images using AI masks, Remove and Lens BlurProblemLightroom Classic produces random blue horizontal lines/artifacts on images after AI processing.The artifacts are variable and may appear only several seconds after selecting the image in Develop. They can also be present in exported JPEG files.The problem appears to be strongly related to Lens Blur.Reproducible behaviorI can reproduce the problem with the following sequence:Open an image containing AI masks and/or Remove edits. Apply Lens Blur. Lightroom starts AI processing in the background. After some time, random blue horizontal artifacts appear in the image. The artifacts can also appear in exported JPEG files.The behavior is not simply a display-only problem because the artifacts can be present in the exported JPEG.Important observationsWith Graphics Processor disabled:Lens Blur ON → blue arti

Apple ProRaw images taken in Apple's camera app on my iPhone 14 Pro generally work well in LrC these days, which is great. In LrC I often use the "Apple ProRaw" profile.   When I perform a panorama merge of these images, however, LrC reports that the resulting .dng file is using the profile "Apple Embedded Color Profile" but shows an exclamation mark: "Profile missing." See attached screenshots.   I wonder if this is an inadvertent result of LrC's rule that only Apple ProRaw files have the option of the LrC ProRaw profile, and that the merged file is not recognized by LrC as a ProRaw file. Can this please be improved, or is there a workaround?   Thanks, Wallace

Hola;Es mi primer post, he estado indagando por la comunidad, y no he acabado de encontrar la solución.Uso LRC en un MacBook Pro y en varias ventanas de ajuste tengo problemas de redimensionar (salen cortadas). Me di cuenta en la de ajustes de mascara (adjunto captura), pero repasando algunas otras secciones como Ojos Rojos, Recorte… también tengo el mismo problema (adjunto capturas)He probado en modo pantalla completa y nada, se queda igual.Alguien sabe como solucionarlo? Es muy molesto no poder trabajar bien.Muchas gracias.  

The new Lightroom version has a major bug in the map module!When you try to position a photo somewhere on the map Lightroom 6.8 assigns a wrong position (near the spot).

Description of IssueI believe that at times, Lightroom Classic 15.5 produces phantom pins on the map, that is, pins that appear to be locations of photos, but either the count of images is wrong, or the pin itself doesn’t work (when you hover over the pin, nothing happens), or both. I understand that a major malfunction of the Map module was fixed in 15.5, but this seems like a different problem.Lightroom Classic Version Number (Help>System Info…) Lightroom Classic 15.5OS Version NumberWindows 11 25H2 (26200.9168)Camera Model (sometimes necessary)Nikon Z6 IIStep-by-step Reproduction Instructions (in precise terms, please)Step 1: Select a lot of images and display the map (in my case, all photos in New York State). Zoom in. Notice the cluster of pins right in the center of this screen capture (I have drawn a red box around them). Step 2: press the plus sign to zoom in more. Let’s focus on the bottom of this cluster of pins. Notice the area indicated by the arrow, there are three pins

Versione di Lightroom Classic: 15.5 aggiornamento di agosto 2026Sistema: MacOs Tahoe ultima versioneFile: Nikon raw convertito in DNGComportamento: sistematico, sempre riproducibileDescrizione: nell’immagine c’è una persona che voglio rimuovere. Dal modulo Sviluppo seleziono “Rimuovi” e spunto “Usa IA Generativa”. Clicco su “Persone”, attendo che LrC trovi l’area con la persona da rimuovere e premo “Rimuovi”.Da questo momento non sarà più possibile salvare i metadati, nel senso che LrC visualizzerà sempre “Metadati non salvati”. La situazione si risolve cancellando la rimozione. Nota: quando premo CMD+S sul file, per salvare il file, comunque qualche modifica viene apportata poiché il finder del mac aggiorna la “Data di modifica”.

Compare view often incorrectly labels a photo as having an embedded preview. To reproduce on LR 15.5 / Mac OS 26.4.1 (see the attached screen recording): 1. Download and open the attached catalog. Observe that Catalog Settings > Standard Preview Size is 2880. 2. Right-click folder "test-pics" and do Synchronize Folder, selecting Show Import Dialog Before Importing. Set the import option File Handling > Build Previews to Embedded & Sidecar. Observe in Grid view that X.ARW is marked with the embedded-preview badge (correct). 3. Do Library > Previews > Build 1:1 Previews, selecting Build All. Observe that neither photo has the embedded-preview badge (correct). 4. With X.ARW selected, go to Compare view. Observe that it says Embedded Preview at the bottom of X.ARW (incorrect). 5. Go to Grid view. 6. Select X.jpg and go to Compare view. Observe that X.jpg is labeled with Embedded Preview (incorrect). 7. Go to Grid view and restart LR. 8. Select X.ARW and go to Compare view.

Yes, this exact question has been raised many times in the past and those posts have all been closed as “answered” without any resolution.  This is still an issue.I open LrC, import and make edits.  LrC sits idle with computer running for at least an hour.  Try to close LrC and it spends several minutes  "Writing Metadata Changes into XMP" before the app exits.  What is LrC doing while idle after the last edit was made that it now needs to do when I’m trying to shut down the computer?  This is unacceptably poor performance but vaguely understandable as edits were in fact made.  Why are the XMP writes not happening during idle time rather than forced immediately at exit?The same delay occurs without making edits.  Open LrC, make no edits and immediately try to open another catalog.  LrC shows the "Writing Metadata Changes into XMP" message for several minutes before finally restarting with the other catalog.  This is after LrC spent several minutes  "Writing Metadata Changes into XMP" p

Just starting today the Map module is leaving behind markers for a photo or photos that have been moved. It also continues to show markers for photos that have been opened but are no longer in the directory being worked in. If I leave LRC and come back in, all is well but I've never had to do this before. It is more of an annoyance than a major issue, but it does clutter up my screen while moving things. I am in the process of locating old photos that have inaccurate or no geotagging and this behavior is slowing me down. I’m running 15.3 on a MacBook Air. Has anyone else seen this or have a suggestion of how to fix this behavior? 

LR 15.5 made numerous inconsistent and incorrect changes to how the Delete and Backspace keys are  translated in Help > Library Module Shortcuts and Map Module Shortcuts. Prior to 15.5, LR followed the principle of using the names of the keys as they appeared on the most commonly used keyboards for that language. For example, on Spanish (ES) keyboards, the Delete key is labeled Supr, and LR's Help used Supr for the Mac shortcuts for Library > Remove From Library, Map > Delete GPS Coordinates, and Map > Delete All Location Metadata. This convention makes sense -- Help uses the names of the keys that are displayed on the user's keyboard. But in 15.5, the displayed names of the Delete key (Mac) were changed in all 15 non-English languages, for some but not all of the commands assigned Delete.  Similarly, the displayed names of the Backspace key (Win) were changed in 6 languages, for some but not all of the commands assigned Backspace. For example, in Spanish, the name for the

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”. 

 EnvironmentAdobe Lightroom Classic 15.4 (also observed in earlier versions) Lightroom SDK Windows 11 Standalone reproducer plugin attachedSummaryA floating dialog opened via presentFloatingDialog() becomes the active window, but no control initially receives keyboard focus.As a result, standard keyboard interaction is unavailable immediately after the dialog opens. Pressing Enter, Esc, Space, or Shift+Tab has no effect. Keyboard navigation only begins after pressing Tab once (or after clicking any control with the mouse).The same reproducer behaves differently on macOS, where the first control immediately participates in keyboard navigation.Steps to ReproduceInstall the attached reproducer plugin via File > Plug-in Manager > Add. Run File > Plug-in Extras > Floating Dialog Keyboard Focus Reproduction Without using the mouse, press the following keys in order: Enter Esc Space Shift+Tab Finally, press Tab.A complete standalone reproducer plugin is attached. Expected Resu