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
Please add an option in Lightroom Classic's Crop tool to display the physical dimensions of the current crop in inches or centimeters, calculated at a user-selectable print resolution such as 300, 240, or 200 PPI.Ideally, while cropping, Lightroom could display information such as:7200 × 4800 px | 34.6 MP | 30 × 20 inches @ 240 PPIAs the photographer moves the crop boundaries, these values should update live.An optional inch/cm ruler around the crop area would also be extremely useful.This would allow photographers preparing images for fine-art and large-format printing to immediately understand the effect of a crop on the final printable dimensions without leaving the Crop tool or manually calculating pixels, megapixels, and print size.Lightroom already has the pixel information necessary to perform these calculations. Providing this information directly in the Crop tool would make cropping for print considerably faster and more intuitive.
Lightroom Classic already displays the pixel dimensions of an image, for example 8256 × 5504. Please also automatically display the corresponding total megapixel count beside those dimensions.For example:8256 × 5504 — 45.4 MPMore importantly, the megapixel count should update automatically after an image is cropped so the photographer can immediately see how much resolution remains.This would be particularly useful for photographers evaluating cropped images for large-format printing. Currently, we have to calculate the remaining megapixels ourselves even though Lightroom already has all the information required to make this calculation.It is a small addition that would make evaluating image resolution and print potential much faster and easier.
After latest update "There was an error working with the video" message appears for all of my GoPro videos leaded earlier this year. Videos from other cameras still process just fine.
In wake of a power outage, when I reopened LrC, ALL of my images had been moved to a new location. Some of which remained intact as thumbnails and others completely missing. Is there any way to revive the current catalog? If so, how? Matthew
HiI am running LrC version 15.5 on a Mac - 3.8 GHz 8-Core Intel Core i7, AMD Radeon Pro 5500 XT 8 GB, MacOS Tahoe 26.6Until recently I had no issues using the masking tool, however it no longer finds people .. it comes back with "No people found"Other masks such as background and subject selection work as they should. Any help or guidance would be most appreciated.Thanks
Summary:The Map module fails to render any map content. On launch, the world map appears very briefly, then the entire module goes grey and stays grey indefinitely. No persistent error is shown, though a fugitive message reading "Unable to connect to Adobe servers. The Map module is not working." occasionally flashes on screen for a fraction of a second before disappearing. This matches other open reports of the same bug (e.g. the "(Europe) Map Module not showing a Map" thread, open since LR 14.2 in early 2025 and still unresolved as of 15.5).Environment:Lightroom Classic version: 15.5 [202607291506-b8869fa7] OS: Windows 11 Home, version 11.0.26200 GPU: NVIDIA GeForce RTX 4070 Ti SUPER (driver 32.0.16.1088) GPU acceleration: Off (User Preference: Off, GPUDeviceEnabled: false) Displays: two monitors, both 3840×2160, system running at 200% (192 DPI) scaling Language: EnglishSteps to reproduce:Open Lightroom Classic with a catalog containing photos that have GPS coordinates embedded in th
I ran the latest update on Lightroom classic and Lightroom and now the people detection on the masking function is not working. It says people not found. Is this a known issue? Is it being worked on? Anyone else running into this.
the lightroom Classic after installing newly updated version 15.5 keeps shutting down in the middle of assisted culling. the issue persists even after system restart and app restart. Windows 11 Pro, processor 11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz 2.30 GHz
So I have been trying to fix this problem for so long and I cannot seem to figure it out. Whenever I go to select an object, keep in mind the object is very clear, it literally does nothing. It maybe buffers for a second or two but then nothing selects and the mask just goes away. Every single other ai feature in lightroom classic works for me, including subject and denoise. This is the only one that doesn't seem to work. I also just recently upgraded my GPU so it is completely updated and meets the requirements for adobe lightroom classic. I am also on the most recent version of lightroom, 15.1.1. If anyone has a solution to this please reply because this has been driving me nuts. Thank you!
When I try to import picture files, I get a popup for assisted culling that locks the application. I need to go to task manager to shut down the application. I turned off assisted culling under catalog settings, but this does not correct the issue. Is anybody else experiencing this issue. I cannot import new files!
Have been having a lot of crashes with LRc 15.4.1 for a week or so. Currently the situation is so bad, that moving from library to dev the app crashes every time. I’ve been sending a lot of crash reports. I’ve also tested multiple files from different cameras over past 20 years, the issue stays.I’ve also tested downgrading LRc, issue doesn’t go away. I also tested the other Lightroom, Photoshop, Bridge and Bridge (beta) - all crashing equally the same, when changing to dev/edit or in case of bridge an ps, just opening any raw file. This suggests that the problem is somewhere in Adobe shared runtime stack that is used by all of the apps. I also repaired Creative Cloud installation, no help. Files can be opened just fine in any other capable app. I created new catalogs to see if it was catalog corruption, but it is not. I have gone through all the usual Windows error checkings, sfc, dism, chkdsk, even the memory check. no problems there. All my other apps and even games work fine. Window
Opened Lightroom Classic 15.5. Upgraded Library version as requested. I imported some photos into Lightroom Classic. After a while, looking through the collection, it automatically closed down. I had this happen several times. I ran log collection and uploaded the logs.The log reference is Adobelogs_20260811_075703_590-win-GS.zxp.I could not find a way to log in directly to support on this issue.My system setup CPU: AMD Ryzen 5 5600X 6-Core Processor (3.70 GHz)RAM: 64 GB DDR4GPU: NVIDIA GeForce RTX 3050 (6 GB)System type: 64-bit, x64-based processorOS: Windows 11 Home Version 25H2 Build 26200.8875 I would like to know how to solve this issue.
LRC: 13.5.1Windows 11Lightroom has been really slow for me, and I was sure that facial recognition was turned off, but today I was scanning some photos that had group pictures, and LRC is still recognizing faces when I’ve explicitly turned it off. Note that it was turned off before this screen capture and has been turned off as long as I can remember, but LRC is clearly still doing it. How can I stop this? I don’t want LRC to recognize faces. I don’t want it, don’t need it, and it’s taking computer resources and slowing down my work. Thanks NB: I am not upgrading to the newest version because it is incompatible with my Fuji GFX100 due to LRC’s native tethering causing issues. Thanks
I can't get Lightroom Classic to launch. When I try to I get spinning wheel while the computer thinks about it for a second then nothing happens, but Lightroom Classic shows up as a Background Process in Task Manager. This only happens with Lightroom Classic, I also have Photoshop and Lightroom (not classic) and both of those work with no issue. I have tried un-installing + reinstalling including using Adobe Creative Cloud Cleaner but always with the same result (everything except Lightroom Classic works). Is anyone able to help or experienced something similar? Details below. Creative Cloud 5.3.1.470Lightroom Classic 10.0Windows 10 Pro Version 20H2
When importing images from an external drive or an SD card when I click on Import nothing happens except that the menu items “import photos and video” are greyed out. Lightroom worked perfectly earlier this week. Mac Mini M1.
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
Depuis la mise à jour 14.5, mes correcion par IA générative génèrent toute une erreur : Le service ne répond pas, veuillez vérifier vore connecion internet. Bien évidemment ma connection fonctionne correctement...
After updating to 15.5, I noticed during the last editing cession of a dozen of landscape pictures with various masks that the histogram disappeared from its window. The RGB values were still changing when the cursor moved over the picture, proving the window was still active. The histogram returned only after entering and exiting the masking tool. But scanning through the photos make it disapeared again later in the develop module for some pictures.I had to relaunch LRC to have the histogram window working again as it is supposed to be.Unfortunately this bug seems to happen randomly and cannot be repeated on purpose.My config is Apple MacBook Pro M1 Max 24Mo Ram OSX latest version of Tahoe, LRC 15.5.I must say this is the third strange behaviours since the update to 15.5. The first was the uncontrollable scrolling with the arrow key in the film strip, the second being the loss of the zoom ratio in Full view returning automatically to 33.3%. Restarting LRC solved apparently both issues
LR 15.5 made numerous inconsistent and incorrect changes to how the Delete and Backspace keys are translated in Help > Library Module Shortcuts and Map Module Shortcuts. Prior to 15.5, LR followed the principle of using the names of the keys as they appeared on the most commonly used keyboards for that language. For example, on Spanish (ES) keyboards, the Delete key is labeled Supr, and LR's Help used Supr for the Mac shortcuts for Library > Remove From Library, Map > Delete GPS Coordinates, and Map > Delete All Location Metadata. This convention makes sense -- Help uses the names of the keys that are displayed on the user's keyboard. But in 15.5, the displayed names of the Delete key (Mac) were changed in all 15 non-English languages, for some but not all of the commands assigned Delete. Similarly, the displayed names of the Backspace key (Win) were changed in 6 languages, for some but not all of the commands assigned Backspace. For example, in Spanish, the name for the
segue exemplo do defeito - fotos em formato CR2, camara Canon
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.