Lightroom Classic

Renaming a develop preset from within Favorites incorrectly moves the preset from the User Presets group into a second Favorites group.   To reproduce on LR 14.3.1 / Mac OS 15.5:   1. In the Develop Presets panel, create a new preset named Test.   2. Right-click Test and do Add To Favorites.   3. In the Favorites group, right-click Test, do Rename, and rename it to Test 2.   4. Observe there's now a second group named Favorites containing Test 2, and Test 2 no longer occurs under User Presets (incorrect).   5. Right-click Test 2, do Show In Finder, and edit it's .xmp file. Observe that it records the group as "Favorites" (incorrect): <crs:Group> <rdf:Alt> <rdf:li xml:lang="x-default">Favorites</rdf:li> </rdf:Alt> </crs:Group>   6. Drag the second instance of Test 2 back into User Presets, and the second bogus Favorites group disappears.

 Windows 11 It's reporting the following error, intermittently when synching metadate over multiple images.  This can sometimes be fixed by closing/opening LRC, sometimes, not so much ~~~~~~Arggh, I couldn't replicate, but the error was to the effect that the database or catalog failed ~~~~~  Rebooting the computer was the only working solution.It's also Refusing to accept my titles and descriptions.  When I enter them and move to the next file, if I return to the one just edited, there is no title nor description.  If I type the first letter of the title previously entered, the suggestion of the entire title appears.  After closing and reopening several times, the title and description finally appear.  This is not a lightning fast computer, but it's no slowpoke, either. Also, when two images are stacked and one of them is labeled red, it cannot be unlabeled withoug unstacking 

Hello, I'm finding that LRc starts to become less responsive after a few minutes of edting pictures. I see this mainly in simple things like trying to crop a picture, or even scroll through the filmstrip at the bottom of the screen in Develop mode. The program stops and starts and jerks as I try to do things. I try things like clearing the cache, restarting and it doesn't seem to fix it. I'm really only running LRc and a browser at the same time, so I'm unsure what is going on. Any ideas? System info posted below. Lightroom Classic version: 13.1 [ 202312111226-41a494e8 ]License: Creative CloudLanguage setting: enOperating system: Windows 11 - Business EditionVersion: 11.0.22621Application architecture: x64System architecture: x64Logical processor count: 32Processor speed: 3.4GHzSqLite Version: 3.36.0CPU Utilisation: 0.0%Built-in memory: 65445.7 MBDedicated GPU memory used by Lightroom: 10480.0MB / 24340.0MB (43%)Real memory available to Lightroom: 65445.7 MBRea

I've tried to use the denoise on a Lossless and compressed L RAW files from my A7IV. Initially it will start the process then stop. THen I'm unable to check the denoise box at all. I've updated to LR Classic 14.5 and camera raw 17.5. Updated to Sequoia 15.6. Lightroom Classic version: 14.5 [ 202508061311-4cef2162 ]License: Creative CloudLanguage setting: en-AUOperating system: Mac OS 15Version: 15.6.0 [24G84]Application architecture: arm64Logical processor count: 10Processor speed: NASqLite Version: 3.36.0Power Source: Plugged In, 100%Built-in memory: 32,768.0 MBDedicated GPU memory used by Lightroom: 9,081.5MB / 21,845.3MB (41%)Real memory available to Lightroom: 32,768.0 MBReal memory used by Lightroom: 6,191.5 MB (18.8%)Virtual memory used by Lightroom: 420,971.1 MBMemory cache size: 247.9MBInternal Camera Raw version: 17.5 [ 2318 ]Maximum thread count used by Camera Raw: 5Camera Raw SIMD optimization: SSE2Camera Raw virtual memory: 1266MB / 16383MB (7%)Camera Ra

When I import files from my Autel Evo 2 Pro V3 the .dngs look completely different than the actual photos. They import fine but when I click on them the zoom level changes and they turn neon red - the white balance sliders go to the far ends. Also the only profile availble is "XL706" and I can't add or change others. Adaptive color is the only other option and it makes the colors worse.  No amount of sliding fixes this insane color. Everything looked fine while taking the photos but they are unusable.  I shot on auto white baalcne and tried again at 5500k - does not make a difference. The other thing is all my presets are in italics aka will not work with the selected photos which is a dng, which is what I used to make the preset. This does not happen with any other photos from any other camera. For $3500 this drone f*cking blows. Do not buy it. 20MP my ass, 6k? Nope, 4k? Maybe but its a stretch. Controls are garabge too.  Any ideas whats happeni

I messed up moving files around outside Lightroom to the point there is no longer any convention in the file names. My situation now is that I have a missing folder with 222 images. Those 222 images are present in the folder with 687 images. Is there a way to find them automatically by matching metadata such as time taken?

Do I need to disable color management in LR when printing with custom ICC?

I have a 2017 Mac book pro but I cannot update the operating system to 13 or above, which is required to install the latest version of Lightroom. AS a consequece I cannot currently use LR on my Mac. The mac is in perfect working order and I have no desire to buy a new one. Is there anytging I can do?

13.0.1 on Mac Studio M2 Max 96GB RAM. When trying to open a photo in a third-party app for editing, the "Preparing file for editing" progress bar instantiates but doesn't progress beyond 0%. If I view the source image folder in finder, I can see that the tif or PSD has been created almost immediately as expected, but then nothing happens...the progress bar stays stuck and the third-party editor doesn't launch. I've been able to reproduce with On1 Suite, Luminar Neo and SilverEfex. On rare occasions, when I've had the patience, the third-party application has eventually launched after 20-30 minutes. This worked as expected in versions prior to 13.

Hello,The cloud upload apparently gets stuck on one photo.The upload runs endlessly, but the number of photos remaining to be uploaded (973) does not decrease. However, the log shows no error, and I also don’t know which photo it is stuck on.What can be done in this case?I have the newest LR Classic Version (14.5) on Windows.I really appreciate any help. Thanks!

I created the catalog a few days ago and it worked for a while. I imported about 200 photos and processed most of them. Then the next day I noticed that the photos reverted to the original imports. I then discovered that several catalog files were automatically going to the OneDrive Recycle bin. I was unsuccessful trying to restore these files and I believe the catalog is hopelessly corrupt. I have not been able to open LR Classic the last few days. Should I reinstall Lightroom Classic?  I have about 6,000 photos in another catalog. I do not know if this catalog is corrupt, too. 

Hi, I have to admit that I'm a very curious person, maybe I'm a photojournalist also because of this. I'd like to know why still on August 22, 2025, working with Lightroom Classic , "Selecting the Crop Tool will exit Reference View" and if I'm doing the same thing with Lightroom Desktop I'm able to crop in the Reference View. Why Adobe? Why?!?  

Trying to resize an image. I'm trying for a .. 1920x1080 image and I keep getting a .. 1620x1080 image after clicking "Resize to Fit" box and setting parameters.Windows 11LrC version 14.3.1  

I have 11 years of photos in my main Lightroom catalog. On my harddrive, the photos are put into folders by year taken, and then a folder for each "shoot". I am unable to find (for example) photos taken in 2024.  You can see a snapwhot of my catalog. Filtering by 2024 does not work. I don't understand the order of folders displayed or how to manage it. You can see just a snapshot of my catalog.

Hi,I'm confused about the remove photo from Lightroom process, which has changed from how I remeber it. The message used to say "Remove from catalog but it will remain on disk" but now the following message is displayed...Remove Photo from Lightroom CatalogThis photo will be removed from your Lightroom Catalog and any synced Lightroom Client. Select "Delete from Disk" to also move the selected photos on your computer to the Finder''s trash I guess it's something to do with "any synced Lightroom Client", which I didn't even knwo you could do!! I need to unassociate the client maybe?Has this change been rolled out across Lightroom CC or have I inadverently changed something? I do have Lightroom CC running on a desktop Mac and a Macbook Pro but obviously different catalogs and the Macbook LrCC keep asking "Sync this catalog instead?" to sync to the Mac catalog, which it never used to do?I just want to keep the Mac (for office work) and Macbook (for field work) catalogs separate with

라이트룸클래식 컬렉션 작업시 처음에는 컬렉션 작업이 잘되다가 어느정도 작업시 컬렉션에 이동이 되지 않음

When a raw file is imported with the option Copy As DNG and a metadata preset is applied during import, the values set by the preset disappear from the metadata panel after a couple of seconds. A workaround is to set the option Catalog Settings > Automatically Write Changes Into XMP.     Originally reported by another person: https://www.lightroomqueen.com/community/threads/copyrights-disappear-during-dng-conversion.53023/    To reproduce on LR 14.4 / Mac OS 15.5 (see the attached screen recording):   1. Download and open this catalog: https://www.dropbox.com/scl/fi/97ztsg16ekxc2h297lv4w/copy-dng-metadata.2025-06-23.zip?rlkey=9iqixpsthk7c7e3ybbtvlboh1&dl=0   2. Define a Metadata preset "Copy As DNG" with the fields:   Caption: Hello world Copyright Status: Copyrighted. Copyright: 2025 Joe Cool   The preset's .lrtemplate is in the catalog folder.   3. Verify Catalog Settings > Automatically Write Changes Into XMP is unchecked.

 I need BADLY the jpeg file name OR a sequential number to print ON THE IMAGE when exporting (not renaming a file or jpeg).  This way the client can tell me which image they want when i send 100 similiar images.Why is this not in Lightroom? Should be in watermark editor OR in export. The work around is the PRINT area, which is quite barbaric in nature for digital. PLEASE ADOBE?   You mess with Ai and other useless features, but we NEED features that help us SELL images so we can PAY you. Contact me if you need Clarification.  

Please see the attached screenshot.   Lightroom Classic version: 14.5 [ 202508061311-4cef2162 ]License: Creative CloudLanguage setting: enOperating system: Windows 11 - Home Premium EditionVersion: 11.0.26100Application architecture: x64System architecture: x64Logical processor count: 24Processor speed: 3.4GHzSqLite Version: 3.36.0CPU Utilisation: 0.0%Power Source: Plugged InBuilt-in memory: 65325.1 MBDedicated GPU memory used by Lightroom: 8658.9MB / 15907.0MB (54%)Real memory available to Lightroom: 65325.1 MBReal memory used by Lightroom: 13382.6 MB (20.4%)Virtual memory used by Lightroom: 24487.6 MBGDI objects count: 1282USER objects count: 4266Process handles count: 12655Memory cache size: 14467.4MBInternal Camera Raw version: 17.5 [ 2318 ]Maximum thread count used by Camera Raw: 5Camera Raw SIMD optimization: SSE2,AVX,AVX2Camera Raw virtual memory: 4694MB / 32662MB (14%)Camera Raw real memory: 4707MB / 65325MB (7%) Cache1: Final1- RAM:1498.0MB, VRAM:2105.

The Nikon Z5 II Raw Files (NEF Files) are having a known probem in LR Classic, including the very latest release 14.4. Here is a link to a YouTube video detailing the problem, and a summary of the video with chapter markings. It's a known issue, and thousands of people are discussing it on multiple social media outlets. Lightroom Classic will read the RAW files from the Nikon Z5 II, but when "auto" WB is applied, a magenta cast takes effect. I spoke to an Adobe rep today. We could not troubleshoot it. Nikon says it's an Adobe issue, and I agree, as this issue does NOT occur in Capture One, or Nikons own software. The JPEGS from the camera are great and as long as "AS SHOT" is applied in LR, it works, but any other WB settings (Auto, Daylight, Cloudy) etc... leans the file so far into magenta, it's unusable. I also tried using the eyedropper tool on a grey card, and it also leans magenta. I am on Mac OS, Sequoia 15.5. Anyone else having this issue? How can we escalate it to Adobe s

I have been experiencing a persistent rendering issue in both Lightroom Classic and Lightroom CC for over 3 months. The problem occurs on HiDPI/4K displays (including my laptop’s 2880x1800 screen and dual external 4K monitors). In Lightroom Classic: Develop mode only displays the photo in a quarter of the image area. Library module displays normally. Disabling GPU acceleration fixes the problem, but this is not an acceptable long-term workaround. In Lightroom CC: Both Grid and Detail view only show the image in a quarter of the expected display area. Unlike Classic, disabling GPU acceleration does not help. System Info (from CC): Lightroom CC 8.5 x64 [20250805-2023-ec91a85] OS: Windows 11 Pro (2009) [System Info reports as “Windows 6 / Windows 8 Pro (2009)”] Laptop: ASUS Zenbook 14 UX3405MA (Intel Core Ultra 9 185H, Intel Arc Graphics, driver 32.0.101.6314) RAM: 32 GB Displays: Laptop (2880x1800), 2x 4K externals (at other residence), currently tested with 3x 1920x1080 externals + l

I have Windows 10 Pro and Lightroom Classic 14.5 installed.I've been experiencing system instability issues since early 2025.Lightroom has corrupted my catalogs and is almost impossible to work with, because the error appears just 10 seconds after opening it.There's no time to load the photos into the gallery.Sometimes the catalog lasts a little longer.But then it crashes when I try to import photos.Or it crashes when I open the print module.The errors are constant, and I can't find a way to resolve them.I've uninstalled Lightroom to install previous versions, and it didn't work.I've formatted my PC to rule out operating system installation errors or possible driver errors.I've installed the latest version of all the drivers for my computer.However, Lightroom still crashes.I've opened my catalogs using the "catalog integrity check" option, but Lightroom doesn't detect any errors.However, once the catalog is launched, it causes a crash error again.After each error, Lightroom asks to che

Hi all!  I've tried searching out the answer to this issue using multiple search queries but haven't been able to find this question previously asked/resolved.  I did spot some issues that had been posted about regarding Mac computer permissions, and making sure to select "Copy" (as opposed to "Add") in the import dialogue, but neither seemed applicable here. However that said, apologies in advance if this has been asked before and I just was unable to come up with the magical question words to plug into Google. SYSTEM SPECS: I'm currently running Lightroom 6.10 on a Windows 7 computer with two internal drives: an SSD as the primary drive with the OS on it ("Local Disk (C:)") and an HDD where I store the bulk of my files, including my photos ("RUSS (B:)")BACKGROUND: Historically when I've imported photos off of my camera/memory card my workflow has been to have the "Don't Import Suspected Duplicates" option checked, with the Destination panel set up to organize the imported p

Hello,   I am experiencing a recurring issue with the Sky Mask AI tool in the latest version of Lightroom. After creating a Sky Mask, it initially works fine and appears in the Masking panel. However, when I close and reopen Lightroom (or sometimes after syncing), the Sky Mask remains in the list but becomes completely empty, as if the detection has disappeared.   Important details:   The mask is still listed in the Masking panel, but there is no selection inside it. This only happens with Sky Masks. Other AI masks, such as Subject or People, are preserved correctly. I have already tried clearing the cache, updating Lightroom to the latest version, and disabling GPU acceleration, but the issue persists. I am working with RAW files, and the problem repeats consistently.     It looks like the Sky AI detection is failing to reload after reopening, leaving an empty mask. Could you please confirm if this is a known bug and if a fix is planned?   Thank