Lightroom Classic

Recipe:  When the secondary window is in grid view, it doesn’t always respond to the keyboard shortcuts “f”, Escape, or Shift+g.  To reproduce on LR 15.3 / Mac OS 26.4.1, follow these precise steps (see the attached screen recording): 1. In LR, go to Grid view, close the secondary display window if it’s open, and do Window > Screen Mode > Normal 2. Restart LR. 3. Do the menu command Window > Secondary Display > Grid to open the secondary window in Grid view. 4. Select a thumbnail in the secondary window and type “f”. Observe that nothing happens (incorrect). 5. Do the menu command Window > Screen Mode > Full Screen Preview (the command invoked by the shortcut “f”) and observe that the image is displayed in full screen. 6. Type Escape to exit full screen preview and observe nothing happens (incorrect). Typing “g” and Shift+g also have no effect (incorrect).   7. Type Cmd + Tab and then Tab to switch to an app other than LR. LR is now no longer in full screen mode. 8. C

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 am so SAD!  I have bought a new Macbook M4 Max However, Lightroom CC lastest version, cant EXPORT slideshows as videos! the progress bar is stopped at nearly 10% position. No matter if I wait several hours it won't move any progress = I Cant export slideshow as Video   I always used this function, for a few years, day by days   I uninstalled the LR and tried reinstalling it, but it still failed. Does anybody have the same issue?I wonder if it is a problem related to M4 chips. Please kindly help and fix please!

System: Mac M1 Air 16gb/512gb OS: Sonoma 14.3.1 LRC Version: 13.1 Release ---------------   Three Issues: 1) I have a preset folder with six custom presets.  When doing multiple exports using the batch export feature, LRC often doesn't launch the same number of processes as there are presets selected.  I select 6 presets and it will only do 4 sometimes, 5 others.  Sometimes it does all 6.  I have to examine the export folder, see which ones it missed, and go back and re-export the ones it didn't do.  Annoying.   Potential Fix:  If LRC can't do all of the processes because of system limitations (I don't know why on a Mac M1 that would be the case), at least inform the user which ones are being done and which are not.  Perhaps a loop to do sets consecutively with proper UI notification would be a good approach.   2) When doing multiple exports, a dialog comes up for each process, "Preparing to export".   "number of processes - 1

[This bug report was originally posted on 1/26/2019 in the old feedback forum, but it never got transferred here. See the attached email message.]   In LR 14.3.1 / Windows 11, when LR is in  Window > Screen Mode > Full Screen, floating dialogs always appear hidden in back of the main LR window, and calling the toFront() function has no effect. This prevents my Any Crop and Any Filter plugins from being used in Full Screen mode. This doesn't occur in the other screen modes, nor does it occur on Mac OS 15.5.   This simple plugin demonstrates the bug:https://www.dropbox.com/s/6d1l3llo5dwzzuw/floatingfullscreenbug.lrdevplugin.zip?dl=0 Simply invoke Library > Plug-in Extras > Floating Dialog in the various Screen Modes. The command executes this simple code: LrDialogs.presentFloatingDialog (_PLUGIN, { title = "Floating Fullscreen Bug", contents = f:push_button {title = "Push Me"}, onShow = showErrors (function (t) LrTasks.startAsyncTask (s

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.

EnvironmentAdobe Lightroom Classic 15.4 Lightroom SDK Windows 11 Standalone reproducer plugin attachedSummaryA floating dialog opened via presentFloatingDialog() does not consistently receive keyboard input.The same floating dialog implementation exhibits two different behaviors depending on the SDK calls executed immediately before the dialog is created.In one case, keyboard input is routed to the floating dialog immediately after opening.In the other case, keyboard input remains with Lightroom, allowing Lightroom keyboard shortcuts to continue working while the floating dialog is visible.A complete standalone reproducer plugin is attached. Steps to ReproduceInstall the attached reproducer plugin via File > Plug-in Manager > Add. Run via File > Plug-in Extras > Floating Dialog Keyboard Input Reproduction. Choose one of the two test configurations: Plugin dialog receives keyboard input Lightroom receives keyboard input Press the Tab key.A complete standalone reproducer pl

Lightroom Classic Version15.4.1macOSTahoe 26.5.2HardwareMacBook Pro (Apple Silicon)DescriptionExport as Catalog consistently fails when the destination is an external exFAT SSD.After several minutes Lightroom displays:“An unknown error occurred while exporting the catalog.”The partially created export folder is then deleted.The identical export succeeds immediately when the destination is the internal APFS SSD.ReproductionOpen any Lightroom catalog. Choose File → Export as Catalog. Select an external exFAT SSD. Export with or without negatives. Wait. Lightroom reports “Unknown error occurred while exporting the catalog.”ExpectedCatalog exports successfully.ActualGeneric error.Export folder deleted.Reproduces onSamsung T9 (exFAT) SanDisk Extreme SSD (exFAT)Does NOT reproduce when destination isInternal APFS SSD.The same catalog (approximately 415 GB including negatives) exports successfully to the internal APFS SSD in a few seconds. The resulting exported folder can then be copied to th

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.

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

When importing Leica M11 DNG files using Adobe Default (as shown in the Preferences / Presets -- Global setting) Adobe Standard is applied as the Profile instead of Adobe Color.  When I create and specify a Preset which specifically uses Adobe Color as the Profile, Adobe Standard is still applied.  If I specify to use Camera Setting, then the embedded M11 profile is correctly applied.  As a work-around,  I can indeed force the Adobe Color profile to be applied if I specify it as the Apply During Import - Development Setting (right-hand panel when importing) and select under the Defaults presets - Adobe Color + Lens or similar. [Moved to Color Management by moderator authority]

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

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

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   about LRC :  

Description of IssueLR Classic fails to import TIFF files with deflate/zip compression.Lightroom Classic Version Number (Help>System Info…) Lightroom Classic version: 15.3 [ 202604090947-8f3672ed ]License: Creative CloudLanguage setting: en-NLOperating system: Mac OS 26Version: 26.3.1 [25D2128]Application architecture: arm64Logical processor count: 8Processor speed: NASqLite Version: 3.36.0Adobe GSDK Version: 1.4.0.213OS Version Numbermacos Tahoe 26.3.1 (25D2128) Camera Model (sometimes necessary)n/aStep-by-step Reproduction Instructions (in precise terms, please)Import the following sample image in LR classic:https://drive.google.com/file/d/14eazJOmOZ1XALHYXqae16sXBuZf9bZ_d/view?usp=sharingThe Expected ResultImage imports correctlyThe Actual ResultErrors: “preview unavailable for this file” and “Could not read preview”. No image is shown.Further details:Hi, developer of PTGui here. PTGui now outputs TIFF images with deflate/zip compression by default. It’s fast and efficient and th

I have encountered an instance where a wide gamut orange colour appears desaturated in HDR editing mode. I have the uploaded output PQ HDR AVIF files to https://andrewkeyanzhe.github.io/posts/Lightroom_vs_darktable/ for comparison. My website serves the uncompressed HDR AVIF files, so you should be able to see the difference on an HDR capable device and browser (e.g. Macbook Pro with XDR display with Google Chrome)   The camera used is the Panasonic Lumix S5ii   Details:  Version of the app - Lightroom 14.2 (Camera Raw 17.2), Lightroom mobile v. 10.3.1 71F6C8/202 Platform and OS version - Macbook Pro 16 M1 Pro, macOS Sequoia, iPhone 14 Pro Max, iOS 17.5.1 Basic steps to reproduce the problem - Download the raw file https://drive.google.com/drive/u/0/folders/1YIhkxHvp77HHTaanyFJ5LXX28jH74Rau , open in Lightroom, turn on HDR editing mode, increase the exposure by 3.4 stops so it matches https://youtu.be/0FYjApop7Mk?si=S-cXCX-0hyAvsT

On macOS Tahoe, Lightroom Classic overshoots when navigating with arrow keys on MacBook Pro models with ProMotion enabled. Setting the display refresh rate to 60 Hz immediately eliminates the issue. Reproduced on both M1 Max and M5 Max with fresh macOS and Lightroom installations. Does not occur on an M4 MacBook Air (60 Hz display).

Lightroom Classic 15.0.1, Windows 25H2 26200.7171, Nvidia GeForce RTX 3060 (32.0.15.7602)   I took a photo of a bunch of fish swimming around behind a glass window. I wanted to use both reflection removal and AI Denoise. According to this page, I perform the AI Denoise first.   Here is the photo I used: https://www.dropbox.com/scl/fi/2zqjndbvb4i2mcwqqrgku/PMC_3135.NEF?rlkey=gq1w1mwdiu86oab9avto3wj9i&st=bi4tyj72&dl=0   Here is a screen capture of the unedited version of this photo, you can see reflections as well as noise       Here are the steps I followed:   1. AI Denoise, slider at 50, works as expected, noise is reduced.  2. Distraction Removal: Reflection, slider at 100. Reflection is not removed. Here is a screen capture after both steps, the noise reduction remains effective, but the reflection is not removed.     Also, please note that if I perform the steps in the opposite order (Remove Reflections first, the reflections are removed) but when I then add on the AI Deno

Lightroom Classiv v15.3 (on Mac OS Tahoe) has a problem importing photo files that have a pipe symbol - a | symbol - in the XMP field dc:subject.Lightroom apparently has a problem interpreting the pipe symbol, and then hangs, seemingly indefinitely until the import is cancelled, while showing a high level of CPU usage. This hanging seems to take place at the end of the import process for this photo.The pipe symbol is used by Lightroom to separate levels in the keyword hierarchy within the Hierarchical Subject XMP field.  Having pipe symbols also within the keywords doesn’t seem to be a problem with the Hierarchical Subject field - at least it doesn’t interfere with importing.  Also the pipe symbols in the Weighted Flat Subject field don’t seem to cause a problem with imports.Attached is a sample file that hangs when being imported into Lightroom.  Of course, a problem file causes a batch import of photos to fail, with some number of files correctly importing until Lightroom does to pro

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.

Synchronize Folder > Scan For Metadata Updates can cause frequent spurious metadata conflicts for TIFFs that are stored on NAS.  Over the years many people have reported spurious metadata conflicts that Adobe hasn't been able to track down, and many of those reports involve photos stored on NAS.  Here's a recent report:https://feedback.photoshop.com/photoshop_family/topics/before_after_comparison_of_metadata_conflicts...While the particular use case here may not be that common, it may provide a reproducible test case that points to the bug (likely a race condition) underlying all those other persistent reports.Here are the steps that consistently produce the spurious conflicts in my configuration:1. Connect to a network volume on a 2013 iMac running MacOS 10.14.6. The volume is mounted with SMB 3.0.2.  2. Place 4 1800 x 1200 TIFFs (about 13 MB each) in a folder on the network volume.3. Import them with Add into a LR 9.0 catalog running on a 2019 Macbook Pro

This bug causes DATA LOSS.Description of Issue After viewing duplicates using the new LR15.4 Find and manage duplicate photos feature, and marking some photos (either Original or Duplicate) as Rejected, the use of the “delete rejected photos” function (e.g., through the keystroke cmd-Delete) will cause all photos to be deleted from disk and from the catalog, not just those marked for rejection. Lightroom Classic Version Number (Help>System Info…) Lightroom Classic version: 15.4 [ 202606101834-493069d4 ] OS Version Number ​​​​​​​MacOS 26.5.1 (25F80) Step-by-step Reproduction Instructions ​​​​​​​add a photo, and a duplicate of that photo, to a LR catalog. switch to Duplicates view; the two photos should appear in a stack. mark one of the two photos Rejected. cmd-Delete to delete rejected photos confirm. The Expected Result ​​​​​​​only the Rejected photos disappear from disk and the catalog. The Actual Result ​​​​​​​all the photos - even those not marked Rejected, disappear fr

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?

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!

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