Lightroom Classic

When importing images (I shoot Nikon D800 and D850 with Nikon lenses), lightroom will not identify the lens correctly.  The import shows up as a generic lens:import will be 24.0-120.0 mm f/40 Correct is:Nikon AF-S Nikkor 24-120mm f/4G ED VRThere are a small amount of images that have the correct information in the catalog.  If I look at the EXIF data from a sample of two files, one that is correct and one with the generic name, both have the correct information.  HOWEVER, comparing the xmp files is not.  The DSC_9863.xmp file is the one that works and the DSC_9729.xmp is the one that is the generic name. This has been a pain in my backside for a LONG time and I hope someone has some suggestions. 

I store all of my images in a LR catalog. That’s how I was taught to do it. I can access certain years of photos based on my hard drives, labeled LR1, LR2  and so on. My first catalog is from 2010.  However, when LR says it cannot open my catalog unless I update I have been doing so. Now, when I go to open catalogs on older hard drives, I can’t! Please help. I just need access to my photos. TIA!

I am experiencing a repeatable startup failure in Lightroom Classic 15.4.1 on macOS Tahoe 26.5.2. Lightroom never progresses past the splash screen and remains indefinitely at “Reading Preferences.”The application does not crash or generate an error message—it simply hangs.Environment:Lightroom Classic: 15.4.1 macOS: Tahoe 26.5.2 Hardware: Apple Silicon Mac Adobe Creative Cloud: Current versionSteps to Reproduce:Launch Lightroom Classic 15.4.1. Splash screen appears. Startup stops at “Reading Preferences.” Lightroom never completes startup.Expected Result:Lightroom Classic should complete initialization and open normally.Actual Result:Lightroom remains indefinitely at “Reading Preferences” and must be Force Quit.Troubleshooting Performed:Uninstalled and reinstalled Lightroom Classic. Confirmed Creative Cloud is installed and signed in. Reset Lightroom preferences using the keyboard shortcut. Deleted Lightroom preference files manually. Removed Lightroom support files. Restarted the Mac

I was using Lightroom Classic, hovered over the Adaptive:Sky drop down menu and it crashed.When I re opened it had reset itself to Default, every menu had to be reopened and it will not allow me to save an image as a jpg, I only get jpeg2000 and jpeg XL in the menu, I do not have any unflattened layers.

Hi I have recently migrated my catalogue from a very old version of lightroom to the most recent but even though the program knows where the files are located it is not showing any previews of my images, just greyed out boxes. I have tried deleting the preview files held but that hasn’t worked. I have also tried changing the colour space but that hasn’t worked either. Please help! Lightroom Classic version: 15.4.1 [ 202606201310-b9f148a4 ]License: Creative CloudLanguage setting: en-GBOperating system: Mac OS 26Version: 26.5.2 [25F84]Application architecture: arm64Logical processor count: 14Processor speed: NASqLite Version: 3.36.0Adobe GSDK Version: 1.4.0.213Built-in memory: 49,152.0 MBDedicated GPU memory used by Lightroom: 60.3MB / 38,338.5MB (0%)Real memory available to Lightroom: 49,152.0 MBReal memory used by Lightroom: 979.3 MB (1.9%)Virtual memory used by Lightroom: 427,402.0 MBMemory cache size: 0.0MBInternal Camera Raw version: 18.4 [ 2608 ]Maximum thread count used by Camera

Just starting today the Map module is leaving behind markers for a photo or photos that have been moved. It also continues to show markers for photos that have been opened but are no longer in the directory being worked in. If I leave LRC and come back in, all is well but I've never had to do this before. It is more of an annoyance than a major issue, but it does clutter up my screen while moving things. I am in the process of locating old photos that have inaccurate or no geotagging and this behavior is slowing me down. I’m running 15.3 on a MacBook Air. Has anyone else seen this or have a suggestion of how to fix this behavior? 

See horizontal and vertical line on right. half of the pictureThe artifacts (lines) became visible in a part of the pictured that I repaired with the Remove - Generative AI tool. The artefact only appears if Denoise AI is applied as well. Disabling one of them, makes the artefact dissapear. No other edits applied. Camera is Sony RX10iii, cRAW (.ARW file).Lightroom version 15.4.1macOS Tahoe 26.5.2

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. 

Bonjour après avoir été dans Préférences/Lightroom synchronisation/supprimer les données synchronisées/Lr web puis supprimer la bibiliothèque Lightroom, impossible de supprimer la bibliothèque. Après avoir recopié la phase, "supprimer" reste en grisé. Une idée du problème?

I have seen posts from as far back as 2011 asking this same question and it is astounding to me that LrC doesn’t have the ability to batch re-name files using string substitution. So it appears my options are: create a naming template that will overwrite the part of the filename that I want to keep, or rename them in Bridge the way I want and then re-import them into LrC. Anyone else have a way to accomplish a batch rename that allows for a simple find and replace?

Hey, I read the best monitor for photo editing and decided to buy this one: https://www.monitor-picker.com/en-us/monitors/lg-27ep950-270-3840-x-2160-60-hz-monitor. Which one would you guys recommend me instead? My budget is u pto 700€

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

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

I upgraded to 15.4.1 about 10 days ago and have been experiencing LRC crashes ever since. It’s mostly OK in the Library Mode but if I go into Develop, it usually crashes after a few minutes. If I also have Chrome open, it sometimes freezes as well and gives me a ‘low memory’ reason.I run LRC on an LG Gram 16” laptop which uses an Intel Iris Xe Graphics card with 128 MB of dedicated video memory and 8 GB of shared system memory. I suspect those numbers may be low to support LRC, but none of this happened before upgrading to 15.4.1. LRC ran quite well before the upgrade.Any ideas on how to fix this before I reluctantly buy a new laptop?

I have encountered an instance where a wide gamut orange colour appears desaturated in HDR editing mode. I have the uploaded output PQ HDR AVIF files to https://andrewkeyanzhe.github.io/posts/Lightroom_vs_darktable/ for comparison. My website serves the uncompressed HDR AVIF files, so you should be able to see the difference on an HDR capable device and browser (e.g. Macbook Pro with XDR display with Google Chrome)   The camera used is the Panasonic Lumix S5ii   Details:  Version of the app - Lightroom 14.2 (Camera Raw 17.2), Lightroom mobile v. 10.3.1 71F6C8/202 Platform and OS version - Macbook Pro 16 M1 Pro, macOS Sequoia, iPhone 14 Pro Max, iOS 17.5.1 Basic steps to reproduce the problem - Download the raw file https://drive.google.com/drive/u/0/folders/1YIhkxHvp77HHTaanyFJ5LXX28jH74Rau , open in Lightroom, turn on HDR editing mode, increase the exposure by 3.4 stops so it matches https://youtu.be/0FYjApop7Mk?si=S-cXCX-0hyAvsT

After the updated 15.4 my images have degraded quality using the same editing workflow and editing process as before. When boosting the exposure the noise profile has changed to a more pixelated versions and artificial look. After applying Denoise AI the shadows and mid tones have a posterisation look, especially around high contrast edges, that did not appear before 15.4No matter what amount of Denoise AI level I put the image quality looks horrible, where before using 50-100 looked great now it looks very bad and I can’t use more then 5-15 and have to accept noise in the images.I have tried the same files on a Windows 11 with i7 9750H,16GB DDR4 and RTX 2060 6GB and Mac mini M1 base model with 16GB RAM with the same issue being presented. Both machines are OS and Drivers updated to Jul 2026. This problem has persisted for almost 3 weeks since the Lightroom Classic 15.4 and 15.4.1 was introduced. Both software have been installed via Adobe Creative Cloud with updated Adobe Camera RAW t