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
Hi, when I open photos from Lightroom into Photoshop or just export as JPEG to my desktop, the images are very diffrent. Can anyone help me fix this please. The images show what I’m struggling with. Please help if you can, I’m matching sRGB in Lightroom & PS and it doesnt make a diffrence. This is exported from LR to desktop and produces the same result…. :-/
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
Could Adobe Lightroom Classic incorporate a feature that automates window masking in real estate photo editing, facilitating 'window pulls' without the need for manual brushing? Love the products! greets!
JPEG XL 非可逆圧縮時に 16ビット指定をしても実際に出力は8bitになっていました。
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
It's all in the title. But here's a screenshot of the problem.Because of this problem, local AI functionality is much slower.I have already tried the troubleshooting steps on the troubleshooting page, but without success.This is intolerable considering that I pay for the subscription to this software.I've attached my dxdiag file.I'm also experiencing the same issue with Camera Raw versions 18.4.1 through 18.6. Only Camera Raw 18.4 still works correctly. And my NVIDIA driver is fully up to date with version 616.56, released yesterday.
Dear I would like to use a smart collection that depends on the keyword and I am having many problems:if the keyword has many words for instance “blue birds” and there is also a keyword “birds” if I look for photos with just “birds” it also shows photos of “blue birds” if I work with keyword trees, for instance I do have “birds” and inside two other keywords “small” and “big”. Some photos do only have “birds” and other do only have “small” or “big”. If I ask the filter to show “birds” it also shows those photos with “small” or “big” keyword and that do not have the “birds”. another problem with the keyword trees: supose that I add another keyword “dogs” and inside it I have “small” and “big” keywords. I did not find the the solution to make the smart collection show photos with the specific “big” keyword inside “dogs”. I have tried “dogs > big”, “dogs / big” but didn’t work I have been trying to use a synonim for each keyword with a code without spaces and asking to include the co
Lightroom Classic now adds AI content credentials to image exports automatically (just started last week, without warning). For tools such as Remove, for dust spots, etc. This appears not possible to be turned off ?The export options show that Content Credentials are off, but it is still appliedMy use of such tools is for image refinement, not creation of distortions (which is where the content credentials are more appropriate)For minor refinements I do not want my images to be tagged in this way, misconstruing and giving he wrong message about the final image Please let me know how I can stop the CC being tagged, as it appears in Bridge (and beyond)
I have a three monitor setup. I want lightroom / photoshop on monitor 2, the photo full size on the secondary display on monitor 1. Monitor 3 is used as general purpose, often showing ChatGPT as I edit. I cannot get the full size photo on monitor 1 to stay there if I start typing on monitor 3. It goes blank. Thanks to anyone who can help. Having gone to the time and expense of a three monitor setup I can’t use it.
This has been happening for probably a week or two. I have it by default apply content credentials to every jpg I export - can’t hurt, right?In every single export lately, a random number of them ‘fail to apply’ and hence do not export at all. I have to keep going to the export dialog, click ‘skip’, and it will export a few more and fail to export a random number. Currently I have done this 8 times to a set of 148, and am down to one single file that it just doesn’t seem to want to apply them to ever. I assume this is a bug and I should give up on credentials until this is fixed. Mac Mini M4 Pro, OS 26.5.2
I use Lightroom Classic 15.5 on MacBook Air chip M1 with macOS Tahoe 26.5.2.I usually import photos directly from a card reader, in Copy mode, but it failed in the last tries : when I select the source folder, Import seems running (icon moving in circle on the bottom left), but no image is showing on the panel in the middle.I tried copying a few images in a new folder in “Documents”, and then import it from there, to make sure it is not a permission issue, but I had the same behavior.I also tried in Add mode, unsuccessful.Lightroom Classic is having “Full disk access” in Mac settings, so I don’t know what to try next.Can someone help me ?Thanks in advance for all your suggestions.
I have a three monitor ‘Windows’ setup. I want lightroom / photoshop on monitor 2, the photo full size on the secondary display on monitor 1. Monitor 3 is used as general purpose, often showing ChatGPT as I edit. I cannot get the full size photo on monitor 1 to stay there if I start typing on monitor 3. It goes blank.A good answer about the issue was received from Conrad C in the forum, as below.This isn’t a technically verified or official answer, but just from experience, I am not sure this is solvable unless Adobe makes some changes to the code. To me, the Secondary Display window appears to be a floating “palette” or “panel” in the same way as panels in other applications. The problem with that is, in most other software that I’ve used, panel-type windows appear only when that application is the active/foreground application. Switching to another application hides all of the first application’s panels, even though the main application window stays visible.In Lightroom Classic the
Unter Windows 11 kann ich mit Lightroom Classic 15.5 ein reproduzierbares GPU-/WDDM-bezogenes Problem beobachten, das nach längerer GPU-Nutzung in Lightroom dazu führt, dass DxO PureRAW 6 extrem langsam wird.System: Windows 11 Build 26100, Lightroom Classic 15.5, Camera Raw 18.5, NVIDIA RTX 2070 SUPER 8 GB, Studio Driver 610.88, HAGS deaktiviert. Der Fehler ist auch mit GPU-Werkseinstellungen reproduzierbar.In einer frischen Lightroom-Sitzung läuft PureRAW normal: ungefähr 100–110 Sekunden für 15 RAF-Dateien, GPU-Leistungsaufnahme etwa 190–200 W, PureRAW hält dabei stabil einen GPU-Arbeitssatz von ungefähr 742 MiB.Später in derselben Lightroom-Sitzung kann PureRAW bei denselben Bildern und Einstellungen extrem langsam werden: 25–30 Minuten für dieselbe Verarbeitung, teilweise mit Restzeitanzeigen von mehreren Stunden. Die GPU-Auslastung bleibt dabei nahe 100 %, die Leistungsaufnahme fällt jedoch auf ungefähr 115–120 W. PureRAW hält dann seinen normalen GPU-Arbeitssatz von etwa 742 MiB
What an awful release. Don't get me wrong, I'm glad to see new developments, but this Lightroom update is an absolute disaster. After culling just 5-10 images, the AI Assist culling tool completely hogs all my RAM, causing my Mac to freeze and throw memory errors. It’s a total nightmare.Culling images via the library module is practically impossible right now - everything just locks up. Even with previews pre-generated and trying to run AI Assist culling, the performance is still abysmal. On top of that, it frequently fails to even generate a Denoise. What is going on, Adobe?! This is absolutely unacceptable!P.S. The RAM management is completely broken and goes beyond any acceptable limits!
I have a folder in which I imported about 200 images from a shoot. Edited them last night as normal. Got a request for two additional images.I import the 2 new images from the SD card as usual. Accidentally see I selected all 1496 images. Click CANCEL import and cancel render previews. Lightroom shows "Previous Import"-view as normal, about 20 images. The original folder with the 200 edited images NOW HAS NO RAWs left. Only .xmps.Only the about 20 images from the canceled import are there. The original files are not in Trash. Not in the folder where I worked on them last ight. Just... gone.SURELY this is not intended behavior? Files on SD card are thankfully still there, lucky me.Windows 11 Home 25H2, OS Build 26200.8037LR Classic 15.2, Build [202602111402-ec4112e8]
I have been having trouble exporting files from Lightroom Classic (15.5.1) into Photoshop (27.10.0). If the raw file has been denoised in LRC it won’t open when I export to Photoshop. I am on MacOS and the files were taken on a Nikon Z8.
Seleziono filtro radiale. Compare l’ovale di modifica. Ma non c’è un elenco di effetti su cui agire, per es. regola esposizione, per modificare la zona dell’ovale., che quindi non serve a nulla
Hello,Lightroom Classic 15.2.1 (on macOS 26.4 in my case) does not correctly reproduce Nikon Zf in-camera presets (my test is on custom presets).In the Library module, the image matches the in-camera look because Lightroom is showing the embedded RAW preview. But in the Develop module, Lightroom switches to its own rendering and applies Camera Flexible Color, which produces colors that are clearly off compared with the Nikon rendering.So although Lightroom appears to support this feature in principle, the current implementation is not accurate enough to be useful. The user is then left trying to reverse-engineer and manually correct the many settings changed by Camera Flexible Color.As it stands, this feature is effectively broken/useless for Nikon Zf files.Here is a side by side view of what is expected and shown correctly in the Library module (left), and what Lightroom’s Develop renders (right). Thanks in advance for considering this bug report.
When backing up it states that it only backs up the catalog and not the photographs. How do you back up the RAW photographs from LRC to a hard-drive, especially if they’re already in Collections.
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
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.