Lightroom Classic

See the attached screenshot

hola, el LR en el dia de hoy no funciona? no puedo editar ninguna foto. cuando se solucionara el problema? la actualizacion se hizo hace 16 dias

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

I got the 20GB subscription. Since a long time I get warnings about it being full. I have tried everything suggested on your site. Including looking for files on the computer. Have only two photos when I check. My son previously used the other seat when I had the subscription that included Illustration.  Could it be that big files are left from that? Kindly Mikael Wester  

Hello Dears, I have a problem with synch. Last night I tried to synch with 493 photos. Most of development setting was Ok but some of ones missing and/or not correct. For example; linear mask starting point, color adjustment and crop position are different some photos.I tried remove all 492 photos in lightroom and called again. I kept original one which is modified than I tried synch but no change. Issue still there. Is there anybody to face same situation and know solution. I’m using creative cloud desktop version. Thanks in advance for your help.

Summary: Lightroom Classic throws a generic "unknown error" when importing HEVC video files tagged as hvc1, which is the default output format for DJI cameras (tested with DJI Osmo Action 6). The same file remuxed to use the hev1 codec tag imports without issues. No re-encoding is performed — the video bitstream is identical.Steps to reproduce:Record video on a DJI Osmo Action 6 (or likely any DJI camera outputting HEVC). Or use attached input file. Attempt to import the resulting .MP4 file into Lightroom Classic via File → Import LrC throws "unknown error" and fails to importWorkaround: Remux the file using ffmpeg with no quality loss:ffmpeg -i input.mp4 -c copy -tag:v hev1 -map 0:v:0 -map 0:a:0 output.mp4The resulting file (attached) imports correctly.File properties (ffprobe):Codec: HEVC / H.265 Profile: Main 10 Resolution: 3840×2160 Codec tag (original, failing): hvc1 Codec tag (remuxed, working): hev1 Color: yuv420p10le, bt709Expected behavior: Both hvc1 and hev1 are valid, spec-c

Subject: Lightroom Classic – Reproducible UI Instability and Repeated Crashes After the Latest UpdateDear Adobe Support,I am reporting a serious stability issue that started immediately after installing the latest version of Lightroom Classic.EnvironmentWindows 11Latest version of Lightroom ClassicCatalog optimizedSufficient free disk space availableLatest graphics drivers installedLightroom Classic reinstalledGPU settings reviewed and testedCamera Raw cache reviewed and increasedWindows fully updatedIssue DescriptionSince the latest Lightroom Classic update, the application has become unstable during normal editing sessions.The issues occur without using any AI-powered features such as AI Denoise, AI Masking, HDR, Super Resolution or Generative Remove.During normal work in both the Library and Develop modules, I consistently experience the following problems:The histogram in the Develop module randomly disappears and then reappears several seconds later.Interface panels load slowly or

I tried a trial subscription in the hopes this would speed my workflow. Currently I edit real estate photos, then export, then edit in Nano Banana to replace skies or create twilight images. Then I download, rename and export the finished file.I was happy to see that I can now transfer the file to Firefly, and assumed I could return the edited file to LR Classic, as in PS. But, no I still have to download, rename and export. So, the time saving is negligible and the true cost is unknown because of the annoying credit system.WILL WE BE ABLE TO directly return edits to Lightroom? 

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.

This starting a couple of weeks ago after working fine for probably the past 6? months. After opening LrC I plug in my card reader, go up to “FILE” > “IMPORT FILES AND MOVIES”.  I am not seeing my card reader in the list.  ??LrC ver 15.4.1Windows 11 

Hi Adobe Team, I’m posting this as a clear performance regression report for Lightroom Classic v15.x — specifically the Develop module image-to-image switching latency on Mac. REALLY SLOW. Please do not merge this thread into a generic “performance” megathread and then mark it as “Solved” as if nothing happened. Multiple users are reporting the same behaviour, and it deserves a proper investigation and acknowledgement (instead of being dismissed as an “NVIDIA driver” issue — this is Apple Silicon). What’s happening On Lightroom Classic v15.2, switching between photos in Develop is several times slower than in previous versions. This is not a minor “feels slower” issue — it’s a real, repeatable regression that drastically impacts professional workflows. My setup  MacBook Pro (M3 Max) macOS v26.2 Lightroom Classic v15.2 Preferences → Performance → Graphics Processor: ALL acceleration options manually enabled (not Auto)  Proof / Reproduction To remove any subjectivity, I recorded sc

When importing Leica M11 DNG files using Adobe Default (as shown in the Preferences / Presets -- Global setting) Adobe Standard is applied as the Profile instead of Adobe Color.  When I create and specify a Preset which specifically uses Adobe Color as the Profile, Adobe Standard is still applied.  If I specify to use Camera Setting, then the embedded M11 profile is correctly applied.  As a work-around,  I can indeed force the Adobe Color profile to be applied if I specify it as the Apply During Import - Development Setting (right-hand panel when importing) and select under the Defaults presets - Adobe Color + Lens or similar. [Moved to Color Management by moderator authority]

Whatever was done in the masking with the last update you need to revert it. Masking was fine but now all my photos have this horrible gray outlining around the subject. All you have to do to reproduce this is take a picture load it in Lightroom add a subject or background mask edit it slightly and there you go. Previously no matter how bad you edited a photo it would never look like this. The above picture is one edited with the new masking the white moth picture below is edited before the changes took place. This is really ruining all my photos. 

This post is applicable to Lightroom Classic. ETAs for tethered support for specific cameras are not available.   Tethered Capture is a feature of Lightroom Classic that allows the direct connection of your camera to the Lightroom desktop environment. Images are imported into your Lightroom catalog as they are captured via the connected camera. New camera support for reading the raw files is generally added quickly after a camera is released by its manufacturer.  New camera support can be verified here: https://helpx.adobe.com/camera-raw/kb/camera-raw-plug-supported-cameras.html.  Tethered support for a particular camera model normally follows a version or two after the raw file support. Adobe relies on the manufacturer’s (Nikon & Canon) SDK (Software Development Kit) to facilitate the tethering of your camera to Lightroom. The timing of the release of a manufacturer’s support via their SDK greatly affects the time to release for tethered support. In additi

Since the recent updates I have intermittently experienced a number of issues when using Lightroom Classic 15.4.1 on a Windows 11 PC (System info below):program crashed on one or two occasions; program switches from Develop to Library mode by itself;  clipping indicators show in green rather than red;  ‘Before’ image does not appear when selecting Before / After; Masking fails to find landscape features, subject or object and pop-out closes; Adaptive colour profile does not work.None of these issues were present before the update, and I tried the masking in Lightroom (desktop) without problems on an image where LR Classic failed to find the subject or landscape features. I have tried switching between ‘use graphics processor’ and ‘off’ but it does not seem to make a consistent difference - sometimes things work as expected, the next time they don’t.Lightroom Classic version: 15.4.1 [ 202606201310-b9f148a4 ]License: Creative CloudLanguage setting: enOperating system: Windows 11 - Busine

I am using an Apple studio computer.  In both the Library Module and in the film strip, when selecting a file, the next file is also selected.  When trying to scroll through the other pictures in the folder, it only scrolls between the selected two files.  This problem started after updating to the latest version of Lightroom Classic.  I can only advance by using my mouse to click the next file.  Then it will also select the file next to it.Does anyone else have this problem.  If so how did you fix it?

How do I get Lightroom to write the metadata directly into the original jpgs?In my Lightroom catalogue are two folders with images from my smartphone (Pixel 9 Pro). One contains the original jpgs plus dng raw files of some of those images. The second folder holds images edited on my phone with Snapseed. I use Lightroom to edit the keywords and filenames.If I add keywords to a Snapseed edited photo those keywords are immediately written into the jpg image but if I do the same for an original photo the keywords are stored in a xmp file. Even if I manually ask Lightroom via right click Metadata > Write Metadata to file all I get is a xmp sidecar.  

In Lightroom it is impossible to edit a photo as much as we want or need, using Masking regardless of the hardware you have.EXPLANATION Let's say you want to edit a photo with Masking to your heart's content OR because you need to change many aspect of the photo.Logic tells you "we have Masking so obviously it's possible to do masking safely and as much as I want"Reality is that in Lightroom Classic there is an "upper limit" of local edits that we can have on a photo: once we reach that "upper limit" the photo will be be reset.So in Lr it's not possible to sue Masking as much as we want/need.Usually if you have lots, lots of edits on an image other editing software struggle and get progressively slower and slower (if one has powerful hardware generally slowdowns don't happen or appear later) but in LR a photo can reach a point where it's no longer editable and it will be reset NO MATTER THE HARDWARE YOU HAVE. All Masking tools (gradients, sp

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? 

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