Design the future of fashion, win Firefly Pro 👗✨
Bug Reports
Recently active
Bugs should only be reported for the latest or current version of Lightroom Classic. If you believe you have a bug, it must be verified on the latest version of Classic. New bug reports will not be accepted for older versions of the software. If you believe you have encountered a bug, it is important to first search the existing bugs to see if your issue and a possible solution or workaround have already been reported. If so, please add to that thread. If not, it may be prudent to start a new thread.Greater than 90% of the bugs reported are not actually bugs. Before starting a new thread, please read:P: Do I post in Discussions or Bugs? When logging a new bug report, it's required by the Lightroom Classic team for the information in the report to include steps to reproduce the bug experience. Once we can reproduce an issue, then we can start to investigate a fix. Bug reports without reproduction steps will be moved to discussions.If, after some troubleshooti
Select a number of photos say about 200 on the film strip. auto sync on Hit auto to adjust the settings automatically. Can be done on library or develop module does not matter to the issueLightroom will adjust the settings automatically and you can go to different photos and the automatic settings would have been applied to all the photos.Now adjust one setting on one photo with auto sync on (eg. bring the vibrance or saturation down back to 0 or a different amount….in this case vibrance to -5)Browse the rest of the photos … The rest of the photos should now have auto adjustments applied + the vibrace slider to where you adjusted it manually. However when I do this other than some photos that are in immediate to left and right of the photo that was active while I did the vibrance adjustment the rest of the photos has the auto adjustments back down to 0 and the only vibrace is at -5. This seems to affect tone and vibrance saturation.. not presence (probably because auto does not affect
When cropping a landscape-oriented photo to a portrait orientation, you can easily do so by dragging with your mouse.However, you cannot crop a portrait-oriented photo to a landscape orientation using the mouse in the same way.In Camera RAW, you can perform both types of cropping using the mouse.Pressing the "X" key allows you to toggle between portrait and landscape orientations.*To start cropping, begin dragging from near the center of the image.Lightroom Classic 15.6 , CameraRAW18.7 , Win11
I see multiple instances of this issue from years ago, and a bug that was reported as fixed in the 11.3 release notes. But I wanted to report I’m still seeing it in 15.6:Printing an uncropped iPhone landscape-oriented photo in the Print module, using “Zoom to Fill” and 4x6 paper. The output is a wider aspect ratio, so requires cropping the top/bottom of the photo. If I drag to display the very bottom of the photo and crop the top on screen, the print output is the opposite: keeps the top, crops the bottom. And vice versa if I drag in the other direction.
Beim Import von Videos meiner Nikon Z6iii nach LrC kann kein Vorschaubild angezeigt werden und auch der Import wird mit Fehler abgebrochen. Die Videodatei ist fehlerfrei und kann mit einem z.B. VLC media player angeschaut werden. Der Import von einer Sony DSC-HX66 funktioniert.
Une fois mes photos retouchées, je veux les exporter. Certaines photos s’exportent, d’autres non.Généralement les photos avec visages sont celles qui ne s’exportant pas.Je ne peux pas créer de copie virtuelle de ces photos. Je peux seulement les ouvrir dans Photoshop via Lightroom et les exporter depuis Photoshop.Version Lightroom Classic 15.6
See description above
When I switch on the slide-show modus = manual I get the message"Manual mode does not support these settings".The maximum show-time in automatic-mode is 20s, which is sometimes not sufficient to talk about the pic with friends, hence I'd like to run the slides in manual mode.When I search in Google for this issue I get hints, that I should switch off music etc., but I have no music-file attached. Another hint says that this message is an system-issue and can be ignored, it should run anyway: which is not true. The show runs for e.g. ten pics, then it freezes and stops.
Description of IssueI defined in a plugin a custom metadata "Intent", of type “enum”, which can have any of the following values: "Expressive", "Personal", "Documentary" (the plugin code is here: https://github.com/mrzgll/ma-intent-metadata).The metadata is set by the user in the metadata panel. In order to check if there are any photos with Intent not initialized (i.e. nil), I created a Smart Collection with the condition "Intent" is "No Value.The Smart Collection works correctly, showing all photos whose ‘Intent’ metadata has not been assigned yet.If I reopen the Smart Collection I always find the condition changed: "No Value" is no longer there, there is a blank field instead. If I save this Smart Collection, it no longer works.Lightroom Classic Version Number15.6OS Version NumberMicrosoft Windows 11 ProVersion 10.0.26300 Build 26300Step-by-step Reproduction InstructionsLaunch Lightroom Classic Open a catalog of your choice (it shall contain at least 1 photo) Install and activate
System Windows 11 desktop built by Puget Systems 32 GB RAM NVIDIA GeForce RTX 3070 Ti, 8 GB VRAM Current Lightroom Classic 15.6 release Catalogs and previews on internal SSD; original photographs on internal drives ProblemLightroom Classic has become extremely sluggish and frequently hangs on my Windows 11 desktop. Operations that should be nearly instantaneous can take many seconds or longer. The problem occurs in Library and Develop and makes Lightroom impractical to use.The same photographs and edits perform substantially better in Lightroom Classic on my MacBook Pro Max.Reproduction with a new catalogMy principal aurora catalog contains approximately 76,000 photographs. Initially, I suspected a problem with that catalog or its previews.However, I created an entirely new Lightroom catalog on the Windows desktop and imported a small selection of DNG photographs. Import completed in less than one minute, but the new catalog exhibited the same sluggishness and hangs.A separate,
The aspect ratio changes when cropping a landscape-oriented photo into a portrait orientation using the Crop tool.A: When the Crop tool is active and the "X" key on the keyboard is pressed.B: When the Crop tool is active and the image is dragged vertically using the mouse.The resulting aspect ratio differs between methods A and B.Please investigate this and provide a fix. Original resolution 6742 x 4480pxA:4480 x 2987pxB:4480 x 2983pxLightroom Classic 15.6 , CameraRAW18.7 , Win11
Immediately after importing new photos into Lightroom Classic, the SDK appears to expose an inconsistent or stale catalog state to plug-ins.In my case, two problems occur at the same time: catalog:getTargetPhotos() returns only one photo regardless of the actual selection in Lightroom. Keywords that have just been assigned to the newly imported photos are not reliably available to the plug-in through photo:getRawMetadata("keywords"). Closing and restarting Lightroom Classic immediately fixes both problems without making any other changes.After restarting Lightroom, the exact same plug-in code correctly detects the selected photos and the keywords assigned before the restart.Environment Lightroom Classic: [insert exact version from Help > System Info] Operating system: Windows 11 Lightroom Classic SDK plug-in Catalog containing an existing hierarchical keyword structure Newly imported RAW files Steps to reproduce Start Lightroom Classic normally. Import a new set of photo
After updating from 15.5.1 to 15.6, the dialogue boxes are FAR brighter. The medium grey has been replaced with much brighter elements. I ended up rolling back to 15.5.1 because of this!when will Adobe follow Mac’s dark mode? And at least not make things BRIGHTER!this interface won’t let me attach images?
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
Lightroom Classic synchronization has been stalled for an extended period, initially under version 15.5 and continuing under 15.6.Approximately 1,400 photographs remain pending. Lightroom Classic displays the status "Uploading" with "Image" in the sync details.Steps to reproduce Open Lightroom Classic with synchronization enabled. Observe that existing photograph uploads remain stalled. Import a new JPEG from local Mac storage, independently of NAS storage. Create a new collection and enable synchronization. Add the JPEG to that collection. Verify that the collection appears in Lightroom Web and Lightroom Mobile. Observe that the photograph itself never uploads. Expected resultBoth the collection and its photograph should synchronize successfully.Actual resultThe collection synchronizes, but the photograph remains queued. Existing uploads also remain stalled.Previously, restarting Lightroom Classic advanced synchronization by approximately four photographs before stalling a
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
Lightroom was working perfectly this morning.. I come to load in new images and edit some while sitting here.. and as soon as Lightroom opened up - I tried to slide exposure (and other ones to test those...) and the slider immediately jumps one way or another. I have reset preferences, turned off GPU.. NOTHING is helping.. please help me!
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?
I updated to LrC 15.5 a few hours ago. Since then LrC has problems with video files. The first problem I noticed was that when I tried to synchronize a folder that had two new video files. After a couple of minutes I got the error message “An unknown error occurred while reading the video file. (2)”. I had just completed those files with DaVinci Resolve so I went back and produced the same files again to check if DR had made an error. When I tried again with the new files but got the same errors. I was able to play both videos without any issue using VLC Media Player, so they seem to be OK. I then shutdown LrC and did a backup including optimizing the catalog, and then restarted it to see if that made any difference, but same error. Then I started looking at other videos that were already in LrC and found that when browsing them in the Library module, most of them pop up a message “There was an error working with the video”. They will not play in LrC but work fine with VLC Med
any step to create a pic with LR is sooooo slow. whats up ? bugs ?? please repair your performance
Camera profiles that contain two DNG 1.6/1.7 profile features load and can be selected, but the features have no effect on the rendered image:RGBTables (tag 52543 / 0xCD3F) ProfileGainTableMap2 (tag 52544 / 0xCD40)This applies to external DCP profiles and to profiles embedded in DNG files, in Lightroom Classic and in Camera Raw in Photoshop. The DNG SDK 1.7.1 parses both tags in camera profiles, and its reference rendering applies them to the same files.Test 1 – RGBTables (SDR)Two DCPs for the Nikon Z 7, identical except for the RGBTables payload: one with an identity table, one with a defined chroma change. Each is a group (ProfileGroupName) with an SDR member and an HDR member (ProfileDynamicRange). Installed in %APPDATA%\Adobe\CameraRaw\CameraProfiles, Lightroom restarted. Applied to the same raw file with identical neutral settings (white balance As Shot, all sliders 0, sharpening and noise reduction 0, linear tone curve), HDR editing off. Exported as 16-bit TIFF, ProPhoto RGB. Res
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.
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.
I recently got a 5D IV and just noticed that capture times on video files shows 5 hours ahead in Lightroom (photos are fine). This causes videos taken late in the day to be imported into the folder for the next day. I'm running the latest Lightroom (6.10) and 5D Firmware (1.04). I checked my old 5D Mark III videos and they are fine. I suspect Lightroom ins't picking up the timezone info and is using UTC time. Is this a bug?
My basic issue is that Library previews do not update reliably in Lightroom Classic after work is done on a TIFF file in Photoshop, whether the “edit (original) in Photoshop” command is used, or the file is simply opened from the Finder and edited. It started a few months ago. It’s intermittent: sometimes previews update immediately, perhaps half the time, though it seems to be getting worse. Sometimes I can force Previews to update using one of several methods gleaned from this forum or other research (see below), sometimes nothing will work except re-saving the file in PS, then reimporting it to LR, OR making an (un-needed) adjustment in the Develop module to trigger preview update in Library. The excellent Lightroom Queen web site suggested I try a bug report as they couldn't come up with a solution for me. After several weeks troubleshooting I’ve learned that making an adjustment to a parameter in Develop, even a very small one, seems to trigger the preview to appear correctly
Remix with Firefly Community Gallery
Thousands of free creations to fall in love with and remix in Firefly.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.