Questions

Adobe has gone all in with AI in Lightroom.  This make a lot of sense.  However, Adobe has been sloppy in keeping clear delineation between what counts as an AI modification and has made it near impossible to confidently and quickly identify files with AI modifications.    For example: Lightroom currently identifies NON AI Heal as an AI update, making it impossible to separate files with Heal vs Generative Remove.    Another example; Lightroom provides a filter “Has AI”, except it traps everything that remotely appears to be touched by AI.  AI Masks are an example.  Yes the Mask is generated by AI, but this in no way changes the  pixels,  and is not an AI change to the image.    Please cleanup your AI filtering and identification logic so it is clear and discoverable which images have AI tools used verses which images have AI edits.    

I have very clear picture, One person in the image and white background. Person is not wearing  any white cloths but still mask is unable to detect person to edit it.

Lightroom sync pending. Won’t sync. Won’t indicate which files are the problem. 

I have a LR catalog based on COLLECTIONS and need to migrate them to a FOLDER based catalog.I've been using that catalog for years (back when LR worked just like that) and I don't want to lose all the keywords I've assigned to my pictures.The collections I use exactly replicate the folder structure of my external HD.Is there a way to do it?Thanks!!

Problem summary:Lightroom Classic 15.5.1 consistently disables GPU acceleration on my HP OmniBook Ultra Flip with Intel Arc 140V graphics, even though Photoshop / Adobe Camera Raw 18.6 on the exact same machine detects the same GPU and reports full acceleration.This causes Lightroom Classic AI Denoise / Super Resolution to fall back heavily to CPU and run dramatically slower.System:HP OmniBook Ultra Flip Intel Core Ultra 9 288V Intel Arc 140V GPU 32 GB RAM Windows 11 Home Windows build: 11.0.26200 Intel graphics driver tested: 32.0.101.8974 32.0.101.8993 32.0.101.9030 Current driver: 32.0.101.9030Lightroom Classic:Lightroom Classic 15.5.1 Internal Camera Raw: 18.5.1 [2687]Lightroom Classic System Info reports: Graphics Processor Info:Init State: GPU disconnectedUser Preference: AutoGPU for Preview Generation: OffGL_RENDERER: Intel(R) Arc(TM) 140V GPU (16GB)GL_VERSION: 4.6.0 - Build 32.0.101.9030GPUDeviceEnabled: falseOGLEnabled: trueLightroom also reports: Dedicated GPU memory used

I am a longtime user of Lightroom Classic. Historically when my main image drive approaches FULL, I buy a pair of larger external drives.One for images the second for backup. Currently the drives are 40 TB containing 200,000+ images. It has become financially difficult to buy 2 drives significantly larger than 40TB. Is it possible to "daisy chain" drives so that new images import into the new empty drive? For instance, can I add 2new 40TB drives, in effect making each 80TB?

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

Hi, my LrC has been failing to complete Denoise on photos this month, and I am looking for solutions. It’s been a great tool for years, and I am unsure where the problem stems from.When I click the Denoise button in Develop module it seems to start working like it used to, but when the pop-up window is gone the button stays unticked even if I press it (it just goes back unticked immediately)  The system info from LrC Lightroom Classic version: 14.5.2 [ 202601141538-bad3ef80 ]License: Creative CloudLanguage setting: en-AUOperating system: Mac OS 13Version: 13.7.8 [22H730]Application architecture: x64Logical processor count: 8Processor speed: 2.8GHzSqLite Version: 3.36.0Power Source: Plugged In, 58%, ChargingBuilt-in memory: 16,384.0 MBDedicated GPU memory used by Lightroom: 758.1MB / 2,048.0MB (37%)Real memory available to Lightroom: 16,384.0 MBReal memory used by Lightroom: 1,280.5 MB (7.8%)Virtual memory used by Lightroom: 42,896.3 MBMemory cache size: 192.8MBInternal Camera Raw versi

Every time I open Lightroom Classic v15.6 I am missing Develop, Photo, Settings, Tools and View unless I click somewhere on the screen. They will then appear but I have to do that a few times before they actually stay visible. Never had this issue previously and it is mighty irritating when I am trying to edit photos. I am working on a Mac, Apple M4 chip, version 27.0.1.

Utilizo las aplicaciones del plan de fotografía, Photoshop, Lightroom y Lightroom Classic.He revisado en Creative Cloud Desktop los archivos existentes en la nube y actualmente solo hay un archivo. En la papelera de archivos eliminados no hay nada.¿Donde se están usando los 19.7 GB ocupados?¿Hay alguna forma de recuperar el funcionamiento de la nube con un espacio que me permita seguir utilizando la sincronización en la nube?.

Adobe Lightroom Classic creates (and rebuilds when deleted) a 100GB cache with ≥10,000 files, many of them >100MB in size, containing Apple ML files, at  /Users/ [username] /Library/Caches/com.adobe.LightroomClassicCC7/com.apple.e5rt.e5bundlecache/, even without using ML-based features or any user interaction. When the user deletes this cache; it’s immediately rebuilt when starting Lightroom. This only seems to happen with one large catalog.When I contacted Adobe support about this, they told me that I only have a “basic” Creative Cloud subscription and should just “buy more storage” (!). Absolutely unbelievable and obviously not helping.Lightroom Classic Version: 15.6 (current)OS Version: macOS 27.0.1 (current) on a 2021 M1 iMac (but the issue was already present in 26.*)# Expected resultI have a mid-size Lightroom catalogue covering an archive with about 60,000 photos (170 GB). Both this catalogue and my images are on an external SSD. The Lightroom catalogue itself is about 700 MB

when trying to use presets I'm getting the error saying some AI models are downloading please try again later.   This is making the program unusable. 

It is 2026 and Smart Previews for Lightroom still have the same resolution of 2560px on the long side. So they’ve stayed the same since the introduction of Lightroom 5 in 2013.I’d argue it's time to increase the resolution to at least 4K. Our monitors got bigger and our hard drives and bandwidth did too.I know it would add some trouble for Adobe as the smart Previews are also used to sync between devices and on the cloud, but those of us who use them in a laptop workflow should at least have an option to choose a higher resolution for offline usage.What do you guys think?

Using Lightroom Classics on Mac Book Air (Golden Gate 27) my photos are stuck syncing and any photos imported to Lightroom aren't showing on my iPad. I've deleted the sync errors. What can I do to sync my photos?

Since upgrading to Lightroom Classic 15.6, I have been experiencing a persistent problem with metadata display. The Metadata and Keywording panels in the Library module become blank, the metadata loading indicator keeps spinning, and the Loupe Info overlay in the Develop module no longer displays the expected information.Closing Lightroom Classic and deleting the catalog's `Helper.lrdata`, `Previews.lrdata`, and `Sync.lrdata` folders temporarily resolves the issue. Lightroom recreates these folders when it starts again, and metadata initially displays correctly. However, after approximately 10 minutes of normal use, the problem returns.I have reinstalled Lightroom Classic on Windows 11 and reset the application preferences, but neither action has resolved the issue. I have also tested with GPU acceleration disabled and with new catalogs, but the problem persists.The issue makes it difficult to work with and organize my photo library, as essential metadata and keywords become unavailabl

Hi all!  I want to import a couple of presets, but 8 of the 12 don’t show in Lightroom. When I try to re-import, I get the message they’ve already been imported.  I've looked through every preset folder, its not a profile preset, they are all XMP, checked show partially visible presets is clicked, and countless other things and they just are not showing up. I have synchronizes my profile, there are no incorrect characters in the names, checked display partially compatible development presets. Is it possible that the presets are ‘old’? I am out of options...

Here is a nesting “App” I created with Claude AI: (Replace .txt with .html)   <!DOCTYPE html><html lang="en"><head><meta charset="UTF-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"><title>Fine-Art Print Nesting Planner</title><style>@import url('https://fonts.googleapis.com/css2?family=DM+Mono:wght@400;500&family=DM+Sans:wght@300;400;500;600&display=swap');:root {  --ink:#1a1a18;--paper:#f7f5f0;--warm:#fdfcf8;--border:#ddd9d0;  --accent:#2c5f2e;--accent-light:#e8f0e8;--accent-mid:#4a8c4d;  --warn:#8b4513;--warn-light:#fdf3e8;--danger:#991b1b;--danger-light:#fee2e2;  --muted:#888880;--mono:'DM Mono',monospace;--sans:'DM Sans',sans-serif;}*{box-sizing:border-box;margin:0;padding:0;}body{font-family:var(--sans);background:var(--paper);color:var(--ink);min-height:100vh;font-size:13px;line-height:1.5;}.header{background:var(--ink);color:var(--paper);padding:1.25rem 2rem;display:flex;align-items:baseline;gap:1r

I want to buy Lightroom 1 TB for my Slovak VAT-registered company. Checkout only asks for first and last name. How can I add my company's legal name, billing address and VAT ID to receive a correct company invoice?

my catalog is a complete mess. I’d like to start a new version of Lightroom, and I don’t mind losing any edits. Most of my photos are in my iOS library and in my picture folder. so I would like to start a new clean version of Lightroom using smart previews and not uploading photos to the cloud.I might add that I’m 81 and my brain is not what it used to be. I use Lightroom and photoshop mainly to correct very old b&w photos as well a recent iPhone photos.  So I am not a complete beginner!

I cannot open Lightroom Classic or even uninstall it ! Windows 11 system? 

Dear Adobe Team,I am writing to request the addition of Ukrainian language support to Adobe Lightroom Classic.As a paying Adobe Creative Cloud subscriber, I rely on Lightroom Classic daily for my professional photography and editing workflow. Ukraine has a vibrant and growing community of paying users, professional photographers, and visual artists. Having Lightroom Classic localized in Ukrainian would significantly improve usability and show great support for your paying customers in our region.Thank you for your time, consideration, and continued work on improving Adobe products. I hope to see Ukrainian language support included in future updates!Best regards,@romanchuk_photos

Dear Adobe Lightroom Team,I am a paying Lightroom subscriber and recently encountered a metadata problem that led me to research Lightroom's handling of EXIF and XMP capture dates.Several professionally processed JPEGs I received contained incorrect or misleading EXIF date information. Fortunately, the correct original capture date and time — including the time-zone offset — had survived in XMP metadata.In researching the issue, I found multiple discussions in Adobe's own Community documenting similar Lightroom behavior, including cases where Lightroom knows the correct capture time but fails to preserve or write EXIF DateTimeOriginal correctly in an exported JPEG. I also found instances in which Adobe representatives acknowledged related metadata problems as bugs.I understand that Lightroom legitimately creates and updates metadata associated with editing, processing and export. My concern is specifically with original capture metadata.The time at which the shutter was released is his

Feature Request: Optimize Lightroom Classic Backup Compression for AI DataI am a professional photographer in Brazil, and I would like to report a significant inefficiency in Lightroom Classic's catalog backup process.After experiencing extremely slow backups, I conducted a controlled performance test to identify the bottleneck.Test environment Software: Adobe Lightroom Classic 15.6 Operating system: Windows 11 RAM: 32 GB Primary storage: Kingston NV3 2 TB PCIe 4.0 NVMe SSD Main catalog (.lrcat): Approximately 307 MB AI data directory (.lrcat-data): 55.6 GB Final backup ZIP: 54.5 GB Measured backup performanceUsing a stopwatch, I recorded each stage of the built-in backup: Initial preparation: 2 minutes 16 seconds Additional processing: 2 minutes 42 seconds Catalog optimization: 2 minutes 44 seconds ZIP compression: 25 minutes 54 seconds Total backup time: 33 minutes 40 seconds Compression alone accounted for approximately 77% of the entire backup operation.During c

Hey there, How do I export an original unedited version of a photo I aready edited? I need something I can use and not the lightroom file and metadata I keep getting when I try to export an original. I edited these photos months ago. I don't see why this should be so difficult so any help is much appreciated.  Kevin

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