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
Lightroom previews won’t stop “Loading.” And these are minimal-size previews, which I created when this problem started with 1:1 previews after I removed all the files from Lightroom and re-imported them. And, when I attempt to build 1:1 previews, even if I only select one, the progress bar doesn’t move at all or gets stuck. This issue just started up a day or two ago.
I think it occurs when an image is synced to the Cloud, but in Lr Classic the text of a caption or description field in the image metadata is being stripped of all the paragraph breaks so all the paragraphs disappear and the field becomes one unreadable block of text.
Yesterday in a small hotel in Oceanside I opened Lightroom, on my system “TL3” but the system said “you need to log out on one of your systems” incl. the very same TL3, and listed the laptop as a “new system” without a name. So I logged out my main workstation at home and started to edit my images. After a making a backup of my work, I started today LR classic again, but to my surprise it asked again for email and password, and than said with error 18000 “cannot confirm your subscription status and exited LR !!! Not even access to the library module! As I am typing it, I am logged in to Adobe of course, and I am using a hot-spot on my phone. Ookla speed-test shows a decent speed. I can watch Youtube for example. That is not right. How do I get access to my Lightroom? This entire model is seemingly flawed.
LRC - many workflows require saving and working in Tif format, why not open for using the excelent noisereduction function on those files?
Please add the option to use variables / metadata in “put in subfolder” name, similar to how we can rename files using e.g. {folder name} {custom name}. I use lightroom to edit students ID pictures, so i organize each classes into their own folders. I then batch export all edited photos to a subfolder named “Edited” under each classes' folder,current setup:Class A EditedClass B Edited...Class Z Edited After that I have to manually add the class name » “Class A - Edited” before I can send those folders to my printer… it would be helpful if we can use the parent folder’s name (in this case the class name) as a variable to name the target subfolder 🙏
Develop sliders jumped to the wrong position when clicked moved way over to the left, on macOS 26.2 with a Magic Trackpad on an iMac. Say it was fixed by rolling back
Description of Issue: I recently upgraded Lightroom classic to version 15.6. Before that it used to take around 10 seconds to run Denoise in one of my files (photos from Nikon Z8). Now it takes around 25 to 30 seconds. This time does not change if I set the “Use Graphics Processor” preferences to off or custom. It seems that the software is always using the CPU instead of GPU. In spite of this behaviour, the application is recognising my processor (Apple M1 Ultra) and it says that it supports full acceleration.Lightroom Classic Version 15.6OS version 26.7.1Camera model: Nikon Z8Hardware: Mac Studio M1 Ultra, 128 GB
I start with an edited version (lightroom adjustments only) of a photo in lightroom. I make a copy of it and then click reset on the new copy. This copy is essentially no modifications at this point. I then edit that copy in photoshop. When I am done editing in PS, I save it. I then open that PS-modified version in lightroom and paste ALL settings I have copied from the original to this new TIFF version. I expect the changes to work but it looks wrong. I notice the REMOVED tool item masks are strange. It looks like the REMOVE masks in the version that I pasted to are 90 degrees rotated - clockwise. Basically, copy/paste of masks does not work from a raw file to a tiff version. It’s like PS messed up the orientation indicator or something and LR got confused?
Since updating to latest version 15.3 I cannot use my presets or update AI edits.When I try I get a box appear saying I am downloading AI models. This gets to 99% then stops. Then when I try to use presets or update the AI edits I get a red box that says ‘some Ai models failed to download. Please try again later.This has been going on since yesterday. I have tried uninstalling LR and reverting to previous version but problem persists. Any ideas?
This post applies to Camera Raw and Lightroom Classic. Dust Removal is no longer in Early Access status and can be found in the Remove edit panel for Camera Raw & Lightroom Classic. Dust Removal helps remove distracting spots in an image that may be caused by dust on a camera's sensor and is also effective on dust on the rear lens element. Once enabled, your image will be scanned, and any detected dust spots will be automatically removed using Content-Aware Remove. For refinement, you can select one or multiple spots to delete or refresh. Batch removal is also supported; simply select the "Dust" checkbox under "Remove" in the copy settings dialog.Please note that scanned negatives are not in the scope of this feature at this time. Dust spots on scans tend to be located in the focal plane, with the negative and very sharp, while sensor dust is typically positioned out of the focal plane and therefore not in focus. Scanned negative dust typically appears as white spots on a darker b
It seems to happen when syncing images to the Cloud, but LrC is stripping the paragraph breaks/returns from the caption field in the metadata of images, creating one large block of text impossible to read. When you Read Metadata from File, the breaks are restored and the caption field looks normal again. Then a few moments later the breaks disappear, I think when the image syncs to the Cloud. The Caption field text was created in Photoshop not in LrC. But Classic reads the data, then ruins it. This behaviour started about 2 months ago.
Having a photograph with people in it—whether in any location, close-up, background, etc.—when I try to apply a mask to detect people, the program tells me that “no people were found”, and therefore it doesn't generate the mask. This started happening after the latest updates, though I'm not entirely sure since I don't use that feature very often.
Prior to around 10:00 am today, I could right click an image I was editing in Lightroom Classic and select "Edit In" and then "Edit in Adobe Photoshop 2026..." and it would open Photoshop 2026, if one wasn't already open, and then open a TIFF called "<image filename>-Edit.tif" with all my Lightroom edits. It was working this morning, but now suddenly when I right click the image in Lightroom Classic and select "Edit in"and then "Edit in Adobe Photoshop 2026..." it will open Photoshop 2026 but will not open the file...it just stops at the Photoshop Recent File list. I have tried all of these:1. Checking for updates. Non available. I’m all up to date.2. Trying through the top menu: Photo>Edit in> Edit in Adobe Photoshop 2026...” but that didn’t work.3. Restarting my computer. That didn’t work.3. Uninstalling both Photoshop and Lighroom, restarting my computer, and then reinstalling Photshop first and Lightroom second. I did it twice: once keeping all of the plugins on my
File raw di Nikon. Computer Apple M4 pro quando applico la riduzione disturbo da giorni mi esce la dicitura: la modifica è temporaneamente non disponibile e la riduzione del disturbo è minima e non corretta. Inoltre quando voglio trasferire la fotografia da Lightroom a Photoshop con PHOTO MODIFICA IN PHOTOSHOP la fotografia non passa in photoshop
When using the color grading panel the numerical fields for the Hue and Sat input behave erratically. When moving the Hue slider sometimes the last digit disappears. This happens with single Color Wheel interface. So instead if displaying 235 the field displays 23. It shows this behavior with various value: 231 shows 231, but 220 shows 22. You can check this when displaying all 3 color wheels simultaneously. The hue values in both image is 235.Lightroom classic is showing this behavior since the last update, 15.6 release. This seems like a bug. I have tried resetting everything to the default settings but that doesn't make any difference.When I edit the same photo in Photoshop Camera Raw, Color Grading behaves as expected.
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)
I just discovered something weird that in over 15 years of using Lightroom Classic (and it's several other names over the years) I have never seen before. I have 165k photos imported into my catalog. I have a photo with the name DSC01885.ARW and a virtual copy of it. When I sort the photos by capture time they are separated by several photos. Looking carefully at the times of the photos I see the several photos were taken at 12:52:09 to 12:52:47 on 2009/12/23. Here is the order they appear in grid view when sorted by capture time:DSC01885.ARW 12:52:47DSC01882.ARW 12:52:09DSC01883.ARW 12:52:31DSC01884.ARW 12:52:46DSC01885.ARW 12:52:47 (virtual copy)When I sort the photos by file name they are not next to each other either. They appear separated by several photos.Weird. Any ideas?Mac version. Backup function performed on every exit daily.
This post applies to Lightroom Classic and the Lightroom Ecosystem products. Camera Raw feedback can be found here. Generative Remove makes it easier to remove unwanted objects and distractions with a simple gesture, even on complex backgrounds. For more accurate results, be sure to include the object's shadow in your selection and/or expand its size. Detect Objects uses AI to find the objects underneath a brushed area. The masked areas will now appear larger than the Early Access version of this feature. You can also circle objects for quicker selection now. We have also updated the spot selection experience to make it easier to manage variations, switch the fill type, refine the selection area, or re-generate as needed. Batch updating is also now supported for Generative Remove spots. Try out the latest updates and share your feedback with us here. Please also include the following details in your post: App versi
I’m a real estate photographer and I use Lightroom Classic to merge the bracketed images. Could be 3 or 5 bracketed images for a total of 30/50 final images .When I launch the action in Lightroom it’s working well until I stay in the same panel or in the same folder, but if i move the process stay stack to the last image in process. Before I was used to move in other folder and do something else.Lightroom doesn’t freeze totally but only the HDR process and I’m unable to quite the process and launch un’other one.The only way is close lightroom , reopen it and launch again the process and this is annoing.To have the process done I have to stay in the same panel and do not change folder and wait until the end.I have LR 15.6 but this issue started at list from 3 or 4 realise ago.
We urge you to consider a transformative feature for Lightroom: an AI-powered batch editing tool, finely tuned to each photographer's unique style. Imagine a feature that learns from an individual's editing history, creating a personalized AI profile. This tool would not only expedite batch processing but also evolve with the user's artistic growth. An essential addition would be intelligent AI-assisted culling. This feature would automatically discern and prioritize images, streamlining the initial selection phase and focusing on quality and composition. Moreover, the introduction of adaptive 'SmartPresets' is crucial. These presets, unlike any currently available, would dynamically adjust to each image, informed by the user's historical editing patterns, ensuring consistency and quality across varied lighting and contextual scenarios. The integration of such advanced AI features would dramatically revolutionize the editing workflow, cutting down editing time and freeing photographers
Lightroom Classic 15.5.1 — Technical Performance ReportSubject: Progressive Develop performance degradation, unusually large .lrcat-data, and possible memory/resource-management problemsApplication: Adobe Lightroom Classic 15.5.1Operating System: Windows 11CPU: AMD Ryzen 7 8700GGPU: NVIDIA GeForce RTX 4060 Ti 8 GBCatalog: Approximately 20,000 photographsCamera: Sony α1 II, 50.1 MP RAW filesTypical RAW file size: Approximately 60 MBExecutive SummaryI am reporting a progressive performance problem in Lightroom Classic 15.5.1 that I believe warrants investigation as a potential application resource-management problem rather than simply a hardware-performance limitation.The principal symptoms are: Develop responsiveness progressively deteriorates during extended Lightroom sessions. CPU utilization can rise substantially simply from navigating from one photograph to another, even when no processing operation has been initiated. GPU utilization is often very low during the periods when D
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.