Lightroom Classic

EnvironmentAdobe Lightroom Classic 15.3 Lightroom SDK macOS 26.5.1 Standalone reproducer plugin attachedSummaryA floating dialog opened via `presentFloatingDialog()` does not reopen on the second screen. When the dialog is closed while positioned on a second monitor and then reopened, it always appears on the primary screen instead. Steps to Reproduce1. Connect a second monitor.2. Install the attached reproducer plugin via File > Plug-in Manager > Add.3. Run via Library > Plug-in Extras > Run Second Screen Dialog Bug Repro.4. Choose "Test Floating Dialog".5. Drag the dialog to the second screen.6. Click "Close and Reopen".A complete standalone reproducer plugin is attached. Expected ResultThe dialog reopens on the second screen at the position where it was last closed. Actual ResultThe dialog reopens on the primary screen. The position on the primary screen mirrors the saved coordinates — for example, a dialog closed at the top-left of the second screen reopens at the top-l

Description of Issue: The eye icon on the Remove panel stays greyed out.Lightroom Classic Version Number: 15.4 (June 2026)OS Version Number: Windows 11 25H2 (up to date)Camera Model: Canon R6 mk2Step-by-step Reproduction Instructions: In the develop module use the remove/heal/clone on some part of the image.The Expected Result: The eye icon should become active so you can hide the edits.The Actual Result: The eye icon stays greyed out.Image below shows the result:  

I have updated the LR to version 15.3, and since that update I cannot sync the edits across multiple photos with auto sync on while using Smart Previews to edit. Some things, like applying a preset works but adjusting exposure, shadows etc do not propagate through the rest of the images… If I do edit while on library module it will work. This works fine with the source files connected and when LR isn’t using smart previews… also lightroom is slower to apply presets etc than the previous versionHow do you fix 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

I encounter an issue with the latest update (V11) on shortcuts to assign a color label (6,7,8,9).Those shortcuts won't anymore assign a color label, it will now only remove the color label. The shortcut "Assign a color label and go to next photo" (Shift+6 to 9) still work well as previously.Please fix this adobe, my culling speed depend on it. Thanks in advance,

As the title says, While using the Remove tool, the cycle new spot fill type (or Shift + T) shortcut is not working with lightroom classic, my version is Lightroom Classic 15.3.1. Is anyone else experiencing this? I have tried resetting the preferences or holding (Shift + Alt) upon launching the program but to no avail. Any help is appreciated, thank you!

In Lightroom it is impossible to edit a photo as much as we want or need, using Masking regardless of the hardware you have.EXPLANATION Let's say you want to edit a photo with Masking to your heart's content OR because you need to change many aspect of the photo.Logic tells you "we have Masking so obviously it's possible to do masking safely and as much as I want"Reality is that in Lightroom Classic there is an "upper limit" of local edits that we can have on a photo: once we reach that "upper limit" the photo will be be reset.So in Lr it's not possible to sue Masking as much as we want/need.Usually if you have lots, lots of edits on an image other editing software struggle and get progressively slower and slower (if one has powerful hardware generally slowdowns don't happen or appear later) but in LR a photo can reach a point where it's no longer editable and it will be reset NO MATTER THE HARDWARE YOU HAVE. All Masking tools (gradients, sp

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 applying the Color Profile “Adobe Standard” to an image in Lightroom Classic and then exporting as DNG. Then later importing the DNG back into Lightroom Classic, the Color Profile is set to “Adobe Color” instead of “Adobe Standard”.When opening in Photoshop, ACR shows “Adobe Standard” correctly. Lightroom Classic Version Number 15.3.1 Mac OS 26.5.1  Reproduction Instructions:Either use a random image, set the Color Profile to “Adobe Standard” and export as DNG. Then import the DNG back into Lightroom Classic and see it applies the “Adobe Color” profile.Alternatively, import the attached DNG file and see that the Color Profile is set to “Adobe Color”. Open it in Photoshop and see that the Color Profile is set to “Adobe Standard”.Expected Result: Lightroom Classic also applies the correct Color Profile: “Adobe Standard”.The Actual Result: Lightroom Classic applies the “Adobe Color” profile.Lightroom Classic:  ACR:  

I applied Denoise to 115 files by selecting the files, select Autosync, the clicking the check box on Denoise.  After all files complete Denoise, I again selected the same 115 photos, select Autosync, then uncheck denoise.  The process starts and a status bar appears labeled “Removing Denoise on 115 photos”.  The status bar progresses but after a short time stops.  Checked the photos and find the first 21 have had denoise removed.  Did “Optimize Catalog...” and then restart.  Tried to denoise the remaining 94 photos. Same result as before but this time it denoised another 21 photos before hanging up.  Restart, the did the same process to remove denoise on the remaining 73.  This time it removed denoise from 18 before hanging up. LrC is unable to remove Denoise from the entire set of selected photos.   LrC 15.3, Win11 

black and white outline on my pictures in lightroom classic after update  v15.3 ->  Filmstrip 

Bonjour,   bonen années à tous !!! J'ai depuis longtemps des problèmes avec LRC et la synchronisation de collections. certaines photos qui étaient synchronisées deviennent tout à coup problématiques. par exemple ici, j'ai des photos que j'ai modifiées et elles sont depuis plusieurs jours en attente de sync. Je n'ai que l'information d'un probleme qualifié "image". Parfois on a "métadonnées". Je ne sais pas comment interpréter ces informations et en core moins comment corriger. si quelqu'un peut m'aider ... ce problème d'incohérence me pourrit la vie depuis très longtemps et jamais personne n'est arrivé à m'aider ! merci d'avance   coustoulin_0-1768298115756.png about LRC : coustoulin_0-1768299498186.png  

Environment Adobe Lightroom Classic 15.3 Lightroom SDK Windows 11 Standalone Lua script attached SummaryTransparent PNG images displayed in an overlapping layout do not reveal the underlying image on Windows.Instead, transparent pixels are rendered using the Lightroom dialog background color, resulting in visible rectangular artifacts around the overlay image.The same code behaves correctly on macOS. Steps to Reproduce Create an overlapping view (place = "overlapping"). Add a background image (blue PNG). Add a second image consisting of a 45×45 RGBA PNG containing a single red pixel and otherwise fully transparent pixels. Position the overlay image using a child container (f:row with margins). Display the dialog. A complete standalone reproducer is attached. Expected ResultOnly the red pixel should be visible.The transparent pixels of the overlay image should reveal the underlying blue image. Actual Result on WindowsA visible 45×45 rectangle appears around the red pixel.T

Since I updated to MacOS 14.6, printing from Lr Classic to my Epson SCP800 has beeen a nightmare. The printer driver seems to have become completely unreliable.    1. When I select a profile in Lr, the printer driver has color matching set to Epson Color Controls, and not (as it should) to Color Sync. Sometimes the driver opens with Color Sync correctly set, but then changing any other setting (eg, paper type) causes it to revert to Epson Color Controls.   2. When I make changes to the print settings (eg, changing paper type) and save a preset, the change is not present in the preset. This problem does NOT seem to occur when using the print driver from Apple Preview.   I have -- reinstalled the Epson drivers -- deleted and readded my printer -- deleted my Lr preferences (but I'm confused about this because moving the com.adobe.LightroomClassicCC7.plist file out of ~/Library/Preferences doesn't seem to change anything in my Lr setup, even if I restart my machine

After updating to LHR classic 14.1.1 LHR stops shwoing metadat in the lybrary module as well as in the developement module (loupe info). Closing LHR and deleting the files: ...Helper.Lrdata, ....Previews.Lrdata as well as ....Sync.Lrdata helps, as they are created each time new when starting LHR.  But after working for about 10min all the metadata disapears again.  I have installed LRH fresh and reset all settings. Nothings seems to help. I have a attached a screenshot but I wonder if that helps - there is just that spinning wheel.     Any suggestions?    P.S. I have a large catalog with about 200.000 photos in it but have had no issues so far. Big Windows PC with plenty of power. 

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 got this error after upgrade to LrC 15.0. Update 15.0.1 not fix this issue.   "Lightroom has encountered problems reading this photo. You will not be able to make adjustments to this photo."   My photos file are OK, restart LrC will able to edit again, but it will happen again sometimes after I sync the photo setting form one photo to another one.   OS is macOS 15.7.2.

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

I re-edit a photo from Lr Classic in Photoshop. It is in my target collection which is my sync collection. Lightroom Classic says the sync is done. The new version is visible in Lightroom on the web (Chrome). The thumbnail in Lr Mobile is correct. When I open the image in Lightroom Mobile it reverts back to the old previously edited version. Thanks

I exported 479 photos to a folder with “Add to This Catalog” selected.  The export proceeded as expected but the operation to add the photos to the catalog was painfully slow.  It was taking 4-10 seconds for each image.  During the time to add the photos to the catalog all other importing operations are frozen.  During the extended add photos operation LrC is consuming about 7-10% of CPU.  The rate at which photos were added to the catalog is much slower than other operations that add photos to the catalog.LrC 15.3Win11 

Short description:When importing RAW and/or JPG files from my Fuji X-T5 into LrC, despite selecting the "Do not import possible duplicates" function, no duplicates are recognised and all images that have already been imported are imported into LrC again. A “-2” is appended to the file names.Duplicates of my RAW files from my Canon R5 II are recognised as such and are not imported. All settings are the same in both cases.LrC 15.2, macOS Tahoe 26.3, iMac with M3LrC 15.2, macOS Sequoia 15.7.4, MacStudio with M4 MaxLrC 15.2 Windows 11 lasted VersionLong Description:The problem I described above, whereby RAW files from the Fuji X-T5 are not recognised as duplicates during import and are therefore not imported, is a little more complicated than it seems.One type of import works, but the other does not.It works when I import the images as follows:1. Connect the camera directly to the iMac -> import > all images that have not yet been imported are offered for import. Images that were imp

After the latest update I’m observing the following issues:Red Eye Correction tool When activated, the entire image is covered with an orange overlay, which makes the tool unusable. Denoise performance and behavior Running Denoise on a larger batch (approx. 100 files) is noticeably slower than before. There is no clear indication of remaining processing time. Overall responsiveness during background processing While Denoise is running in the background, Lightroom becomes largely unresponsive. Image refresh is significantly delayed, and even basic adjustments (e.g. tonal corrections) take a long time to update. Hardware utilization GPU usage reaches 100%, while CPU (14 cores) shows minimal activity during Denoise.System:Adobe Lightroom Classic version: 15.3macOS version: 15.7.4Hardware: Apple MacBook Pro 14-inch (M4 Max), 36 GB RAM.

In the Send Book to Blurb function first the pages are rendered. Thereafter the upload takes place, during that second part the upload is very often stopped with this pop-up:Error appearing many timesThe pop-up shows very often, like dozens of time (100+ page book, 300+ images). The interval between messages does not seem to be fixed.This is the behavior of machine network while sending (between the errors):Data sent while continuingUnknown if this is normal…The progress bar does continue to go forward, so progress seems to happen between the errors. However, as too many errors are given no full book is uploaded currently.The screenshot is using a cable connection (from machine to router), using WIFI gives the same.This is behavior is observed in the LrC 15.3 and 15.2.1 and previously in early 2025 (LrC version unknown).Machine is Microsoft Surface, current version of Windows, ARM64; further info in attached file.

OS: Windows 11LrC VERSION: 14.5A couple of days ago I upgrade to v14.5.As for every update, I regurlay empty cache, optimise catalog, remove all previews and generate new standard ones (also, I wanted to test how was was the new option to use GPU for generating previews).Never had a problem with this workflow.After previews generation process was completed (1h 30m for 29.000 files, 23.000 jpegs and 6.000 raws) I got an error: for 21 RAWs the preview could not be generated. Looking in the catalog at those files, I realised they have an exclamation mark on a dark circle: this is not the missing photo mark. If I click on the exclamation mark, I see error "Lightroom has encountered problems reading this photo, you are not allowed to edit this image. " Yet, I can still enter develop module and edit the photos without any problem: the editing history is there, I can zoom in at 100% (generating the 1:1 preview), I can change sliders, export... Everything... (PS: I do not use smart previe