Design the future of fashion, win Firefly Pro 👗✨
Connect with fellow editors in our Lr Classic community.
Recently active
Lightroom Classic v15.6 brings a smoother editing experience with improved Reflection Removal, making it easier to clean up reflections in windows, glass, and water. This release also introduces faster masking controls with Check All and Check None options, along with support for new cameras, lenses, and important bug fixes. What’s NewThe September 2026 release of Lightroom Classic v15.6 brings meaningful improvements designed to make photo editing faster and more precise. The standout enhancement is Reflection Removal, which now delivers cleaner results when removing reflections from windows, glass surfaces, and even water. The updated technology reduces smudges and ghosting artifacts, helping photographers recover details more naturally in challenging scenes.This release also streamlines masking workflows with new Check All and Check None options in the Masking panel. When creating landscape or people masks, you can now instantly select or clear all available mask options with a sing
When presented with a New Post screen in the Adobe Community, you are given three options for Conversation Type: Discussion, Bug, and Idea. If you were searching in Discussions, the New Post window will default to Discussions. If you are searching in Bugs, the New Post window will default to Bugs and likewise for Ideas. Many customers instinctually report problems they are experiencing as “Bugs”. It is natural to think that a problem you are having might be a bug. A bug is defined, for our purposes, as “something in the software that is not functioning as it was designed to function”. Interpreting whether a behavior is a bug or not is not always easy, however. Here are some reasons why you might want to consider posting first to Discussions rather than jumping straight to reporting in Bugs: Most items reported as Bugs are not actual bugs. In a typical group of reported bugs, only about 3 out of 25* bugs reported turn out to be actual bugs. Of those, typically 2 ou
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
Adobe is excited to receive requests for additional features you need to enhance your workflow. What can you do to increase the chances of being heard? Don't use the words "Feature Request" in your post's title. Search for and add to existing feature requests rather than creating duplicates. There is no advantage to creating a second request for any existing feature request. One request per thread!When creating an Idea or Feature Request thread, please keep requests for features to ONE request per thread. Doing this will allow others to vote on a single, specific feature and not confuse Upvotes amongst a list of feature requests. If an Idea thread has multiple requests in it, a moderator may ask you to split the multiple requests up into multiple threads so others can vote. In the event there remain multiple requests on a thread, the first item requested will be the arbiter of where the thread will be cross-referenced or merged. Describe how the featu
I am setting up a lab of 30 laptops for a high school art class. The teacher has requested Lightroom Classic, which is the only one we have with Adobe Creative Cloud licensing (shared-device licensing). I understand that this operates using a SQLite database so running on network drives is not possible. However, we do not allow our student accounts to access the local drive on devices they log into, so they aren’t able to create local catalogs.I’ve been toying with a script to essentially run LrC out of a scratch folder in C:\ProgramData\, uploading their files to their network drive on LrC closing, and pulling those files back down into the scratch folder on LrC startup. I’m not sure this is the best way to do things, as it really can’t elegantly handle multiple catalogs and can’t account for student behaviors such as logging off before closing the program, or changing the name of their catalog.Any advice at all for how to deploy this would be greatly appreciated. Even if the advice i
In develop module, even if idle, the CPU usage is 60-85% at all times, what causes the browser to slow down and the entire system slows down. As soon I switch to Library, CPU usage returns to minimal. As soon I return to Develop, the CPU jumps back up, even listening to a video in 720p is not possible. Browser chokes for seconds, frames freeze and skip. I run W11 Pro 26H2, OS Build is current 26300.9711The hardware is a Dell 5820 with:Processor Intel(R) Xeon(R) W-2223 CPU @ 3.60GHz (3.60 GHz)Installed RAM 48.0 GB (47.7 GB usable)Graphics card NVIDIA RTX PRO 2000 Blackwell (16 GB)Storage 11.06 TB of 22.32 TB usedSystem type 64-bit operating system, x64-based processor
I experience sync issues in Lightroom Classic for some photos when I add them to a Collection that is synched to the cloud. Only photos that contain Generative AI remove operations are affected. The photos were edited before attempting to add them to a synched collection.I am running Lightroom Classic 15.5.1 on an M4 Pro Mac mini that runs MacOS 26.7.I have found a partial workaround, but it is slow and time consuming. The affected photos appear in the Sync Errors group in the Catalog area at the top of the LH panel. For each of the affected photos, I have to regenerate all of the Removal objects to completely regenerate the data; I have to select each removal object individually to regenerate because there is no bulk operation for a photo. On some photos this may additionally have consequences for masks and I often have to also refresh the masks.Regenerating the AI removal objects does not by itself immediately fix the sync - Lightroom remains stuck. For the sync to complete, I need t
I had a Windows 11 Laptop which failed. I decided to go Mac when buying a replacement.I rocovered the Catalogues and the like off the Windows 11 laptop and moved to my Mac and the main root Catalgue works fine.The problem is I have is that on the windows machine i moved photos to a NAS. These are what I cannit acces now on the Mac. I get an Invalid Path error.As I understand it the problem arises with the “path” being in windows format (UNC) rather than Mac format.Is there a fix for this as I don not want to try and remap NAS folder so to speak.
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?
Hi everyone! I’m switching from Canon to Sony.Lightroom Classic offers Camera Matching profiles for the Sony A1, but not for the A7 V, and my RAW files just don’t look good without them.Does anyone have any ideas on how to improve the colors and skin tones while waiting for Adobe to add Camera Matching profiles for the A7 V?Any tips or workarounds would be greatly appreciated!
Hello,I'm attaching the warning I get and let's see if anyone can think of what may be happening. I use Lightroom to save, classify and edit my photos. It's been a week since I saw for the first time the screenshot that I put in which it says: Lightroom has encountered problems when reading this photograph.You will not be able to make adjustments to the photograph. When marking them one by one to see what they had in common I have found that it happens to me only with t The photos taken with the M11-POnly the DNG and when I shoot RAW + JPG the notice never comes out in the JPG and if in the RAW.They are also photos that have been edited.I have seen that an unedited photo when editing it even if it was just cutting, then I got that warning But it doesn't happen to me with all of them... it only happens with some imports. That is to say, photos that I have taken on a trip and that have been imported all together they come out. I have checked the lenses and it comes out with all the ones
J'ai des problèmes de synchros sur LRC sur des photos avec beaucoup de calques. Il n'envoie pas tout dans le cloud (ce alors que je suis en vert la liste est vide), quand je récupère sur Lightroom mobile il en manque régulièrement je dois jouer avec l'historique des versions pour retrouver la dernière.Tout est en dernière version et je n’ai pas de problème signalé dans Lightroom web.
Lightroom Classic is crashing when trying to select the background mask tool.
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
hice actualización de la versión de LrC ultima y cuando utilizo herramientas como eliminación de ruido, mascaras, aparece una ventana de error y se cierra el programa, regrese a la anterior y el problema sigue. regrese a la versión 15.6 el problema sigue, parece que cuando se conecta con la nube surge el problema.
How to turn off display of milliseconds (capture time). Milliseconds are useless to me, but they clutter the grid view and make it impossible to quickly review capture time for long burst of bird photos when trying to determine when a burst ends and a new beginning. Just want to turn off the milliseconds and keep the seconds (as in the previous version)
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
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
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!
This happens in all “local edit” modes, such as brushes, gradients, “select subject” etc.In these tools, the “white” and “black” sliders behave weirdly, almost as they are editing a jpg. There is no latitude in the edit, even though it’s there in the original file: the same sliders, in the full image mode, work perfectly fine. it’s much quicker to provide an example so I’ll attach screenshots.https://imgur.com/a/rXdu48p (uploader not working today... I used imgur then) as you can tell, in the screenshots on the right i can pull whites to recover sun spots, and push blacks to recover detail in the furniture. on the left, doing the very same edit with brushes, both whites and blacks are severely clipped. this has been happening forever, I’d love to see it fixed especially for recovering sun spots.
Depuis hier les modèle IA ne charge plusJ’ai désinstallé puis re installé LRC sans succès.. En mode ADM pareilCi-desous le log correspondantQue faut il faire ?Report link
Lightroom Classic 15.6 – Both monitors go black during AI Reflection Removal processing (Best Quality, RTX 4090)Issue DescriptionI'm experiencing a critical issue with Adobe Lightroom Classic 15.6 when using the AI-powered Reflection Removal feature.After activating Reflection Removal with the processing quality set to Best, Lightroom begins processing the image and displays the green progress bar.However, shortly after processing starts, both connected monitors suddenly turn completely black.The computer remains powered on: the system fans continue spinning, and the LEDs on the motherboard and NVIDIA GeForce RTX 4090 remain illuminated.Neither monitor recovers automatically, and I have to restart the computer to restore display output.Steps to Reproduce Launch Adobe Lightroom Classic 15.6. Open an image in the Develop module. Enable the AI-powered Reflection Removal feature. Set the processing quality to Best. Start processing the image. Lightroom displays the green progress
Whenever I try to apply a preset, any preset, this message pops up. “Downloading AI ModelsSome AI Models are downloading. Please try again later.”There’s nothing wrong with my internet, or disk space or anything really. It literally just started happening after an update I did (v15.3.1). I’ve uninstalled, reinstalled a few times, same thing. I can’t apply any preset, but lightroom can still function properly as normal. Can anyone help?
You have issues with your latest LrC update. Also with this webpage as it just trashed my last attempt to report these bugs. Please fix this webpage! These issues, which never occurred before your last update now occur EVERY TIME I use my normal workflow.That workflow: Import my raw NEF file Enter “Develop” Use the <File><Plug-in Extras><Process with Topaz Photo (Studio) Let Topaz run its automatic noise reduction and, optionally do some other stuff such as sharpen (but not required to reproduce the bugs described below) Return the denoised DNG file from Topaz back to LrC and enter Develop module Attempt to enter masking. DOES NOT WORK. Change Profile from the default “Camera AUTO” to “Adaptive Color”. Now I can enter masking. But… Subject masking DOES NOT WORK. When I attempt it, the masking subwindow pops up and immediately disappears. Object masking works and I am forced to use it to get my work done. Once I’m done, I go to export my photo. I get the normal po
Before updating to LRC 15 last week I routinely blitzed through bulk HDR merges of dozens of images in just a few minutes, as well as other dng processing/import from DXO Pure Raw, and now these tasks are taking an exorbitant amount of time to complete. This is destryong my work flow at a critical time for my clients. Any help is greatly appreciated... thanks! System info here: Lightroom Classic version: 15.0.1 [ 202511041508-dddee541 ]License: Creative CloudLanguage setting: en-USOperating system: Mac OS 15Version: 15.6.1 [24G90]Application architecture: arm64Logical processor count: 14Processor speed: NASqLite Version: 3.36.0Adobe GSDK Version: 1.4.0.171 Power Source: Plugged In, 100%Built-in memory: 36,864.0 MBDedicated GPU memory used by Lightroom: 2,498.5MB / 27,648.0MB (9%)Real memory available to Lightroom: 36,864.0 MBReal memory used by Lightroom: 6,523.8 MB (17.6%)Virtual memory used by Lightroom: 428,469.5 MBMemory cache size: 3,749.5MBInternal Camera Raw version: 18.0
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.