Connect with fellow editors in our Lr Classic community.
Recently active
The August 2026 release of Lightroom Classic (v15.5) brings a mix of creative enhancements, workflow improvements, and reliability fixes designed to help you edit with greater precision and confidence. From more refined masking controls to a new way to create rendered DNG files, this update focuses on giving photographers more flexibility while also addressing a wide range of issues reported by the community. What’s NewLightroom Classic v15.5 introduces enhanced masking capabilities with new Feather and Edge controls, giving you finer control over photo masks and more creative editing possibilities. Cropping workflows are also improved with the ability to temporarily adjust photo opacity, making it easier to see cropped-out areas and accurately frame your images.For photographers who want a fresh starting point after extensive edits, the new Render to DNG option allows you to save a rendered DNG file with all current edits permanently applied. This creates a non-raw version of your ima
The June 2026 update to Lightroom Classic (v15.4) adds a new Faces panel for people-focused culling, automatic duplicate detection, keyword sync across the Lightroom ecosystem, and more precise subject selection when masking. These updates help photographers handle large shoots and organize catalogs with less manual effort. What’s NewLightroom Classic v15.4 is built to help you move through large shoots with more speed and confidence. The new Faces panel in Assisted Culling brings a people-first approach to selection, surfacing Eye Focus and Eyes Open scores so you can instantly identify your best frames. New auto duplicate detection scans your catalog for exact matches and neatly groups them into stacks, making cleanup far less manual. Masking also gets a boost with more precise subject detection, helping you separate subjects from complex backgrounds with cleaner, faster results.On the organization side, AI-powered metadata filters and Smart Collections make it easier to sort, find,
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
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 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
Sometimes, maybe. 1 in 10 when I edit in another program, LR does not properly make a copy with Lightroom edits. It will sometimes even make the copy of a version prior to some final edits I made. It’s almost always. a much brighter version of what it should have done. You can look at the copy and original and they are not the same.
Ich habe bei meinem Katalog nur die Backupfunktion eingeschaltet und gleich ein Backup mit Katalogoptimierung gemacht. Und nun sind alle Vorschaubilder weg. Das habe ich ja noch nie erlebt. Wie kann das denn sein? Das Problem ist wirklich erst nach dem Backup enstanden.
I was asked if I could help a Mac user of LrC resolve a problem, but being a Windows user, I have been unable to help.Whenever they run LrC inDevelop, this cache location rapidly consumes their hard drive storage:/Users/[username]/Library/Caches/com.adobe.LightroomClassicCC7/com.apple.e5rt.e5bundlecacheIn the user’s own words: ‘Issue: A cache folder grows continuously while Lightroom Classic is open in the Develop module, eventually consuming almost the entire SSD. The problem has been so bad for months, this user is about to ditch LrC forever.
After importing images into Lightroom Classic and performing edits, then selecting Edit in Photoshop and it opens, the images do not retain the LR edits on them and are back to the RAW appearance (No edits applied). I have Uninstalled/Installed both LR & PS with saving preferences and also fully uninstalled/installed without retaining preferences. I have tried Using GPU acceleration and auto. Nothing seems to work. I have gone into so many posts relating to this issue. Windows 11 is up to date. GPU drivers are up to date. LR & PS are up to date. I have a travel laptop that works like it should with this workflow and I set every single preference and catalog setting in LR & PS the exact same and still the same result. I have also created a new (testing) catalog to see if it's a catalog issue but no fix either. The only thing that seems to go with the image is any object removal I have done. No color grading, masking ect.
Yes, this exact question has been raised many times in the past and those posts have all been closed as “answered” without any resolution. This is still an issue.I open LrC, import and make edits. LrC sits idle with computer running for at least an hour. Try to close LrC and it spends several minutes "Writing Metadata Changes into XMP" before the app exits. What is LrC doing while idle after the last edit was made that it now needs to do when I’m trying to shut down the computer? This is unacceptably poor performance but vaguely understandable as edits were in fact made. Why are the XMP writes not happening during idle time rather than forced immediately at exit?The same delay occurs without making edits. Open LrC, make no edits and immediately try to open another catalog. LrC shows the "Writing Metadata Changes into XMP" message for several minutes before finally restarting with the other catalog. This is after LrC spent several minutes "Writing Metadata Changes into XMP" p
This thread is for Camera Raw & Lightroom Classic feedback on the (Early Access) Content Authenticity Initiative (CAI)For the Lightroom Ecosystem feedback, click here. The Lightroom team is dedicated to building capabilities that foster trust and transparency in the age of AI. Our latest release, as part of the Content Authenticity Initiative (https://contentauthenticity.org/), allows you to add content credentials to your work when exporting in Lightroom to ensure provenance and preserve authenticity. New content credential capabilities are available across the Lightroom ecosystem (Lightroom, Lightroom Classic, Lightroom for mobile (iOS & Android), Lightroom for web), and Adobe Camera Raw in Early Access. When exporting a JPEG from Lightroom, you can attach your name, social media handle, and a list of edits via a digital signature. You can find the option to apply Content Credentials while exporting a JPEG in the export panel. It is, by default, turned OFF
Lightroom Classic 12.3 (and all previous versions of LrC while running Windows 11, as far as I can remember) Windows 11 (can't remember if it did this in Windows 10) Let's suppose I have only two applications open, Microsoft Word and my web browser. In windows, when I press Alt-Tab, I switch from one application to the other. If have three applications open, such as Word, Web Browser and E-mail program, Alt-Tab lets me move to the 2nd app and Alt-Tab twice lets me move to the 3rd app. All as expected. But if one of those applications open is Lightroom Classic, then Alt-Tab once keeps me in Lightroom Classic. Not expected. I have to Alt-Tab twice to move to the next application that is open. Not expected, and annoying. Is anyone else experiencing this? Is there a way to fix this so Alt-Tab when I am in Lightroom Classic works as with any other application? Is this a bug?
Since updating to the latest Lightroom Classic 15.5 version on a MacBook Pro M1 Max, I have noticed several erratic display and navigation behaviors in the Develop module.First, when viewing photos in Full Screen mode (F key), the zoom setting of the Develop module no longer seems to be retained. For example, if the Develop module is set to 200%, clicking on the image while in Full Screen view unexpectedly changes the view to 33%, instead of retaining the previously selected zoom level.A second, and more significant, issue concerns navigation through the filmstrip using the arrow keys.A short press on an arrow key can now cause several photos to be skipped. Holding the key down launches extremely fast scrolling through the filmstrip, sometimes advancing through several dozen photos. With a longer key press, the scrolling can even continue indefinitely and can only be stopped by clicking directly on the filmstrip.During this scrolling, the main Develop view becomes completely frozen and
In the recently released 15.5 LrC when modifying the capture time the list in the Library filter is not updated. Before edit capture time 001 is updated, not shown as selected on todayLeaving folder and re-entering brings in new date of 001.Modifying 002 does not show its new date. This started with LrC 15.5, in 15.4 the date list was updated immediately.Checked with Flag and Rating these new values are shown immediately when set.This is on Windows ARM.
I am on Windows 11 Pro and I have the latest Creative Cloud with PS and LR Classic, Nvidia 2060S with the latest drivers. This error started appearing a couple of months ago. I start Lightroom, never mind if I open the catalogue or click the icon, and it takes 20 minutes to pop up. Task Manager shows it’s running, but it takes 20 minutes to show up.
Modern mobile devices run on ARM processors, and that is the future. Look at Apple. Please develop native ARM versions of Lightroom Classic and all other Adobe products. Even with the current version of LrC, it is impossible to take advantage of ARM-based AI for noise reduction! Noise reduction takes hours, despite using a fast Snapdragon processor. That is simply unacceptable.After all, you rewrote the software for Apple in record time—why not for Windows? Otherwise, I will be forced to switch to Luminar Neo, and I could replace Photoshop with Affinity; both run natively on ARM. Adobe is still relying on the outdated x86 architecture. I urge you to change this. ARM is many times faster than x86.Many thanks in advance!
Hi Adobe Team, I’m posting this as a clear performance regression report for Lightroom Classic v15.x — specifically the Develop module image-to-image switching latency on Mac. REALLY SLOW. Please do not merge this thread into a generic “performance” megathread and then mark it as “Solved” as if nothing happened. Multiple users are reporting the same behaviour, and it deserves a proper investigation and acknowledgement (instead of being dismissed as an “NVIDIA driver” issue — this is Apple Silicon). What’s happening On Lightroom Classic v15.2, switching between photos in Develop is several times slower than in previous versions. This is not a minor “feels slower” issue — it’s a real, repeatable regression that drastically impacts professional workflows. My setup MacBook Pro (M3 Max) macOS v26.2 Lightroom Classic v15.2 Preferences → Performance → Graphics Processor: ALL acceleration options manually enabled (not Auto) Proof / Reproduction To remove any subjectivity, I recorded sc
Lightroom Classic 11.2 on MacOS Catalina 10.15.7. In the batch file renaming feature accessed through the hamburger icon to the right of the File Name field in the Library module, I often need to search and replace particular text. I don't see a way to, for example, replace "Jan1969-" with "1969-01-", which I wanted to do this week because I had improved my file naming system and wanted to update my old files' names. Even better would be to support entering an arbitrarily long list of replacements to make in one pass, with a "+" or "Add" button to add more "From" and "To", or "Old" and "New", boxes. For example, Old: Jan1969 New: 1969-01 Old: Feb1969 New: 1969-02 Old: Mar1969 New: 1969-03 A further enhancement to that feature would be to give either the whole list or each entry a pulldown like in the Library module Text Filter, specifying Contains, Starts With, or Ends With. I could actually benefit from a full-blown regular expression matcher,
There is a scaling bug in the Profile Browser in the Develop Module. The star icons used to favorite profiles are ONLY visible when the Font Size (in Preferences) is set to 150%. If the Font Size is set to 'Medium' or 'Small', the right-hand panel cannot be dragged out or expanded far enough to reveal the star icons, causing them to be cut off. Windows 11, 25H2, Build: 26200.8875
A "Photo Merge - HDR" menüt használva, 3 képet kijelölve, az összeszerkesztés nem fejeződik be. Ez a hiba a korábbi verziókban is előfordult, de nagyon ritkán. Most a legfrissebb verzióban, nagyon gyakori. Csak a programból való kilépés és újraindítás után tudom folytatni, és látom, hogy elkészült az összeszerkesztett kép, de továbbra is látva marad a 3.db. kép amiből összeszerkesztődött.
non riesco a creare nuove raccolte o a rinominare una raccolta esistente
I want to switch light and color smoothly. Now the open and close in auto. I want to left the damn colorsection open on right side. also left side colapses by itself, even tho I have things to do there!. This is not a good update, you messed it up. Why would you change UI after a long time of use. not good.
I’ve noticed the crop tool is sticky again. Lightroom Classic version: 15.5 [ 202607291506-b8869fa7 ]License: Creative CloudLanguage setting: enOperating system: Windows 11 - Home Premium EditionVersion: 11.0.26200Application architecture: x64System architecture: x64Logical processor count: 24Processor speed: 3.4GHzSqLite Version: 3.36.0Adobe GSDK Version: 1.4.0.213CPU Utilisation: 1.0%Power Source: Plugged InBuilt-in memory: 65292.0 MBDedicated GPU memory used by Lightroom: 11351.4MB / 15995.0MB (70%)Real memory available to Lightroom: 65292.0 MBReal memory used by Lightroom: 12382.0 MB (18.9%)Virtual memory used by Lightroom: 24292.0 MBGDI objects count: 1276USER objects count: 4660Process handles count: 19316Memory cache size: 0.0MBInternal Camera Raw version: 18.5 [ 2673 ]Maximum thread count used by Camera Raw: 5Camera Raw SIMD optimization: SSE2,AVX,AVX2Camera Raw virtual memory: 1660MB / 32646MB (5%)Camera Raw real memory: 1926MB / 65292MB (2%)Cache1: NT- RAM:0.0MB, VRAM:0.0MB,
Remix with Firefly Community Gallery
Thousands of free creations to fall in love with and remix in Firefly.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.