Lightroom Classic

If you hit the escape key in the Import dialog, the dialog is exited and all organization is lost. The expected behavior would be to exit Loupe View and return to Grid View (staying within the Import function) as happens in the Library Module. I have muscle memory for this behavior and I keep destroying my organizational work within the Import dialog--(ie: checkmark selections for "Include in import") Either make the behavior consistent between the modes, or add a warning that "All selections will be lost, exit anyway?" Thanks, --David Aughenbaugh

Hi everyone,I'm experiencing severe export slowdowns in the latest Lightroom Classic 15.3.1 on my Mac Studio (M1 Max, 24-core GPU, macOS Tahoe). Exporting 500 high-res RAW images to maximum quality JPEGs takes way longer than it used to, and my hardware is not being utilized properly.During the export process:•    CPU usage is pinned at nearly 100% (Full Red).•    GPU Utilization sits around 60-70%.•    GPU Render and Tiler utilization drops down to just 5%.•    ANE (Neural Engine) utilization stays at 0%.It seems like a massive I/O or processing bottleneck where the CPU is completely choked, while the GPU is just sitting idle waiting for data.What I have already tried (which only partially helped or didn't fix the underlying bug):    1.    Camera Raw GPU Config Fix: Checked the Camera Raw GPU Config.txt file and noticed crs:gpu_preferred_system="" was completely blank. Cleared the entire GPU cache folder and forced LrC to re-test the hardware.    2.    Hard Reset: Performed a full pre

Hi everyone, I recently downloaded some presets and imported them into Lightroom (using Windows), but they’re not appearing in the dropdown menu. When I try to import them again, I get a message saying “All items were already imported.” An Adobe assistant had a go at fixing the issue, but had to go away to look into it further. I thought I’d check in here to see if anyone else has run into the same problem and managed to sort it out. I believe he already tried opening new images, reinstalling LRC, and a few other things. Thanks in advance!

This has been happening for probably a week or two. I have it by default apply content credentials to every jpg I export - can’t hurt, right?In every single export lately, a random number of them ‘fail to apply’ and hence do not export at all. I have to keep going to the export dialog, click ‘skip’, and it will export a few more and fail to export a random number. Currently I have done this 8 times to a set of 148, and am down to one single file that it just doesn’t seem to want to apply them to ever. I assume this is a bug and I should give up on credentials until this is fixed.  Mac Mini M4 Pro, OS 26.5.2 

Bonjour,J’ai des photos en double dans un dossier et les doublons ont “ 2.RAF” ajouté à la fin du nom ([espace]2). Hélas LR me sort tous les fichiers qui se terminent par “ 2.RAF” mais aussi ceux qui se terlminent par “2.RAF” (sans l’espace)… Comment contourner ce problème ?Je suis sur MAC.Merci

I try to install lightroom classic on my laptop, but the installer continues to run till I force my computer to restart. He gives me a conflict error. I work on a MAC with Tahoe 26.5 installed

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

Les "modèles utilisateur" que j'ai créés apparaissent dans le panneau de gauche et dans l'aperçu en haut à gauche, mais ne sont pas visible dans la fenêtre principale (style de disposition : collection personnalisée) et donc, ne sont pas utilisables. De plus, le panneau de droite reste figé et ne permet pas de créer de nouveau modèles (p.ex. le sous-panneau "cellules" n'apparait pas).

When I click “Import” in the import dialog right after it opened and when not waiting until all files (and miniatures) were loaded in the import grid view, the import apparently only imports those files where the miniature/preview was loaded. 

I have upgraded to a new MacBook using MacOS Tahoe, V26.6.2 with LRC Release 15.5.1.When I look to import files from my card it does not see anything so I have to use Finder to copy files to my Mac and import from there.  Why does LRC not see the files on the card?

Version: Lightroom Classic 15.5.0.8OS: Windows 11 Pro (build 10.0.26100)GPU: NVIDIA RTX 3090, driver 32.0.16.1088 (22/07/2026)RAM: 32 GBRepro: Run Assisted Culling / auto-stack-by-similarity on a large batch of photos. Crashes reproducibly — 5 identical crashes since 2026-08-09.Crash signature: Windows Application Error log shows Lightroom.exe faulting in ntdll.dll, exception code 0xc0000374 (STATUS_HEAP_CORRUPTION), consistently at the same fault offset (0x112165) across all occurrences.Context: App log shows the last command before each crash was ag.library.stacking.generateAutoStacksBySimilarity. Lightroom's process memory usage reached 13.5–14.6 GB (41–45% of system RAM) just before crashing, suggesting a memory-handling bug in this feature on larger culling batches. 

I’ve processed multiple images in LR and try to send them to open as layers in PS ready to stack. PS wont finish importing them it locks up. This has only occurred since last week. It worked flawlessly previously.

I am a photojournalist and recently switched from a PC to a MacBook (last week). My workflow has been rock-solid for many years, and my old archive copied over to the new Mac system without any issues.My Workflow: Preview & Culling: Photo Mechanic Editing: Photoshop 27.9.1 / Adobe Camera Raw Saving: Exported/saved as DNG files Archiving: Import DNGs into Lightroom Classic 15.5.1 The Issue: For my commercial side work, I regularly apply the "Adaptive: Color" profile to my Raw files. However, since switching to the Mac, when I import these newly edited DNGs into Lightroom Classic, LrC fails to apply or read the "Adaptive: Color" profile. The images import looking completely flat.What I've Tried: I read that updating the AI settings in Lightroom might resolve this, but it did not work. Manually reapplying the Adaptive Color profile inside Lightroom does fix the image, but this is way too time-consuming and defeats the purpose of my workflow. Note: Older images processed this

this occurs both in the filmstrip as in the raster mode and in both library and develop module.I use the dutch version of LRC

SystemLightroom Classic 15.5.1 macOS 26.6.2 (build 25G83) MacBook Air, Apple M4, 24 GB memory Apple M4 GPU, 10 cores; Metal supportedSteps to reproduceMerge source images using Lightroom Classic’s Photo Merge → Panorama. Open the resulting DNG, approximately 13,000 × 4,000 pixels, in Develop. Create a mask using Select Sky. Enable the overlay and try changing the mask’s adjustment sliders.Actual resultSelect Sky appears to run, but no mask overlay is visible and adjustments have no effect.Expected resultSelect Sky creates an editable mask covering the sky.Comparative testsLinear-gradient masks work correctly on the same merged DNG. Select Sky works on the individual source images. Select Sky works in Lightroom Classic on a full-resolution TIFF version of the panorama. Photoshop’s Select Sky also succeeds on the panorama.These results suggest an issue with Select Sky processing this merged DNG, rather than a general masking failure or image dimensions alone.WorkaroundExport the merged p

This thread is for Camera Raw & Lightroom Classic feedback on the (Early Access) Content Authenticity Initiative (CAI)For the Lightroom Ecosystem feedback, click here.  The Lightroom team is dedicated to building capabilities that foster trust and transparency in the age of AI. Our latest release, as part of the Content Authenticity Initiative (https://contentauthenticity.org/), allows you to add content credentials to your work when exporting in Lightroom to ensure provenance and preserve authenticity.   New content credential capabilities are available across the Lightroom ecosystem (Lightroom, Lightroom Classic, Lightroom for mobile (iOS & Android), Lightroom for web), and Adobe Camera Raw in Early Access. When exporting a JPEG from Lightroom, you can attach your name, social media handle, and a list of edits via a digital signature.   You can find the option to apply Content Credentials while exporting a JPEG in the export panel. It is, by default, turned OFF

I am working on a photo. This is what it looks like when editing.  Then on export this is what it looks like.  I also see this in the Export Preview:  That’s a pretty big difference in noise and even some color saturation. I’ve tried many settings, can’t seem to get rid of this.  

I updated to LrC 15.5 a few hours ago.  Since then LrC has problems with video files.  The first problem I noticed was that when I tried to synchronize a folder that had two new video files.  After a couple of minutes I got the error message “An unknown error occurred while reading the video file. (2)”.  I had just completed those files with DaVinci Resolve so I went back and produced the same files again to check if DR had made an error.  When I tried again with the new files but got the same errors.  I was able to play both videos without any issue using VLC Media Player, so they seem to be OK.  I then shutdown LrC and did a backup including optimizing the catalog, and then restarted it to see if that made any difference, but same error.  Then I started looking at other videos that were already in LrC and found that when browsing them in the Library module, most of them pop up a message “There was an error working with the video”.  They will not play in LrC but work fine with VLC Med

Les métadonnées comme la légende, mots-clés, disparaissent et il est impossible de les compléter.

Using LrC 15.5.1 with CC subscription long term on a new MacBook Pro M5 running Tahoe 26.6.2.Sync generally worked with v15.5.1 previously on my M1, but since migrating to the M5 a few weeks ago not so much.I have about 50,000 photos and am trying to sync them in batches of 2000-4000 at a time. They start syncing fine and then at some point it just stop working and gets hung on a file.I'll just see the sync Local Activity in top right of LrC say it's syncing the same number of files (ie; remaining files) and hasn't changed in hours.In Lightroom Sync tab in Preferences, the same photo is listed at the top of the Sync Activity window and it hasn't changed for hours.The photos all say "Image" in the Sync Activity window of LrC and nothing lists any kind of error.I tried selecting the very top photo and applying a minor edit to see if that would "kick start" the process (the previous fix for some earlier versions of LrC) but no change.There no Sync Errors or Sync Error Album anywhere and t

So continuing the saga of importing from a cfExpress type b Card raw files from my z9. It takes about 9 hours to import roughly 4k files. I am using a reader and very fast cards for read and write speeds. Some of the events I shoot leave me with more than 10k images to import so just moving into a folder on my harddrive and then imporing is not practical as I end of with files with the same name spread over multiple cards...LR renames the file when writing to prevent this from overwriting existing images.  This slowness has persisted for several years now as I h ave been reading about this issue for quite a while. Adobe you can do better..please fix this.  

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

For all the years I have used Lightroom I have used a User Preset to Import my photos. This is pointed at the current month in my Folder Structure and creates folders in that month according to the day of the month the photos are taken. Each month I edit the preset to move the output to the next month. I have recently mover my entire Catalogue from being split between my D: Drive and my external G: Drive so the entire catalogue is on the G: Drive. The Import User Preset has gone “wrong” and I cannot find a fix. Refer the following screens. Import using User Script - everything is as it should be with a couple of days straggling to be moved back to AugustLightroom structure after Import Nothing has added to September. Going through Previous Import - Photo - Go to Folder In Library takes me here. Which is outside my Master CatalogueThen I cannot Drag any of these new folders into their correct location within the Master Catalogue.I cannot find any way of either rectifying the problem wit