Lightroom Classic

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?

A login window pops up every time I open the program. Please fix this issue, as it is incredibly annoying. 

THe subfolders appeared in the folder panel in LRC but separately and not in the parent folder.  When I tried again to import the same, the images were greyed out, indicating they were already imported.  The parent folder is on the disc but does not appear in the folder panel in LRC.  I want the subfolders under the parent folder to keep things organized. I tried  to create a new parent folder but it did not appear on the disc or in LRC.  How can I collect the subfolders under a parent folder?

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

Import Keywords — Do Not Export flag not applying to existing keyword namesI'm importing a plain text keyword file via Metadata > Import Keywords (tab-indented, [bracketed names] for Include on Export = off, {curly brace} synonyms). It works fine for brand-new keyword names, but when the imported name matches a keyword that already exists elsewhere in the catalog, the bracket is ignored — after import, the existing keyword's Include on Export checkbox stays exactly as it was before, checked or not.Is this expected behavior (import merges into an existing same-name keyword and won't touch its Include on Export flag from the file), or am I missing correct syntax/an option to force it? Is there any way to set Include on Export via the import file for a keyword name that already exists in the catalog, or is manually toggling it in the Keyword List panel after import the only route?Lightroom Classic, imported via a plain .txt file (also tried .csv, same result). Thanks for any pointers.

I am unable to import photos into Lightroom Classic suddenly this morning. When I attempt to import new photos, either from an SD card or my hard drive, it displays them as if it is going to import them, but then nothing happens, and the import photos and videos button becomes grayed out. If I close and reopen Lightroom Classic, the button seems to be active, but than again nothing happens after I click it, and then it becomes grayed out again.

Adobe Lightroom Classic 15.5 import problem on Windows 11Hi Adobe team and Lightroom Classic users,I’m experiencing a serious import problem with Lightroom Classic 15.5 on my Windows PC, and this only started happening recently.System: OS: Windows 11 Pro 25H2 Lightroom Classic: 15.5 Catalog: Tested with both my current catalog and an older catalog Photos: Sony ARW RAW files Import: Using Add Storage: Tested from different physical drives Problem:Lightroom can see and read the photos normally in the Import dialog. For example, I can select 1,446 ARW files and Lightroom correctly displays all the thumbnails and recognizes the files.However, when I click Import, the import progress bar only runs for around 2 to 3 seconds and then disappears.After that, Lightroom returns to the Library and shows:All Photographs: 0None of the photos are added to the catalog.This is happening even when I try importing only a few photos.What I have already tried: Tested the original photo drive Mo

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

4 x 6 inch photo printing in lightroom classic not centered when i reduce the size to passport photo. it will print it all the way to the end towards the left side. But if i print the full size instead of reducing it, theres no problem at all.

Lightroom Classic silently skips files during batch export if it fails to write Credit/IPTC metadata. Additionally, it misreports local file errors as network issues.Steps to reproduce: Select a batch of images (e.g., 120 files). Export with a metadata preset that includes Credit/Copyright info. Observe that some files are randomly skipped. Actual Results: Only a portion of the files (e.g., 106 out of 120) are exported without a proper per-file error log. A "No network access" error pops up mid-export despite a perfectly stable internet connection. The export engine deletes the entire image file if the metadata write operation fails, instead of just skipping the metadata and saving the image. Expected Results: Lightroom should export the image even if metadata injection fails (best-effort export). Errors should be accurately reported (local I/O failure, not "No network access"). A detailed log should show exactly which files failed and why.  

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

  I have a question about the processing of Canon RAW files that were shot with Highlight Tone Priority (HTP) enabled.  These images are underexposed by one stop at capture time by lowering the ISO.  For example, if you shoot at 1/2000, f/8, ISO 400, the actual exposure is done at 1/2000, f/8, ISO 200 and the file is tagged as having HTP enabled.  When you bring such a file into Canon’s DPP software, it recognizes the HTP flag, and automatically applies a special tone curve which will brighten the shadows and midtowns by one stop, but will attenuate the effect on the highlights.  My understanding is that Lightroom Develop will recognize the HTP flag, but will simply brighten the entire image by one stop without making any special accommodations for the highlights.  This is also the behavior I see when testing this out on my own.  However, I continue to see folks claiming that Lightroom Develop will behave exactly like DPP on RAW files shot with HTP.  Can someone give a definitive answe

LR Classic 15.5, Windows 11 ProTrying to connect to an SFTP server, either to browse for a folder in the “Configure FTP Transfer” dialog, or to upload a project, fails with the error:“Cannot browse the FTP server, because an unknown error occurred. (CURLE_SSH)”On the SFTP server side, the error is:Aug 25 20:57:39 pi1 sftp-server[811]: error: process_read: read "/home/jsmith": Is a directorywhere “jsmith” is the user connecting to the server. So the error is trying to read the user home directory. For a while cURL accepted the “/~” path for the user home directory, but since 2023 this syntax is no longer accepted, see:https://github.com/curl/curl/issues/17534It is necessary to terminate all directory references with an ending slash, i.e. “/~/”  or (79) Error in the SSH layer (CURLE_SSH) is raised.I can replicate the same error easily from the command line:curl --k sftp://<sftp_server>/~ --user "<user>:<password>”triggers the same errorcurl --k sftp://<sftp_server&gt

In library, I hit R to open crop tool in Develop. But this opens crop overlay, with the Zoom tool, not the crop tool. Hitting R again (closes crop ), then R again, will open crop overlay with the crop tool.The in the Right-hand panel the Crop section is greyed out too.

EnvironmentMac mini M4 24 GB unified memory macOS Tahoe 26.5.2 Lightroom Classic 15.5 Apple Silicon / arm64 Lightroom Classic catalog with images using AI masks, Remove and Lens BlurProblemLightroom Classic produces random blue horizontal lines/artifacts on images after AI processing.The artifacts are variable and may appear only several seconds after selecting the image in Develop. They can also be present in exported JPEG files.The problem appears to be strongly related to Lens Blur.Reproducible behaviorI can reproduce the problem with the following sequence:Open an image containing AI masks and/or Remove edits. Apply Lens Blur. Lightroom starts AI processing in the background. After some time, random blue horizontal artifacts appear in the image. The artifacts can also appear in exported JPEG files.The behavior is not simply a display-only problem because the artifacts can be present in the exported JPEG.Important observationsWith Graphics Processor disabled:Lens Blur ON → blue arti

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

This post applies to Lightroom Classic and Lightroom Desktop.  Feedback for Camera Raw should be posted here.   Update February 2025:Adobe has introduced two Adaptive Profiles – Adaptive Color & Adaptive B&W.   Getting started with the Adaptive Profiles:  Access a profile inside the profile favorites menu.  In addition, there is a new section for Adaptive Profiles in the Profiles browser.  Enable the profile and adjust the ‘Amount’ slider as desired.  Use the rest of the Camera Raw tools just like you would otherwise.  Check out the Help Page for more detailed usage information. For more technical information on the underlying technology, please refer to this blog post.    Please try the profiles and share feedback in this community forum thread. It would help to include details like how you access Camera Raw (via Adobe Bridge or Photoshop), your computer system details, and as much information as possible about

Nach dem Verschieben und Umbenennen von Ordnern außerhalb von Lightroom Classic zeigt der Ordnerbereich dauerhaft „Unterordner fehlt/fehlen“, obwohl laut Lightroom keine Fotos fehlen. Das Aktualisieren des Speicherorts und Zusammenführen behebt die Warnung nur bis zum Neustart. Ursache ist ein unsichtbarer, leerer Katalogeintrag für einen nicht mehr vorhandenen Ordner. Durch erneutes Anlegen dieses leeren Ordners verschwindet die Warnung.Lightroom-Classic-Version 15.5 Windows-Version 11 Ordner wurden außerhalb Lightroom verschoben beziehungsweise umbenannt Alle Fotos waren verfügbar: „Keine fehlenden Fotos“ Trotzdem erschien dauerhaft: „Unterordner fehlt/fehlen …“ „Speicherort aktualisieren“ und „Zusammenfügen“ halfen nur bis zum Neustart Katalogprüfung und Optimierung änderten nichts Ursache war ein unsichtbarer leerer Katalogeintrag für F:\Fotos\Lightroom Das erneute Erstellen dieses leeren Ordners beseitigte die WarnungLightroom Classic retains an inaccessible zero-image folder reco

I installed the latest version of Lightroom, and every time I try to paste a preset onto a photo, I get the message: “Some AI models are downloading. Please try again later.” However, nothing actually downloads, and I can’t use my presets. And also I can’t use the AI in Lightroom Classic 

Since the latest versions of Lightroom Classic and MacOS the masking of people always shows “No people found” – even on photos where it was working before. Lightroom Classic version: 15.2 [ 202602111402-ec4112e8 ]License: Creative CloudLanguage setting: en-DEOperating system: Mac OS 26Version: 26.3.0 [25D125]Application architecture: x64Logical processor count: 24Processor speed: 3,3GHzSqLite Version: 3.36.0Adobe GSDK Version: 1.4.0.171Built-in memory: 196.608,0 MBDedicated GPU memory used by Lightroom: 4.743,3MB / 16.368,0MB (28%)Real memory available to Lightroom: 196.608,0 MBReal memory used by Lightroom: 3.040,3 MB (1,5%)Virtual memory used by Lightroom: 55.303,7 MBMemory cache size: 62,7MBInternal Camera Raw version: 18.2 [ 2482 ]Maximum thread count used by Camera Raw: 5Camera Raw SIMD optimization: SSE2,AVX,AVX2Camera Raw virtual memory: 631MB / 98303MB (0%)Camera Raw real memory: 644MB / 196608MB (0%)Cache1: Final1- RAM:519,0MB, VRAM:1.818,0MB, ALP05331.ARWNT- RAM:519,0MB, VRAM

 I recently discovered that banding has started appearing in smooth color gradients when saving JPEGs in Adobe Photoshop. Naturally, I always save at maximum quality—12 out of 12. If I save as an 8-bit TIFF and then convert to JPEG using FastStone, I can select RGB as the photometric type in the save options; furthermore, I don't necessarily have to choose 100% quality—which would result in a 40 MB file for my example—since 95% is perfectly adequate for me, yielding flawless gradients and a file size of 16 MB, matching what Photoshop produces at its maximum quality setting (12 out of 12). Samples are here: https://disk.yandex.ru/d/7mPxpYfAsDOR7g

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.

Adobe Lightroom 15.4.1 is crashing repeatedly during the culling process and causing my  pc computer to run terrible slow.  I had to remove it and roll back to a previous version of LRC

Ik kan de programma's niet updaten. Ineens werkt het niet meer goed, het importeren van 60 foto's duurt ruim 9 uur in Lightroom Classic