Lightroom Classic

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.

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?

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.

  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.

Apple ProRaw images taken in Apple's camera app on my iPhone 14 Pro generally work well in LrC these days, which is great. In LrC I often use the "Apple ProRaw" profile.   When I perform a panorama merge of these images, however, LrC reports that the resulting .dng file is using the profile "Apple Embedded Color Profile" but shows an exclamation mark: "Profile missing." See attached screenshots.   I wonder if this is an inadvertent result of LrC's rule that only Apple ProRaw files have the option of the LrC ProRaw profile, and that the merged file is not recognized by LrC as a ProRaw file. Can this please be improved, or is there a workaround?   Thanks, Wallace

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

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 

Hola;Es mi primer post, he estado indagando por la comunidad, y no he acabado de encontrar la solución.Uso LRC en un MacBook Pro y en varias ventanas de ajuste tengo problemas de redimensionar (salen cortadas). Me di cuenta en la de ajustes de mascara (adjunto captura), pero repasando algunas otras secciones como Ojos Rojos, Recorte… también tengo el mismo problema (adjunto capturas)He probado en modo pantalla completa y nada, se queda igual.Alguien sabe como solucionarlo? Es muy molesto no poder trabajar bien.Muchas gracias.  

Why don't you help us out and incorporate logic inside of Lightroom “auto” to disable vibrance and saturation adjustment on profiles other than your native profiles like Adobe Color and Adobe Standard.  It was designed to work only with your color matrices.

I just reinstalled LRC 15.5  on iMac 27” 2019:sequoia 15.7.9, 64GB RAMI get the permissions problem which is normally resolved by granting full disk access, but this message is followed by several others each specifying the folder to which it cannot write; this despite full disk access being granted. Ive tried restarting as well. I don't dare use it in case the back ups might be corrupted. It DOES open though.Ive not had tis many messages before-whats going?  also when I try to access preferences I get another error message of the same ilk 

I was asked if I could help a Mac user of LrC resolve a problem, but being a Windows user, I have been unable to help.Whenever they run LrC inDevelop, this cache location rapidly consumes their hard drive storage:/Users/[username]/Library/Caches/com.adobe.LightroomClassicCC7/com.apple.e5rt.e5bundlecacheIn the user’s own words: ‘Issue: A cache folder grows continuously while Lightroom Classic is open in the Develop module, eventually consuming almost the entire SSD. The problem has been so bad for months, this user is about to ditch LrC forever. 

Dear Adobe Team, despite having followed some recent tipps (like deleting preferences in the library, deleting cache, changing the performance settings, deactivating modules etc.) my Lightroom Classic V14.4 is working very very slowly in the developer module: going to the next image is lacking performance and is delayed, copying the image settings to the clipboard is delayed 2-3 seconds... All this happened directly after updating from the previous version befor 14.4.My hardware was not changed in between, catalog was/is the same etc. Working on a Mac Studio M1 with 64GB Ram OS Sequioa 15.5, just one display.LR classic 14.4 It would be super nice if there would be a more helpful tipp or update to get back to the previous performance. Best regards Jan

Mac version: macOS Monterey 12.7.6Lightroom CC Classic: 13.5.1 I aware a 13.4GB "Mobile Downloads.lrdata" when I move cc classic to new mac machine  After study what is this file about, I find it related to I sycned iphone in past (should be import iphone in past), seem the file flow is from iphone syn to clould and cc classic download those sync photo from clould to local to create this "Mobile Downloads.lrdata". My question is, is there any way to housekeep "Mobile Downloads.lrdata"I located "iphone" under "Folders" and drag those file to my NAS, the size of "Mobile Downloads.lrdata" remain unchange, should I deal with this problem in clould level?

Product/Version: Lightroom Classic 15.5, Adobe Camera Raw 18.5 (August 2026 release)OS: macOSCamera/File type: DNG (ProRAW), iPhone 15 Pro back triple camera 6.765mm f/1.78Description:Certain unedited DNG photos show a small rectangular geometric artifact (jagged blue/cyan/green diagonal streaks fading to white) consistently positioned in the same spot on the image. This artifact appears in:macOS Finder preview (especially on window resize) Lightroom Classic Library grid and Develop module The final exported JPEG — the artifact is baked into the output file, not just the on-screen previewOut of 964 photos in the catalog, 13 are affected so far, all unedited DNG files (no Develop adjustments applied), each with the artifact in a different location and size.Steps to reproduce:Open a catalog/folder containing unedited iPhone 15 Pro ProRAW DNG files. Identify an affected photo (artifact visible in Finder preview, Library grid, or Develop module). Export the photo to JPEG. Open the exported

When selecting multiple photos and applying auto settings (Devleop Settings > Auto Settings), only a small portion of the photos have auto settings applied. This can be anywhre between 50 and 700 photos. There seems to be no logic to how many photos correctly have auto settings applied. It seems to work for more photos when selecting in the Library tab as opposed to selecting in the Develop tab.    Running Windows 10 on Lightroom 13.2. This has been happening for a couple years now.    Same as post: https://community.adobe.com/t5/lightroom-classic-discussions/auto-adjust-settings-does-not-apply-to-all-the-selected-images/td-p/13511661

After exporting a gallery on my Mac to an external hard drive. I returned to LC and all my edits and history have been removed from the catalogue. When I launched the catalogue it said there was an issue and to fix.However this has not fixed the issue and all my edits have now gone along with the history.