Connect with fellow editors in our Lr Classic community.
Recently active
I've owned an R5 not long after it released and since then I've had color profile issues with lightroom classic and my CR3 files. I've had the common issue of RAW files looking washed out using the Adobe Standard color profile so I had ended up switching to Fidelity a few years ago which helped improve the images but they still never looked quite right and I just dealt with it being that way. More recently I tried experimenting with the newer Camera matching profiles and I didn't like the way they looked either. Recently I started looking at my older images when I was using a 6D and I couldn't believe how great the colors and contrast looked in my photos. So as a test I setup both cameras and tested the 6D using the Adobe Standard profile (where it looked great with wonderful contrast, colors, and skin tones.) and the R5 using every profile available profile and none of them looked as nice as the 6D with the default Adobe Standard profile. I cou
“Lightroom can’t import this catalog because of an unexpected error” I shot a festival last weekend, did some on site editing on my laptop. Now i want to import the festival catalog to my main one. specs of the main one and the festival match, they’re both:Lightroom Classic-versie: 15.5 [ 202607291506-b8869fa7 ]Licentie: Creative CloudI can open both catalog on my computer i can optimize them, close one, open the other all without problem. So they both seem to be working. I’ve put them in the same folder. So in folder x is a folder current catalog and a folder festival catalog. But everytime i click File → import from a different catalog, i select the festival catalog and immediately i get the error “Lightroom can’t import this catalog because of an unexpected error”. Somebody who can advise me?
PHOTOSHOP OPENS AND WORKS FINE BUT LIGHTROOM CLASSIC WILL NOT OPEN
Hi, since the last update of LRC it changes the “date created” and the date “last modified” to the time of ‘now’ when I export my RAW’s to JPG’s. Before the update I had no problems, I have searched through a lot of settings and preferences, but I can not figure out what has changed. I’ve read some old posts regarding this topic, but I still don’t know what to do. Can someone please help?
Sliders for the new mask feather/edge seem quite sensitive. Was wondering if there were any keyboard shortcuts available which would allow nudging the sliders a step at a time?
Sliders for the new mask feather/edge seem quite sensitive. Keyboard shortcuts would allow nudging the sliders a step at a time?
As soon as I import, “fetching previews” is stuck. No previews show. I have tried updating, restarting the computer and the application, and going to the catalog settings- face detection was not checked/address lookup not checked / culling not checked.
Hi all. I upgraded Lightroom classic to the latest version 15.5 which is the August update and now I find that I cannot see any of my images in the libary module. Lightroom was fine before the upgrade and now I find this happening to me. I want to know if this is a bug or something else. Has anyone else experienced thins issue after upgrading to the latest version of Lightroom classic. I have enclosed a screenshot if anyone can help out a solution to this.
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
Trying to export a Video (MP4), status shows no progress at all for a long time. I have tried a 1 seconds video, its the same. I can still work on other files in the library. I have also export an image file to the same folder, while the video files is still in export process, the image files successfully exported. Below is System info Lightroom Classic version: 14.2 [ 202502071718-3869eef7 ]License: Creative CloudLanguage setting: en-THOperating system: Mac OS 15Version: 15.3.2 [24D81]Application architecture: arm64Logical processor count: 8Processor speed: NASqLite Version: 3.36.0Built-in memory: 16,384.0 MBDedicated GPU memory used by Lightroom: 273.9MB / 10,922.6MB (2%)Real memory available to Lightroom: 16,384.0 MBReal memory used by Lightroom: 1,487.5 MB (9.0%)Virtual memory used by Lightroom: 410,782.8 MBMemory cache size: 240.3MBInternal Camera Raw version: 17.2 [ 2155 ]Maximum thread count used by Camera Raw: 5Camera Raw SIMD optimization: SSE2C
I recently updated my version of Lightroom and moved to the 15.4.1. since then I have a problem of AI storage. all the modifications I do (remove with AI, denoise...) do not work or are lost when I work on another photos. I tried to follow all the steps mentioned by adobe.com, but nothing works. what should I do. the message error I get is “AI Edits Storage Issue - Lightroom has encountered an issue updating AI edits. Future AI edits may not be saved and could be lost. Please contact Adobe Customer Support for troubleshooting”.Unfortunately I can not contact anyone, apart from posting a message here.What should I do? I am a professional photographer and need LRC to work. thanks a lot for your help Emilie
I was told that “when an image is opened in LRC, sometimes Adobe automatically creates a mask” and I want to know if that is correct and if so how do I detect or search for these auto created masks?
On a Mac mini M4 Pro running macOS Tahoe 26.6, Lightroom Classic 15.3 through 15.5 consistently hangs when generating Standard Previews.Environment Hardware: Mac mini M4 Pro Operating System: macOS Tahoe 26.6 Lightroom Classic versions tested: ✅ 15.2.1 – Works correctly ❌ 15.3 – Hangs ❌ 15.3.1 – Hangs ❌ 15.4.1 – Hangs ❌ 15.5 – Hangs IssueWhen selecting photos and choosing Library → Previews → Build Standard Previews, Lightroom starts generating previews but then freezes indefinitely. The progress may stop at different points (for example 4/4, 5/68, or 100%), but it never completes.During the freeze: Lightroom remains responsive, but the preview generation never finishes. CPU usage stays around 0–5%, indicating that the process is idle rather than actively rendering. Troubleshooting PerformedThe following steps did not resolve the issue: Disabled GPU acceleration. Deleted the preview cache (Previews.lrdata). Optimized the catalog. Tested multiple cata
The Book Module currently only supports “Standard Layflat” which is Blurbs “Mohawk proPhoto Pearl”. I want to do a book with “Mohawk Superfine Eggshell” which is a matte paper. I know I could order a book with the Pearl and then reorder it with matte but that’s several hundred dollars I don’t need to spend. The workaround isn’t the easiest way either. Could you just add the paper type to the list?
Letters in texts added in books in Book module are rotated in LrC 15.3. The rotation seems to happen per line as displayed (not per carriage return). Switching back to 15.2.1 put the letters correctly again, and upgrading to 15.3 rotates the letters.Attached two screenshots of the same page in a book in 15.2.1 and 15.3.15.2.115.3The letters are also rotated for a new book created in 15.3.
Lightroom Classic Bug ReportTitleLightroom Classic reports "The file appears to be unsupported or damaged" for valid Lightroom-generated HDR DNG files. Product Adobe Lightroom Classic 15.4.1 macOS 15.7.x (Apple Silicon) SummaryLightroom Classic reports that certain HDR DNG files are unsupported or damaged.However: Adobe Camera Raw opens and edits the files without any problems. Adobe Photoshop opens the files without any problems. Adobe DNG SDK Validator validates the files successfully. Lightroom Classic itself reports the files as invalid ("Validate DNG"). The same behaviour occurs in a brand-new Lightroom catalog and also with backup copies of the same files.Steps to Reproduce Open Lightroom Classic 15.4.1. Import or open the affected HDR DNG. Lightroom reports: The file appears to be unsupported or damaged.The file also cannot be imported into a brand-new catalog.Expected ResultThe HDR DNG should open normally, since: it is a Lightroom-generated HDR DNG, it validates
when i try to open lightroom it says that there is a problem and it will take a moment to fix it. then after a few seconds it says there is an unexpected error opening catalog.
Not as much of a question, but more a critical remark. Recently I noted that some new features in the latest Camera Raw update were not available in Lightroom Classic. Specifically I mention some masking features like "Depth Range" and the "Feather" and "Edge" options in the "Sky" mask. Earlier on we had "Denoise" in Camera Raw not needing to create a separate DNG file, when Lightroom Classic's Denoise resulted in an extra large additional DNG file.This is very inconvenient. To use these (very useful!) features, I now have to open a raw file as a smart object in Photoshop to continue with raw editing and save the result as a very large psb file. Later when continuing with the edit, I have to reopen the psb file from Lightroom Classic.I hope it is not Adobe's policy to continue with supporting new features in Camera Raw first and only later in Lightroom Classic, I find it cumbersome and annoying when Lightroom Classic lags with feature updates, complicating the workflow and resulting in
Is anyone else having issues with the copy/paste settings? I’ve tried to use Lightroom classic, and the regular light room, and they are both having the same issue. I have a photo that was taken literally 2 seconds apart, same exact lighting and everything, when I copy my settings, which I make sure I copy EVERYTHING, then paste it onto the photo that’s literally almost identical, it turns out look completely different. I know I’m not crazy because I did compare the settings side by side from original photo and second photo, and some of the adjustments didn’t match, and the mask also weren’t the same, so it literally changing up some of the edits by itself. This drives me nutssss, there’s noooo way I can edit each photo one by one… any one have this problem or a solution for this!!?
I am getting worried and pretty desperate. I got a Mac M4 and downloaded lightroom and transfered by catalog on to the M4. My lightroom clasic is working insanely slowly so so that it take hours to move a few pictres from one folder to the next, deleting a file takes minutes, and moving from one file to another also takes along time. I tried to move a folder from one external hardrive toanother and I could not do it (3000 pictres). On my old compter I could do it all and fast (that compter was 12 years old). I do not know where the problem is. Please help me. NB: I had Adobe on the line for two hours and the staff could not come with solutions. The second level assistance was reqested but after more than a week, I have still not received a call. [Moved from ‘Bugs’ to ‘Discussions’ by moderator, according to forum rules.]
Es kann doch nicht sein, dass ich ständig den selben Fehler habe und ich mit grossem Aufwand Foto für Foto neu generieren muss, nur damit es dann eine Woch funktioniert und wieder kommt.Findet bitte schnell eine Lösung. Das erwarte ich von Adobe, der sich selbst als die Nummer 1 in der Bildbearbeitung präsentiert.Es gibt sonst mittlerweilen viele alternative Anbieter auf dem Markt und ich muss mir ein Wechsel überlegen...
Lightroom Classic 15.4.1 on Windows: 1–2 second UI stalls when selecting photos — WPR trace points to MFC/Win32 window-handle processing Hello, I am investigating a persistent Lightroom Classic performance problem on Windows. Selecting a different image can freeze the entire Lightroom interface for approximately 1–2 seconds. This does not appear to be caused by RAW decoding, storage performance, the catalog, previews, GPU acceleration, plug-ins, or monitor refresh technology. Windows Performance Recorder traces consistently point to Lightroom’s main UI thread spending substantial CPU time in MFC and Win32 window-handle processing. ## System configuration - Lightroom Classic 15.4.1 Build: 202606201310-b9f148a4 - Camera Raw 18.4 - Windows 11 Business, build 26200.8737 - AMD Ryzen 9 5950X, 16 cores / 32 threads - 32 GB RAM - NVIDIA GeForce RTX 2080 Ti, 11 GB VRAM - NVIDIA driver 591.86 - Catalog stored on an NVMe SSD - 12 MP RAW files stored on another NVMe SSD - Approxima
I had to create a new catalog and reimport all my photos. By importing from a previous catalog I got my collections back but not the publishing services like JF Flickr and Adobe stock. I have reinstalled JF Flickr, reauthorized in Flickr, without results. Can anyone help?
I'm a relatively newbie to Lightroom and I think it is fantastic. It does occur to me that pros who have been using Lightroom for a while understand all the issues about selections, settings, copying, pasting, synchronising etc etc. Like many things in life the people who do things almost as second nature forget what it was like to be a beginner. The one thing that has surprised me about lightroom is that I cannot find a way of indicating "I am happy with this - I just want to lock it to ensure I don't damage, amend or delete it" through my own incompetence.
Seit dem Update von Lightroom Classic auf Windows 11 wird beim KI-Entrauschen keine neue -Verbessert-NR.dng mehr im Ordner erstellt. Der Entrauschungsvorgang läuft scheinbar durch, aber das Ergebnis wird nicht persistent gespeichert. Beim anschließenden HDR-Zusammenfügen werden wieder die ursprünglichen RAW-Daten verwendet, wodurch das Rauschen zurückkehrt. Früher funktionierte der Workflow korrekt: RAW entrauschen → neue DNG-Dateien entstehen → HDR aus den neuen DNGs erzeugen. Getestet mit DNG- und TIFF-Export, Neuimport der RAWs und erneutem Laden; das Verhalten bleibt unverändert.
Remix with Firefly Community Gallery
Thousands of free creations to fall in love with and remix in Firefly.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.