Lightroom Classic

Post-processing an anamorphic image (e.g. 1.33x squeeze) currently requires extra steps outside of Lightroom Classic like Camera Raw (I don’t have) or exiftool in Terminal. Please add to Lightroom Classic natively. It’s just a metadata change.

I’ve had this problem for awhile now and haven’t been able to find a solution.  On the import tab when attempting to import pictures it takes Lightroom classic forever to generate the thumbnails. I’m not talking about the previews that get built based on my choice during the import. I talking about the grid view where you can select which files to actually import.  I just tried on a sample of 280 pictures and it took the better part of 3 or 4 minutes to generate the thumbnails. Which is about as long as it takes to do the actual import AND generate 1:1 previews…  I’m shooting primarily a fujifilm XT5 with and only shoot .RAFLightroom version 13-3 (but has been happening for the better part of the last 2 years) I’ve got a very good homebuilt computer Intel Core i7-13700k (liquid cooled)RTX 4070 (GPU acceleration turned on)64 gigs of RAMHarddrive in question is a 30% full M.2 NVME SSD I previously bought a high end card reader and usb 3.0 cabling hoping this would help. Which is doesn’t.

When I open any new catalog for the first time, I can’t see any of the previews. Once I close Lightroom and re-open it, I can see everything. I’m running Tahoe on a 2021 iMac. I believe it’s possible that the timing of this bug coincided with my update to Tahoe a few months ago, but I can’t remember for sure.More details:-My previews files are not corrupted.-Deleting and rebuilding previews does not work.-Clearing the preview cache does not work. I-I’m not running any virus software.If you haven’t received many reports about this bug yet, it’s because closing and re-opening Lightroom does solve the problem. The majority of photographers only work with one catalog for many months at a time, so restarting Lightroom would have resolved the issue in their eyes. But for those of us who are dealing with 15+ new catalogs every week (which, granted, is the minority of users), this bug is showing up very often. My best guess is that it’s related to the way that Lightroom is interacting with a n

I installed the latest update a few days ago.  This is for Lightroom Classic 15. Ever since that time, when I try to read metadata from files, it never completes. I can highlight 5 images at a time and successfully get it to complete, but if over 6 images, it starts and never completes.  

There are some nice predesigned borders, but you cannot adjust the size or the position. Could that be made possible? 

When searching my library I often use the metadata KEYWORD drop-down.  Instead of having to scroll through hundreds of keywords, it would be super helpful to have a text box into which I could type the keyword instead of scrolling.  Also, as an added bonus - have the feature begin preloading options from the list as the typing progresses. 

Hello, the keywords panel is very very long in my case. Can i sort the keywords panel so that all keywords in use on selected pics or folders appear on top - not strictly alphabetical, but sorted by usage ? (I have the newest LR Classic on Windows.) I understand that i could remove folders and then delete unused keywords from the list. But i don't want to remove folders - i just want the "Keywords" panel to focus on those keywords that are within the files currently selected or displayed, not equally showing keywords for files not under consideration at the moment. I also understand that i could delete or add keywords in the "Keywording"-panel, but that is sometimes tricky especially when deleting a keyword that has accidentally been used on 200 of 300 files. (I know how to do that, but i don't like the procedure.) So i want to sort the "Keywords" panel by keywords in use - can do? Thanks!

Release 14.3.1  In attempting to create a new top level keyword. Results in creation of a sub keyword of an existing keyword. 

I created nested Keywords without any problems but tonight I can't created keywords.   I creted the following keywords: WHO, WHERE and WHAT.  I had to create the WHAT keyword inside another keyword and then drag and dropped where I wanted.  The "+" on the Keyword List tab doesn't seem to be working anymore.  I tried adding the following keyword, 0 GENRES PORTFOLIO as the top level of nested series.  When I click ok it never appears in the list and it gives no errors.  One fix said to delete the helper.irda files which I did,  but it did not resolve the problem.  Should I reinstall Ligthroom Classic?  That's what I use.

I have a keyword of Animals and for some reason in the drop down list of keywords some other keywords have become sub-items of the Animals keyword.  I would like to move the out from under Animals so they are at a higher level and be their own keywords.  How can I do this and what do you think may have caused this.  I use commas to seperate my keywords when I specify multiple keywords in the input box.  Thanks!  I am on Windows 11 computer.

Environment: Lightroom Classic 15.6, macOSSteps to reproduce:1. Create a new collection containing photos never synced before (ordinary RAW/.CR3 files).2. Enable sync on that collection.3. Wait for sync to progress: most photos sync successfully, but a small subset (roughly 5-10% of the batch) gets stuck indefinitely.4. No error message appears anywhere (not in Lightroom Classic, not on Lightroom Web "Sync Issues").5. Create a second, separate collection containing only the stuck photos, and sync again: the exact same files get stuck again.Example: synced a collection of 65 RAW photos, 58 synced successfully (confirmed on Lightroom mobile), 7 specific photos got stuck. Re-tested those same 7 files alone in a new collection: same 7 files stuck again.Investigation done on the stuck files, no common factor found: different camera bodies, different focal lengths, same color label/treatment/develop status as the successfully synced photos, standard file names (no special characters), normal

Latest Lightroom Classic and Windows 11 as of 20260905.When browsing Folders using the Library module, LC crashes without warning, no error message, nothing.Here is the Windows Event Log:Log Name:      ApplicationSource:        Application ErrorDate:          2026-09-05 2:26:16 PMEvent ID:      1000Task Category: Application Crashing EventsLevel:         ErrorKeywords:      User:          DESKTOP-298A3BF\stephComputer:      DESKTOP-298A3BFDescription:Faulting application name: Lightroom.exe, version: 15.5.1.1, time stamp: 0x6a7da27aFaulting module name: ntdll.dll, version: 10.0.26100.9278, time stamp: 0x7e1f2ca9Exception code: 0xc0000374Fault offset: 0x0000000000117eb5Faulting process id: 0x3504Faulting application start time: 0x1DD3D63BFCBCF43Faulting application path: C:\Program Files\Adobe\Adobe Lightroom Classic\Lightroom.exeFaulting module path: C:\WINDOWS\SYSTEM32\ntdll.dllReport Id: da4f7b47-0fc7-46cf-9173-4338c02846faFaulting package full name: Faulting package-relative applica

trying to op /  download LRC  and it just opens up like a flash and turns off. I have a desktop 

I’m using the latest versions of Lightroom Classic (15.6) and Photoshop on Windows 11 Professional. When I transfer Canon RAW photos (CR3) from Lightroom to Photoshop for focus stacking (via “Open as Layers…”), Photoshop regularly freezes and becomes unresponsive. It can only be terminated via Task Manager. Only in rare cases does it work as usual. The problem also occurred in previous versions, but more sporadically. In my old version, which was still running on Windows 10 (until July), this problem never occurred.It appears to be a scripting issue that will hopefully be resolved in LR16. In the long run, to avoid such problems, it would make sense to perform focus stacking directly in LR anyway. System:Prozessor    Intel(R) Core(TM) Ultra 9 285K, 3700 MHz, 24 Kern(e), 24 logische(r) Prozessor(en)BaseBoard-Produkt    ProArt Z890-CREATOR WIFIAdapterbeschreibung    NVIDIA GeForce RTX 5070 TiMemory 64GB 

Lightroom blur Problem please solve it

How do we get the recommended presets working on Lightroom classic for desktop? I heard this is only available for Lightroom, but I don't know anybody who uses that particular version. Please make them available for both versions.

I want to purchase Lightroom Classic for personal use. It says 2 devices limit. Is that I can only download it on 2 devices or I can just have 2 logged in at the same time? Can we put the program on my daughter's school laptop, her desktop and my computer?

Image taken on web for exemple.Heavy banding issues with LED lighting and stage photography (concerts, dance...)High sensor read-out speed can help but not every time, except with global sensors (only Sony has one with a9 III)So, AI features would be a great option and solution for many, many photographers of stage, concerts, dance, event...

In Photoshop gibt es eine automatisierte Entfernung von Drähten, Stromleitungen. Diese wäre sehr hilfreich in Lightroom Classic. Wäre toll wenn die Funktion auch Strommasten entfernen würde.

Lightroom Classic fullscreen bug on MacBook Pro with notch (macOS Golden Gate)I'm having an issue with Lightroom Classic on my MacBook Pro, running the latest version of both Lightroom Classic and macOS Golden Gate.When viewing a photo in fullscreen mode, Lightroom is supposed to keep the image below the MacBook's notch, leaving a black area at the top of the screen. This used to work perfectly.However, something has changed. When I press L to activate Lights Out, the image gets squeezed horizontally, and the entire fullscreen layout seems to resize incorrectly. The image looks squashed rather than maintaining its proper aspect ratio. Toggling Lights Out off doesn't fix it.I want to keep the notch hidden, so disabling the macOS "Scale to fit below built-in camera" option isn't an ideal workaround.I've seen reports of similar behavior in older versions of Lightroom, but I'm wondering whether anyone else is experiencing this on the latest macOS and Lightroom Classic versions.Has anyone f

I am making a photobook using double-sided panoramic paper, and need to leave a blank page- whats the best /easiest way to achieve this? Each sheet will be folded and the whole case-bound.

I recently come across the following Issue:   I have a bunch of jpg files I have post-processed in Photoshop that I want to add geo locations to using the Lightroom Classic map module. After adding the locations I mark all images and do right click - metadata - save metadata to file. For some jpg files the data is written into the jpg file (desired behavior and how I know it from LR Classic for the past 6 years), while for others LR creates a seperate xml file (same location same name as the jpg) containing all metadata including the location.   Since this is a recent thing for me I suspected LR 14 to be the issue so I downgraded back to 13 but the issue persists. I already cleared out my complete LR catalog and only importet a hand full of jpg files to test but the issues persists. The issue can be reproduced, it is always the same jpgs causing the issue. When I open one of the not functioning jpg files in Photoshop and save it again in a new location the issue persists. Whe

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