Lightroom Classic

I have done the same Importing Process for over 10 years. When I click “IMPORT” after I have ensure File Handling, Collection Location, etc.  The status bar in the top left appears as if it were to be “working” on importing with the status bar on the top left of the LrC window; building Smart Previews, applying my Presets etc.  Then, NOTHING. When I try to repeat the process and I click on “IMPORT” again on the bottom left of the window; the folder doesn’t pop up to find the Photos, Create a Collection Location, etc. It’s as if LrC has froze. I have been trying multiple times; deleting the App and reInstalling it. Creating a New Catalog as well, and even in the new catalog LrC does the same thing as far as “working”, then nothing. 

Hey everyone, hitting a wall here and hoping someone might have run into this or found a workaround.I’m on an M4 Pro MacBook Pro (24 GB, macOS Tahoe 26.6.2) running Lightroom Classic v15.5.1 and Premiere Pro. Lately, heavy workflows like AEB HDR merges, timelapse exports, and video renders have ground to an absolute crawl.The weirdest part? My fans stay completely dead silent. The laptop isn't even breaking a sweat because the hardware isn't actually ramping up.I ran powermetrics during a timelapse export to see what was going on under the hood: CPU: 100% maxed out across all 14 cores pulling around 29–35W. GPU: Pulling a measly ~50 mW (basically idling at 0.05W). Fans: 0 RPM. Lightroom is leaving the graphics processor completely untouched and forcing the CPU to shoulder the entire export under a low total power budget.What I’ve already tried: Toggled GPU acceleration (Auto, Custom, Off) inside LrC preferences. Cleared out all preview, scratch, and media caches. Did a full, cl

After starting LR, clicking the GPS badge of a photo centers the map on the last-displayed location rather than the coordinates of the clicked photo. To reproduce on LR 15.5 / Mac OS 26.4.1: 1. Open the attached catalog. 2. Go to Map view. 3. In the filmstrip, click on the GPS badge of "miami.jpg". Observe the map centers on Miami (correct). 4. Go to Library. 5. Restart LR. 6. Click on the GPS badge of "san francisco.jpg". Observe that the module switches to Map view and the map centers on Miami rather than San Francisco (incorrect). 7. Go to Library. 8. Click on the GPS badge of "san francisco.jpg" and observe the map moves to San Francisco (correct).  

Hello,My Lightroom Classic catalog got suddenly corrupted. When I try to open it, it says the catalog cannot be opened due to a data problem or says the version is incompatible.I already tried extracting it using the SQLite command-line tool, but the newly generated file gives the same error, so the database seems severely corrupted.Could an Adobe engineer please help me repair it?Here is the link to download my zipped .lrcat file: https://1drv.ms/u/c/3b9acaaaac65ed43/IQBr1an9dGnUSZZ0Xvs_81l4AZBK4Qyq5TCf50seAZOA628?e=i1CFEaThank you very much!

What?  I can no longer print my photos with LR Classic?

If I use merge to panorama in Photoshop from Lightroom Classic, it works well, better than in just Lightroom Classic, but produces psd or tiff files which can then not be AI noise reduced in Lightroom.  Applying AI noise reduction in Lightroom first and then trying to do a merge to panorama in Photoshop, causes Photoshop to hang.  

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?

SummaryI am a professional photographer and use Lightroom Classic as my primary production software.On a high-end mobile workstation, Lightroom Classic becomes progressively slower within approximately 5 minutes of editing.During normal editing, dedicated GPU memory rapidly increases until almost the entire 8 GB VRAM of the NVIDIA RTX 4070 Laptop GPU is occupied. Once this happens, Lightroom becomes increasingly sluggish and eventually the entire Windows desktop (including mouse movement) becomes noticeably stuttery.The problem has existed since the laptop was purchased in early 2025.Despite extensive troubleshooting together with Lenovo support and the computer manufacturer, the problem has never been resolved.HardwareLaptopLenovo ThinkPad P1 Gen 7CPUIntel Core UltraGPUNVIDIA GeForce RTX 4070 Laptop GPU (8 GB VRAM)Intel Arc integrated GPURAM64 GBStorageNVMe SSDOperating SystemWindows 11 Pro (fully updated)CameraNikon Z8Compressed NEF RAW filesTypical file size: 30–40 MBLightroom Versi

today the open in photoshop as smart object layers from lightroom quit working as did the open in photoshop from lightroom for any file. Uninstalled / reinstalled without success. All apps are latest updates. Tried on a second computer ( both Macs with current OSX ). Same problem on both. Permissions on Macs for PS and LR checked. Happy to try any other suggestions.

I recently upgraded my Mac to Mac Tahoe 26.6.2.  Since then, when using Lightroom Classic Version 15.5.1 I get an error message when trying to use the Denise function (Denise Error “Unexpected error occurred whilst processing (1).  I had a similar issue with a previous upgrade which resolved when Lightroom Classic was updated.  I note that an update has recently been done so it could be sometime before Lightroom is next updated.  How can this issue be fixed

I am using Lightroom Classic on my Mac Studio on Tahoe 26.5.2. I select all photos in the album, turn on Auto Sync at the bottom of the Develop tab on the right, then select Auto. It applies to all the photos that I can see in the tray at the bottom but no more. I have to scroll over to reveal more at the bottom and then it will apply to those now showing, I can see them changing in the thumbnail, which takes several seconds, then I repeat. Since I can only show 18 photos at a time in the tray, I have to do this a ton times. This works totally fine for other manual adjustments like color balance or contrast, if I change any other setting with auto sync on, it applies to every photo selected. I’ve tried auto on all and just leaving the computer without doing anything else and it still does nothing, only applies to the photos I can see ion the tray. I left it overnight, came back and it still had not applied to them all, I scrolled over and it was now applying to those I revealed in the

A recent update to Lightroom Classic appears to have corrupted my catalogue and Lightroom Classic will no longer work…..and this is not a question, it is a request for a support on an application I am paying for that no longer works!

 I edit/process a photo (LRc 15.5) which includes several masks with mask refinement settings of edge and feather. After reviewing the edits I decide to start over and select the RESET button which then resets all sliders/setters to 0 or other baseline values. All values verified in Develop Module as reset I start editing the photo again with new edits and masks A sky mask (or other previously used mask which has mask refinement capabilities) is placed on the photo Mask Refinement feather - edge values, 10 - 3 seen in prior editing session still seen in the placement of the new mask just applied Photo again reset to baseline values. Photo verified at baseline values and no masks applied Sky mask applied to photo Mask refinement edge/feather values at 10 - 3 as seen in prior ediitng session. This process was repeated several time on several differenct photos with the same results. Mask refinement values can be reset manually or by hitting the mask refinement RESET button.

Ik wil een foto bewerken in photoshop vanuit lightroom, maar de foto verschijnt niet in photoshop. Tot nu toe nooit problemen mee gehad. Hoe krijg ik de foto in photoshop om te bewerken?

Steps to Reproduce: 1. Select an Ai mask2. Move any of the Refinements sliders from form the current value to another one and back to the current value but NEVER releasing the slider.Actual Result: A step is recorded in history but nothing changed from step 1 and step 2, the value chosen in UI is the same.Expected Result: Moving AI masks "Feather" or "Edge" sliders DOES NOT record an history step when the UI value is the same as before.Addendum: There is floating point difference in the values when moving a slider back and forth to the same value but it should not matter.Feather at 30 Feather moved from 30 to 30 again 

Hello, I have installed LR 6 on new machine. I can't activate it unless deactivated on other machine. So on other machine I did "Sign out". There is a message - "it will deactivate LR on this machine" - I clicked OK. Still can't activate. On my Adobe account there is nothing under Plans and payment->Activated devices. So haw can I use a product on new machine? I know LR 6 is quite old, but still it is something I purchuased and I want to use.

I’m shooting raw with an OM System OM-3 + 17mm f1.8 II.  Regardless if import is by “Copy to DNG” or just “Copy”, the inbuilt profile is not read.  Distortion is obvious.   In OM Workspace, the profile is read.  To get the correction, I need to go into Develop>Lens Correction and tick Enable Profile Corrections.  It makes the correction.  The dialogue box shows:Setup:   DefaultMake:   OM Digital SolutionsModel:   OM 17mm F1.8 IIProfile:   Camera SettingsI’ve never had this problem before, albeit with other OM gear.  It usually shows an icon indicating that the inbuilt lens profile has been read.

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 

Lightroom bug - hit a folder limit and unable to select the newly imported folder.452497 photographs across many drives in one catalog.The S drive has 214341 photos. It's the largest drive and so had many more folders than the previous drives.S:\Master Photos\ contains ~1633 folders. I know that's a lot but that is how her filing system was started. Those are the sequential numbers from 2220 - 3853 but there may be a sub folder or two or deleted folder in there so that's why the number is ~ approximate.Folders are labeled "sequential number"-"date" so 3853-20150316Adding one more folder caused Lightroom 4 to not allow the last folder to be clicked on and not show any images. The T:\ drive (offline, collapsed and below the S:\ drive) was collapsed and the label was overlaid on top of the "Collections" section label. Updated to latest version of Lightroom 5 via her new cloud account, had it rebuild the catalog and the same problem occurred.Created a sub folder S:\Master Photos\2012 and m

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