Lightroom Classic

LrC 15.4.1. MacOS 15.6.2  When LrC is opened for a longer period of time the upper tool bar locks up. I can't hide LrC or access any other tools. I've had to force quit LrC a few times.

In the Send Book to Blurb function first the pages are rendered. Thereafter the upload takes place, during that second part the upload is very often stopped with this pop-up:Error appearing many timesThe pop-up shows very often, like dozens of time (100+ page book, 300+ images). The interval between messages does not seem to be fixed.This is the behavior of machine network while sending (between the errors):Data sent while continuingUnknown if this is normal…The progress bar does continue to go forward, so progress seems to happen between the errors. However, as too many errors are given no full book is uploaded currently.The screenshot is using a cable connection (from machine to router), using WIFI gives the same.This is behavior is observed in the LrC 15.3 and 15.2.1 and previously in early 2025 (LrC version unknown).Machine is Microsoft Surface, current version of Windows, ARM64; further info in attached file.

Lightroom Classic 15.4.1 on Windows 11 desktop PC with HDR display enabled. In Develop mode, DNG image is adjusted using AI Sky Mask to adjust hue of sky. Develop renders correctly and the exported image renders correctly. However Library Loupe and Library Full Screen regenerate a preview with a green fringe or halo in the sky along the sky/land boundary. When switching to Library you can observe Library displaying the previous preview, then the correct Develop render, then replacing it with the incorrect regenerated preview. Reproducible on a fresh HDR merge and on separate DNG files. The bug appears to be related to the setting on the exposure slider in masking, appearing with higher exposures and disappearing with lower exposures.

Problem: Lightroom Classic catalog backup fails every time, consistently at the final step — "Katalogsicherung wird komprimiert" (compressing the catalog backup). Error shown: "Lightroom konnte den Katalog '2026_07_LightroomFull-v14' nicht sichern" with generic advice to check folder permissions/disk space.System:Lightroom Classic 15.4.1 [202606201310-b9f148a4], Creative Cloud license macOS 26.5.2 (25F84), Apple M2 Max, 32GB RAM, arm64 Catalog:  (~4.2GB), on an internal HFS+ (Journaled) volume connected via PCIe Backup target tested:  (on boot APFS volume) — also failed with 2 other previously tried destination foldersAlready ruled out:Destination folder permissions/ownership — correct, and writable (verified via Terminal) Free disk space — 213GB free on boot volume, 4.2TB free on catalog volume macOS Full Disk Access — granted to Lightroom Classic Filesystem corruption — Disk Utility First Aid on the catalog volume: clean, exit code 0 Catalog SQLite structural integrity — PRAGMA integ

In Lightroom 15.4.1:Open Image with blue sky Generate a virtual copy Set copy to B&W in Basic panel. Sky retains a blue tint. Adjusting blue tones in B&W mix panel deepens or lightens tint but retains the blue colour. This also happens when using B&W preset such as InfraredNOTE: In further testing, I have only found this behaviour in two images which have been edited in Photoshop and saved at TIFF. 

some of these files date back several years.  How do I best manage them and how do I free up disc space?

When opening it shows a box.  “Lightroom has encountered  issue updating AI edits.  Future AI edits may not be saved and could be lost.  Please contact Adobe customer support for trouble shooting.click open recent under catelog the only catelog that comes up is LR catalog.Ircat. Under Manage Catalog, it shows LR catalog.Ircat is located under One Drive.  That is not one of my catalogs and I do not use One Drive.  It gives a choice to Remove All which I haven’t done yet.

I am trying to make a print to fit the dimensions of a mat I have already cut. In Page Setup I set the paper for 13 x 19 Landscape, and set the Cell Size in Print module at 9.3 x 13.32, which is slightly larger than the mat opening. However the finished print measures slightly under 9 x 13. I am printing to an Epson ET-8550 printer. I have been printing lots of 7.5” x 10” prints on 8.5 x 11 paper and they come out the exact dimension as expected.

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

Hi there, I’ve been struggling with a recurring bug in Lightroom Classic (v14.3.1) related to the AI-based Remove tool and the “Update AI Settings” prompt. Here’s what’s happening: I’ll use the Remove tool on an image and allow it to finish processing.I’ll then move to another image and continue editing.When I return to the original image a few minutes later, the removed object has reappeared.A triangle with an exclamation point shows up, prompting me to “Update AI Settings” — even though I’ve already done this previously.This cycle keeps repeating, and edits don’t stick.     What I’ve tried (and confirmed):  I’m running Lightroom Classic v14.3.1 on Windows 11.GPU settings are set to “Auto”, but I also tried manually enabling full GPU acceleration.I’ve restarted Lightroom, reinstalled Lightroom, and even paused cloud syncing.I’ve waited for the AI edit to finish before moving to another image.I cleared the masking cache by deleting the Helpe

Hello, Community.   I'm a photography hobbyist who chases the aurora. Novice-level LRC user. Mostly illiterate when it comes to the details of monitors/sRGB color space.  You guys will be lightyears ahead of me in technical acumen, but I’m hoping you will be able to point me to on-line resources or provide “Dummies” level info to help me understand the image discrepancy I find between the RAW image and what I import into LRC.  Currently working on an older MAC (newer more robust MAC sitting here waiting to be unpacked).   When I started post-processing RAW image from my 2026 aurora trip I immediately noticed a SIGNIFICANT difference between the intensity of the RAW image colors (MAC Preview app) compared to the image imported into LRC Develop module. (both displayed on 5-6 year-old DELL monitor, with same discrepancy seen on husband’s newer DELL monitor)   LRC import images are 1:1.   Is it my monitor settings?  Any information or resources for a novice LRC user to help me understand w

Meine KI preset Maske wird teilweise nicht übernommen. Im Raster Entwickeln ist mein bearbeitetes Bild wie ich es haben möchte - sobald ich in die Bibliothek umschalte ist die Maske weg und somit der Bildlook ganz anders. Auch beim export ist die Maske nicht drauf!

In my Lightroom Classic (15.4.1), the icon for each layer mask located next to the mask name has disappeared. Previously, each mask had an eye icon and I could click on the eye which would turn off the mask visibility and change the eye icon to an eye with a slash through it.  Now there is just a dark gray area with no eye. The only way to turn a mask on or off is to control click on the mask and select hide which is clunky. Is there a hidden setting that will restore the eye icon? Thanks

Lightroom 15.4.1 on Windows.As GPU I have an NVIDIA 4070 with 12GB of VRAM, latest studio driver  6.10.62.In the Graphic tab of the NVIDIA App I can choose to "Optimize" LrC, but if I do then in LrC settings under Performance tab it sets automatically CUSTOM under "Use GPU", option "GPU for export" is disabled and greyed out and it says I have only "Partial graphic acceleration".If I manually force AUTO under "Use GPU" than when i go back to NVIDIA App it says LrC is not optimized, and if I select OPTMIZE again than under LrC Performance it goes back to partial accelleration. Any idea?

Subject: Lightroom Classic creates duplicate NEF files (-2) when importing from Nikon Z8 via USB with dual-card backupProduct: Adobe Lightroom Classic 15.4.1Operating system: macOSCamera: Nikon Z8Issue:When importing photos directly from a Nikon Z8 connected via USB-C, Lightroom Classic creates duplicate NEF files during import.The camera is configured to record identical NEF files simultaneously to both the CFexpress Type B card and the SD card (backup mode).Although Lightroom displays only one import source (the camera), each imported image is copied twice into the destination folder:DSC_1234.NEF DSC_1234-2.NEFThe two files are bit-for-bit identical (same file size in bytes).Important observations:The duplicate files do not exist on either memory card. The camera itself shows only one copy on each card. The “-2” filename appears only after Lightroom imports the files. “Make a Second Copy To” is disabled. No cloud synchronization or third-party sync software is running. Import method

A "Photo Merge - HDR" menüt használva, 3 képet kijelölve, az összeszerkesztés nem fejeződik be. Ez a hiba a korábbi verziókban is előfordult, de nagyon ritkán. Most a legfrissebb verzióban, nagyon gyakori. Csak a programból való kilépés és újraindítás után tudom folytatni, és látom, hogy elkészült az összeszerkesztett kép, de továbbra is látva marad a 3.db. kép amiből összeszerkesztődött.

AI Denoise creates rectangular artifacts in smooth sky areas.The artifacts are not limited to the Lightroom preview. They are permanently written into the generated DNG and remain visible in Photoshop and exported JPEG files.The artifacts become much easier to see after increasing the Dehaze slider, but they are already present in the DNG.I reproduced the issue with:- Canon EOS R6 Mark II (CR3)- Canon EOS R5 Mark II (CR3)- iPhone 17 Pro Max (DNG)The issue occurs in both Lightroom Classic and Lightroom Desktop.Disabling GPU acceleration does not change the result.SystemLightroom Classic 15.4.1Camera Raw 18.4Lightroom Desktop 9.4.1macOS Tahoe 26.5.2MacBook Pro 16"Apple M4 Pro48 GB RAMSteps to reproduce1. Open a RAW/DNG with a smooth blue sky.2. Run AI Denoise with default settings.3. Open the generated DNG.4. Increase Dehaze to reveal the artifact more clearly.5. Export as JPEG.6. Open the DNG or JPEG in Photoshop.The rectangular artifacts remain visible.

Lightroom Classic 14.1 1nd 14.1.1MacOS 15.2 - Import images- Select image(s)- Press a number key to apply a star raing- The UI (Library module) does not update to show the stars below the thumbnails The ratings seem to be applied as I can filter based on the newly applied ratings even though she starts do not appear. The stars will appear after closing and reopening Lightroom

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