Connect with fellow editors in our Lr Classic community.
Recently active
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
I import CR3 files in daily directories into my catalog. I process the CR3 files then export them converting them to JPG I then import the JPG files to put back into the daily directory they came from and to keyword them. The counters on all the directories are set to zero after this import. I have to exit and restart Lightroom to get the counters reset to their actual number of files in each folder. If I delete the CR3's as no longer necessary the counter goes negative by the number of photos removed.
Long time LR classic (windows 11 w/ networked 25T NAS) and med term LR cc user (on an iPad when shooting and on road) who has successfully been able to import, visualize, and edit pictures on both platforms using the synched feature and Adobe Cloud Storage. The work flow is 1)import pictures from my Canon camera directly into a new folder in LR classic and onto the 25T NAS with the same folder name for permanent storage with a copy to a 4T external HD (with additional redundancy by weekly automatic upload into the Amazon Glacier S3 Cloud Storage). 2) create a collection (same name) from the new folder and sync to Adobe Cloud Storage (1T). 3) I edit on any device (windows computer, IPad,iphone, web) and all are synched. Problem is when I go the other way when I'm on the road shooting and want to edit before i arrive home. Workflow is:1)import pictures from my Canon camera directly into a new album in LR cc and sync to Adobe Cloud Storage (1T). Edit away2)when i return home, I log onto
Hi everyone, since I did the update of Lightroom when I try to edit a photo in Photoshop All the edits disappear and the photo look completely washed out, not sure what to do. I need some help with this one, thanks in advance
Lightroom Classic will not open. It looks like V15 has been installed automaticly. For a month now my laptop does not open the app at all. I did’t receive any messages from the program to address. Please help!!!
Hey guys! I am a real estate media company owner, and I have some questions. For stacking photos, is there a plugin or anything I can do to make the stacking feature better? I need to only stack 5 photos (As I do 5 bracketed photos) and turn them to HDR. The issue with capture time and auto stack both is it always creates groups of 4 or up to 10, and then blurs or doesn’t give me full HDR range. As you can see in my screenshot it also leaves the brightest exposure(which I need) out sometimes
OK. Now I see what happened, so I’ll start over. I’m hoping that someone has an idea for a fix for this.Re: LRC 15.4.1Running painfully slow. A little history: I’ve been a Lightroom user for over 10 years, along the way Lightroom would bog down once in a while, but it always seemed to function good enough, until it became unacceptable. I was due for a new system so in 2012 I purchased a new XPS8500. Things went well, but the day came where Lightroom slowed to a crawl again. Fast forward to 2018 when I purchase my present system. Specs:Dell XPS8950Win 11 Pro32GB DDR4 2266 Mhz1TB SSD2TB 7200 rpm HDD NVIDEA GeForce GTX 1080 w 8GB GDDR5X Graphics MemoryBDRE DriveWith this system all problems all Lightroom problems vanished and I could multitask with several photo applications along with Lightroom with no problems. Editing became a pleasure once again.Lately everything regarding Lightroom is once again becoming intolerable.I’ve watched several videos on how to speed up LRC, but all to no a
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
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
Lightroom Classic renders local Radial Gradient masks differently in Develop vs Library/Export Hi,I have a reproducible issue in Lightroom Classic that started after moving to a new computer.My workflow relies on presets containing local Radial Gradient masks.On certain photos (not all), the image looks correct in the Develop module, where the Radial Gradient is applied properly.However, when I switch to the Library module, the image immediately becomes darker, as if the Radial Gradient mask is no longer being applied.The exported JPEG matches the Library module, not the Develop module.I have already tried:* Updating Lightroom Classic to version 15.4.1* Rebuilding previews* Disabling GPU acceleration* Creating new previews* Testing on multiple imagesAdditional findings:* The issue only happens on certain photos.* It is related to local Radial Gradient masks.* Creating a completely new Radial Gradient on a different image works correctly.* Saving the problematic edit as a preset reprodu
I've always had issues going back and forth with clients on proofing — Lightroom's own Web Gallery never quite cut it for this, so I'd end up just sending a folder of images, they reply "I love these three, hate that one, and can we lighten this one up a bit," then I'm cross-referencing that back into Lightroom by hand.Built a plugin that fixes it for myself: it generates a self-contained HTML gallery straight from Lightroom, the client stars favorites and leaves notes right in it, sends back a small file, and it re-imports the ratings/notes straight into LR.Cleaned it up enough that I put it up for sale (ProofingGallery, $29.95 one-time, not a subscription — enginecollective.studio/proofinggallery) but honestly just want to know if it's useful outside my own workflow. I've got 2-3 free licenses if anyone's interested in trying it out and sharing their thoughts.
Windows 11, latest Nvidia studio driver, latest Lightroom Classic version. AMD 5800X, Nvidia 4070TI. The program has started to hang on launch. It launches as a background app in Windows task manager, and next to whatever Catalog I have asked it to open it will create the usual companion files:CatalogName.lrcat-shm CatalogName.lrcat-wal CatalogName.lrcat-lock Nothing happens no matter how long I leave it. I have to kill the task, and those 3 files remain. Even though I have Lightroom set to prompt me to select a catalog every time it starts up, no matter what I try it keeps trying to open the catalog it failed to open every time it starts, even if I start it by clicking and entirely different .lrcat file.The *only* way to get the program to launch at all - even after rebooting Windows - is to remove/rename the .lrcat file it is looking for, and then it will start as normal, get to the splash screen, and create a new empty catalog with CatalogName.lrcat. From there, I can get the progr
Classic will not do an update. It has all the time and updated the June 15.4.1 version, but now I get an error 190 for what ever it is trying to download. I have Windows 10 version 22H2.
Assisted Culling is now generally available in Lightroom ClassicTL; DR: Assisted Culling has graduated from Early Access to General Availability. It gives you a fast, reviewable first pass on large shoots: it surfaces your strongest frames and sets aside the obvious rejects, so you spend less time comparing near-duplicates. You stay in control: review everything, adjust the thresholds, and override any call. If you tried it back in October 2025, it's substantially more accurate now, especially for wedding, event, group, and portrait work. We'd love for you to give it another look and tell us what you think in this thread. What it does Open an album or collection, run a cull, and Assisted Culling analyzes your images against the criteria you choose: Subject Sharpness, Eye Sharpness, Eyes Open, exposure, and more. It marks Selects and Rejects, shows you why behind every call, and leaves the final decision to you. How far it's come since Early Access February 2026: Expanded from individ
In LRC, I have many hierarchical keyword structures, amongst which are locations, i.e. Country/State/City and in some cases location or street name. Since version 15.4.1, LRC deletes upper level location keywords (Country and State, or when there's a fourth level then it deletes the city too) after a photo has been synced to the cloud. The keywords still exist in the cloud. I have checked other hierarchical trees and the keywords are all syncing correctly. If I reenter the locations the save metadata to file, the keywords once again disappear.I'm running LRC 15.4.1 on a Windows 11 Pro computer with Admin rights. Lightroom, catalog and photos are all on (separate) local nvme ssds. Plenty of space, plenty of speed.
It works fine for a few days and then won’t open. Task Manager says it is running but I see nothing. What gives?I should mention my catalog is huge … don’t know if that has anything to do with it.
I have LR 15.4.1 and get frequent catalog corruption when LR locks up. The problem existed in 15.3 so it is not related to the 15.4.1 update.If I have background AI updates active then there is a good chance that LR will just freeze. I have no option except to end task. And after this point I have seen the corruption. So now I backup 3 or 4 times per day so I don't loose too many edits. On relaunch of LR, there is no UI. the all sits around 5% CPU and just a few hundred MB of memory use.The lockup does not always happen - I could update a batch of mages (select images, CTRL+ALT+U) to refresh AI info such as masks or denoise… and this could work fine for 20 images, or lock up for just 2 images. There does not seem to be any pattern.AMD Ryzen 7 3700X, 32GB RamWindows 11 (up to date)Catalog on C: - 512GB PCS PCIe M.2 SSD (NVMe)RTX 2060, 6GB, Nvidia Studio driver version 610.62NViidea driver optimised for LR use GPU for display: On use GPU for image processing: On Use Graphics Pr
I'm having some issues with my exported photos not holding the edits I made in lightroom. Ive been doing some research online but so far, I've had no luck in figuring things out :/. Would greatly appreciate any insight that could be provided here as to what might be the problem. In one of the pictures below you can see the photo is very vibrant and colorful and the other one is dull and bland. The colorful and vibrant photo is what I see in lightroom before I export, and the bland and dull photo is what I see after I export.Thanks, in advanced!
My Lightroom Classic just updated to the latest version (13.0). When I exit, rather than the option of delaying writing XMP, it now says I should wait until it completes. The first time, I let it complete in case the delay was due to the update. I didn't time it, but it took several minutes. I went back in, and made minor edits to two images and then exited. It's been over 5 minutes, and it's only up to 14%. Why has the message changed to say you should wait? Why is it taking so long?
I even went back and looked at a JPG I exported out of Lightroom earlier this year and that image had a hefty resolution of 5000x4000. No problems there! I’m not sure what happened! help!
SUMMARY=======Importing a large image (approx. 143 MP) into Lightroom Classic crashes theapplication 100% of the time on my machine. The same crash occurs on threedifferent LrC versions, including after a full downgrade, so it does not appearto be specific to one build. Smaller images import fine, so this is asize-dependent failure in the import path.CRASH SIGNATURE (identical across 10+ occurrences)==================================================Faulting application : Lightroom.exeFaulting module : ntdll.dll (10.0.19041.7548)Exception code : 0xc0000374 (STATUS_HEAP_CORRUPTION) 0xc0000005 (ACCESS_VIOLATION) on some occurrencesException offset : 0x00000000000ff509 <-- identical every single timeWER Sig[7] : PCH_08_FROM_ntdll+0x000000000009E164Adobe crash reporter stack, top frames: [0] mems... (memset / memcpy family) [1] RtlAllocateHeap [2] RtlAllocateHeap exception = EXCEPTION_ACCESS_VIOLATIONWindows subsequently applied Fault
Lightroom Classic 12.4 / Camera Raw 15.4Just imported a dozen Fuji X-T5 raw files. White balance and tint value is slightly different for all of them as they were shot in 'Auto WB' on the camera. Wanted to adjust the tint value on all images but retain their existing WB value. Selected all, made sure Auto Sync was on in Develop mode, and moved the Tint value to 5. Expected result: all selected images should now have a Tint value of 5, while retaining their original WB value. Actual result: the WB and the Tint value for the main image was applied to all selected images, even though I had not adjusted WB at all.Did an Undo, went through all images to confirm they all had different WB and tint values. Selected a different image. Did a Select All, Auto Sync on. This time I set the WB value for my main image. Expected result: all selected images should now have the same WB as the main image, but their Tint values should be unchanged. Actual re
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.