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
How comes that my “old”/previously edited photo is still present in my lightroom? When I have imported my new photos I can still see my previous photos. Thats very annoying. How do I deselect this option?
A login window pops up every time I open the program. Please fix this issue, as it is incredibly annoying.
THe subfolders appeared in the folder panel in LRC but separately and not in the parent folder. When I tried again to import the same, the images were greyed out, indicating they were already imported. The parent folder is on the disc but does not appear in the folder panel in LRC. I want the subfolders under the parent folder to keep things organized. I tried to create a new parent folder but it did not appear on the disc or in LRC. How can I collect the subfolders under a parent folder?
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
Import Keywords — Do Not Export flag not applying to existing keyword namesI'm importing a plain text keyword file via Metadata > Import Keywords (tab-indented, [bracketed names] for Include on Export = off, {curly brace} synonyms). It works fine for brand-new keyword names, but when the imported name matches a keyword that already exists elsewhere in the catalog, the bracket is ignored — after import, the existing keyword's Include on Export checkbox stays exactly as it was before, checked or not.Is this expected behavior (import merges into an existing same-name keyword and won't touch its Include on Export flag from the file), or am I missing correct syntax/an option to force it? Is there any way to set Include on Export via the import file for a keyword name that already exists in the catalog, or is manually toggling it in the Keyword List panel after import the only route?Lightroom Classic, imported via a plain .txt file (also tried .csv, same result). Thanks for any pointers.
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
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 use masks to blur parts of my images, and in 99% of cases I use them inverted. Older version memorized this and the new version does not memorise the fact I used inverted mask just seconds ago, so for every new mask I have to additionally click on invert checkbox, which together with the fact I have to use masks now and create new ones with additional clicks, slows down my workflow. Please include Invert option to be remembered by Lightroom mask from the previous usage of the mask.
I am unable to import photos into Lightroom Classic suddenly this morning. When I attempt to import new photos, either from an SD card or my hard drive, it displays them as if it is going to import them, but then nothing happens, and the import photos and videos button becomes grayed out. If I close and reopen Lightroom Classic, the button seems to be active, but than again nothing happens after I click it, and then it becomes grayed out again.
I discovered that when saving JPEG files in Adobe LR, banding began appearing on smooth color gradients, even at maximum quality. If I save the file as an 8-bit TIFF and then convert it to JPEG using FastStone, I can select RGB as the photometric type in the saving options, ensuring flawless gradients.Samples:https://drive.google.com/drive/folders/1fJsowuWjIv6RQDeImtK2_7we30tIqLNT?usp=sharingCan you implement RGB photometry support in JPEG to achieve better image quality?
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?
Adobe Lightroom Classic 15.5 import problem on Windows 11Hi Adobe team and Lightroom Classic users,I’m experiencing a serious import problem with Lightroom Classic 15.5 on my Windows PC, and this only started happening recently.System: OS: Windows 11 Pro 25H2 Lightroom Classic: 15.5 Catalog: Tested with both my current catalog and an older catalog Photos: Sony ARW RAW files Import: Using Add Storage: Tested from different physical drives Problem:Lightroom can see and read the photos normally in the Import dialog. For example, I can select 1,446 ARW files and Lightroom correctly displays all the thumbnails and recognizes the files.However, when I click Import, the import progress bar only runs for around 2 to 3 seconds and then disappears.After that, Lightroom returns to the Library and shows:All Photographs: 0None of the photos are added to the catalog.This is happening even when I try importing only a few photos.What I have already tried: Tested the original photo drive Mo
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
4 x 6 inch photo printing in lightroom classic not centered when i reduce the size to passport photo. it will print it all the way to the end towards the left side. But if i print the full size instead of reducing it, theres no problem at all.
Lightroom Classic silently skips files during batch export if it fails to write Credit/IPTC metadata. Additionally, it misreports local file errors as network issues.Steps to reproduce: Select a batch of images (e.g., 120 files). Export with a metadata preset that includes Credit/Copyright info. Observe that some files are randomly skipped. Actual Results: Only a portion of the files (e.g., 106 out of 120) are exported without a proper per-file error log. A "No network access" error pops up mid-export despite a perfectly stable internet connection. The export engine deletes the entire image file if the metadata write operation fails, instead of just skipping the metadata and saving the image. Expected Results: Lightroom should export the image even if metadata injection fails (best-effort export). Errors should be accurately reported (local I/O failure, not "No network access"). A detailed log should show exactly which files failed and why.
How do I get the parent folder “Pictures” to see its subfolders? I get the message “subfolders are missing in this folder, please relink” but “Synchronize Folder...” has not helped.Thanks for your help!Francisco de Lacerda
I have a question about the processing of Canon RAW files that were shot with Highlight Tone Priority (HTP) enabled. These images are underexposed by one stop at capture time by lowering the ISO. For example, if you shoot at 1/2000, f/8, ISO 400, the actual exposure is done at 1/2000, f/8, ISO 200 and the file is tagged as having HTP enabled. When you bring such a file into Canon’s DPP software, it recognizes the HTP flag, and automatically applies a special tone curve which will brighten the shadows and midtowns by one stop, but will attenuate the effect on the highlights. My understanding is that Lightroom Develop will recognize the HTP flag, but will simply brighten the entire image by one stop without making any special accommodations for the highlights. This is also the behavior I see when testing this out on my own. However, I continue to see folks claiming that Lightroom Develop will behave exactly like DPP on RAW files shot with HTP. Can someone give a definitive answe
LR Classic 15.5, Windows 11 ProTrying to connect to an SFTP server, either to browse for a folder in the “Configure FTP Transfer” dialog, or to upload a project, fails with the error:“Cannot browse the FTP server, because an unknown error occurred. (CURLE_SSH)”On the SFTP server side, the error is:Aug 25 20:57:39 pi1 sftp-server[811]: error: process_read: read "/home/jsmith": Is a directorywhere “jsmith” is the user connecting to the server. So the error is trying to read the user home directory. For a while cURL accepted the “/~” path for the user home directory, but since 2023 this syntax is no longer accepted, see:https://github.com/curl/curl/issues/17534It is necessary to terminate all directory references with an ending slash, i.e. “/~/” or (79) Error in the SSH layer (CURLE_SSH) is raised.I can replicate the same error easily from the command line:curl --k sftp://<sftp_server>/~ --user "<user>:<password>”triggers the same errorcurl --k sftp://<sftp_server>
In library, I hit R to open crop tool in Develop. But this opens crop overlay, with the Zoom tool, not the crop tool. Hitting R again (closes crop ), then R again, will open crop overlay with the crop tool.The in the Right-hand panel the Crop section is greyed out too.
EnvironmentMac mini M4 24 GB unified memory macOS Tahoe 26.5.2 Lightroom Classic 15.5 Apple Silicon / arm64 Lightroom Classic catalog with images using AI masks, Remove and Lens BlurProblemLightroom Classic produces random blue horizontal lines/artifacts on images after AI processing.The artifacts are variable and may appear only several seconds after selecting the image in Develop. They can also be present in exported JPEG files.The problem appears to be strongly related to Lens Blur.Reproducible behaviorI can reproduce the problem with the following sequence:Open an image containing AI masks and/or Remove edits. Apply Lens Blur. Lightroom starts AI processing in the background. After some time, random blue horizontal artifacts appear in the image. The artifacts can also appear in exported JPEG files.The behavior is not simply a display-only problem because the artifacts can be present in the exported JPEG.Important observationsWith Graphics Processor disabled:Lens Blur ON → blue arti
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.