Questions

I'm looking for advanced technical assistance with a corrupted Lightroom Classic catalogue.The catalogue originally contained approximately 10,925 photographs, including extensive AI portrait edits.Lightroom's built-in repair has repeatedly failed. The resulting catalogue opens but contains only 153 photographs.I've preserved the original corrupted 127 MB catalogue and its associated .lrcat-data folder. An independent database examination confirmed that the corrupted catalogue still contains 10,925 photo records and develop-settings records.I've already attempted the standard Alt-key catalogue selection and integrity testing procedures.I'm specifically looking for assistance from someone familiar with Lightroom catalogue database recovery and Adobe's .lrcat-data AI recovery procedures.Is there an Adobe engineer or specialist who can help assess the original corrupted catalogue rather than repeating the standard repair process?

After using Face Recognition in LrC ONE time, without any LrC prompts about needing to turn it on/off, my catalog grew from around 2 GB to 50+ GB.  I have been working for MONTHS to try to figure out what was going on and why LrC was so PAINFULLY slow.  After learning how Face Recognition creates indexes and/or caches that cannot be controlled by the user, I had to rebuild a clean catalog.  Completing the clean catalog and updating the AI masks for over 20,000 images has taken me at least 3 full work days.  This has caused such a loss to my workflow and productivity over the past few months.  This is a long‑standing and extremely disruptive problem with Lightroom Classic’s Face Recognition / People View system. This issue has caused severe catalog bloat, corrupted previews, broken masks, and forced me to rebuild my catalog from scratch — something no user should have to do.Lightroom Classic’s People View generates massive amounts of hidden face‑recognition data that cannot be purged, d

Environment- Lightroom Classic [15.1]- macOS 26.4.1 (Tahoe), Apple Silicon- System Settings > Keyboard > Keyboard navigation: ON- System Settings > Accessibility > Keyboard > Full Keyboard Access: OFFSteps to reproduce1. In the Library module, select a photo and press Delete to open the "Delete photo from Lightroom catalog" dialog.2. Press Tab to move focus to "Delete from Disk" and press Space.3. Select another photo and press Delete again.Expected resultKeyboard focus is placed on the button used last time ("Delete from Disk"), so pressing Space repeats the same action. This is how it behaved on macOS Sequoia 15.7.4 with the same Lightroom Classic version and the same keyboard settings.Actual resultKeyboard focus is always placed on "Cancel". Pressing Space cancels the dialog. Return still triggers the default "Remove" button, so there is no keyboard-only way to repeat "Delete from Disk" other than pressing Cmd+D every time.Notes- The only way to get the old behavior b

Since a recent update, exporting a full wedding to JPEG fills my internal disk. This did not happen before with the same workflow.System- Lightroom Classic 15.6- macOS 26.6.2 (25G83), Apple M2 Max, 32 GB RAM- Catalog on an external drive; Camera Raw cache limit 5 GB (stays almost empty during export)- Source: 45 MP raw files (output 5331×7992 JPEG)What happens- During export, Lightroom creates temp files named `cr_sdk_XXXXXXXX_gNNNN.tmp` in `$TMPDIR` (`/private/var/folders/.../T/`).- The files are unlinked right away, so they don't show in Finder or `du`, but Lightroom keeps them open and the space is not released.- Each one is about 1.8–2 GB. `lsof +L1 -p <Lightroom PID>` showed 20 deleted-but-open cr_sdk files = 36.9 GB about one third into a ~3000-photo export.- Some are released from time to time, but overall they keep growing. Earlier today an export of the same size filled the internal disk completely.- After stopping the export, with Lightroom idle, it still held 16 delete

Running LrC 14.4 on MacOS Sequoia 15.5, with the option "Write date or time changes into proprietary raw files" enabled, LrC is automatically modifying the capture date/time in my raw files without me using Edit Capture Time. Initially noticed that all files imported since 14.4 had the file modification date/time changed to when they were imported, whereas it's always previously stayed the same as the capture time from the camera. I then noticed that some older files were also showing the raw file as having been modified after I'd been editing them. After a bit of investigation I discovered it's modifying the capture time in the raw files for some reason. I've been testing with new and old files, some taken in GMT timezone, others taken whilst BST is in effect (+1 hour). They almost all get modified on import or editing, but the ones taken during BST the time is changed back an hour, whereas the ones taken in GMT nothing changes, so the "modification" seems to just be the sam

In LRClassic 15.6 the numeric fields in Develop>Tone Curve are not always showing three digits as they should when the White point is selected. Only seeing two digits is confusing.  As shown where the white point is select and the Input should read 221 and the Output should be 255.

I tested Lightroom Classic 15.6 using Assisted Culling followed by stacking by similarity on a folder that previously triggered the crash. The workflow completed successfully with no crash.However, after processing, Lightroom retained approximately 15.15 GB working set and 39.59 GB private committed memory, with no meaningful reduction during a 15-second observation. After closing and reopening Lightroom, usage returned to 2.68 GB working set / 3.31 GB private, and the generated culling scores remained available.Automatic Assisted Culling analysis is disabled for my catalog. So, in this controlled test, 15.6 appears to fix the heap-corruption crash, but unusually high memory retention may remain after processing.

Since I updated to MacOS 14.6, printing from Lr Classic to my Epson SCP800 has beeen a nightmare. The printer driver seems to have become completely unreliable.    1. When I select a profile in Lr, the printer driver has color matching set to Epson Color Controls, and not (as it should) to Color Sync. Sometimes the driver opens with Color Sync correctly set, but then changing any other setting (eg, paper type) causes it to revert to Epson Color Controls.   2. When I make changes to the print settings (eg, changing paper type) and save a preset, the change is not present in the preset. This problem does NOT seem to occur when using the print driver from Apple Preview.   I have -- reinstalled the Epson drivers -- deleted and readded my printer -- deleted my Lr preferences (but I'm confused about this because moving the com.adobe.LightroomClassicCC7.plist file out of ~/Library/Preferences doesn't seem to change anything in my Lr setup, even if I restart my machine

I made a post yesterday asking about Lightroom Classic. I submitted it and it came back with a yellow bar saying it was being submitted for moderation.After that, I have seen nothing. I can’t even see if my post attempt still exists. My post was pointed and not complimentary, but was not nasty nor did it have swearing. So, when do we know? 

Al exportar fotos en lotes, me arroja un error "proxy unavailable" y me exporta menos de la mitad de las fotos. Si, tengo espacio en el disco C y disco D.Si, ya probé exportar de a 50 y sigue arrojando el mismo error.Necesito SI O SI una solución, ya que trabajo de esto. 

I purchased an annual Lightroom Premium subscription through the Apple App Store.Apple Support has confirmed that the subscription is active and valid until August 2027, with no refund or cancellation of the current subscription.Apple also resent the billing receipt and provided support case number...However, my Adobe account is still being treated as a free account and Lightroom does not recognize the Premium entitlement. I have already tried Restore Purchases.I need help identifying which Adobe ID this App Store purchase is linked to and restoring/synchronizing the Premium entitlement. I can provide the Apple receipt and transaction details privately if needed.

When one is in the Develop module and selects 20+ images in the filmstrip and hits the Sync button Lightroom has historically brought up the Synchronize dialog box immediately. In the last year or so, including LR Classic version 15.6, Lightroom now intermittently has a long pause of around 6-12 seconds before this dialog box pops up.Personally I’m using a MBP M1 Max with 64GB RAM and 3TB hard drive, and 100MP Fuji GFX100 files. This same machine and files did not experience this long delay in the past. This problem sounds small but for professionals doing post production 8+ hours a day this is surprisingly infuriating.I hope we can eliminate this long pause and get us back to where we were for years! Thanks for listening. 

Have been trying to connect my email (gmail.com) with the email function in LRCC.  It says it is validated, but when I hit the send button, it always tells me that a connection could not be established.  Everything is updated and the latest versions.  Thanks in advance.

Ignore update ai settings not available on Lightroom always forcing to update ai setting when it is not required or wanted.  For example if a remove tool edit is made on an area after an ai mask , then it generates the update ai  When copying/pasting any AI driven masks (Select Subject, Sky, Background, Objects, and People) and or by loading that image’s XMP sidecar file or preset / settings on the same image, the masks should not be  recomputed automatically or generate an update ai setting. 

I have been transferring my files to an external HD but not through LRC. But the file destination in the import module was set to C drive. I’ve edited a bunch in C but the saves are going to the HD. The file count in the folders for C are higher than the HD. Both places have all the files. What do I do?

Hello, I have Issues with my presets. According to several sources on the net, the default location for presets is ...\AppData\Roaming\Adobe\Lightroom\ Now I have activated the option to store Presets within the Catalog. The Location should be therefore <PathToCalatlog>\<Catalog>\Lightroom-Settings. After getting a new PC (Windows) and reinstalling Lightroom Classic and restoring the Catalog, I found out there are no presets in at least one catalog (catalog A). So I reimported the (thankfully backed up separately) presets in catalog A. However Lightroom has stored them under ...\AppData\Roaming\Adobe\CameraRaw\ImportedSettings. In catalog B I now have those reimported presets twice, once from the CameraRaw folder and once from its catalog folder. But even there is a huge mess. Some presets are stored within <PathToCalatlog>\<Catalog>\Lightroom-Settings\Developer-Presets but also under <PathToCalatlog>\<Catalog>\Lightroom-Settings\

I had my entire library on LR Online. Then I decided to move my entire library to LRC. At one point in this process, I had all my pics on LR as well as in LRC. At this point I was trying to verify sync behaviour and started sync. In 5-10 minutes I realized that it is only duplicating the assets on LRC and filling up my local storage.I paused the sync. Till it has queued entire LR online inventory of 30k+ assets for download. It downloaded some couple of hundred. At this point, I deleted all online assets except for two albums that are specifically mobile targets and I want to use them to bring mobile photos into LRC. Now I had around 4k photos on LR in these two albums and rest entire library of around 26K in LRC.Based on some google searches, to reset my previous sync, I deleted the sync.lrdata file. Without creating any collections in LRC (meaning nothing to sync from LCR to LR), I started the sync again. But I am not stuck. with lot of errors - refer to first image below. From the 2

LRC crashes time to time. No reason identified. It closes and sends report to Adobe. Never received any feedback from Adobe. It is annoying and I lose a lot of work done… I am using release 15.6

Does not remove as efficiently as previous versions - leaves shaddow / smudge reather than removal and replacement

i cant open and work on my liightroom classc errr 12000

Hello Adobe Community! 👋We’re interested in exploring how Adobe Photoshop can help create engaging visuals, informative graphics, and creative designs related to tree care, {Link removed by MOD} and landscaping.From designing educational graphics about tree maintenance to creating visuals that explain pruning techniques, seasonal tree care, and the importance of healthy landscapes, Photoshop offers many creative possibilities for presenting useful information in an attractive and easy-to-understand way.We believe that combining creativity with practical knowledge can help people communicate ideas more effectively. Whether it’s editing tree care photographs, designing informative posters, improving images, or experimenting with different visual styles, there is always something new to learn.We’re excited to be part of the Adobe Community, learn from experienced Photoshop users, exchange creative ideas, and discover new techniques that can improve our design skills.Our goal is simple: t

J’ai de très grosse lenteurs (plusieurs secondes) pour passer d’une image a l’autre dans Lightroom. je ne peux rien faire et j’ai le message “CPU en attente” durant plus de 3 secondes avant de pouvoir passer au traitement d’une autre image ! Ce problème disparait lorsque je désactive l’option  GPU sur mon lightroom. Mais c’est idiot de se priver de ma carte graphique pour les traitement d’IA ! Voici ma config :Version Lightroom Classic: 15.6 [ 202609251514-f839cde9 ]Licence: Creative CloudParamètre de langue: frSystème d'exploitation : Windows 11 - Home Premium EditionVersion : 11.0.26300Architecture de l'application : x64Architecture du système : x64Nombre de processeurs logiques: 16Vitesse du processeur : 3,8GhzVersion SQLite: 3.45.1Version Adobe GSDK: 1.4.0.213Utilisation du CPU: 0,0%Source d’alimentation: BranchéMémoire intégrée : 32693,5 MoMémoire GPU dédiée utilisée par Lightroom: 10143,1Mo / 16052,0Mo (63%)Mémoire réelle disponible pour Lightroom : 32693,5 MoMémoire réelle utili

All is ok on another computerI imported 500 photos in new folder. all seemed ok. did other work not sure what I did(?) today IMAGES SAVED ON EXTERNAL HARD DRIVE DO NOT SHOW IN LIBRARY. Will show if I hit IMPORT so not lost.

My main lightroom catalog for 2026 ended up corrupted today. I believe I have automatic backups on, as my other catalogs all have “backup” folders, but I can’t seem to find one for this particular catalog. It seems weird to me that most catalogs would auto-back up but not this one. The LR automated repair tool failed to fix the issue, and I’m trying to get the “catalog select” dialog to open to attempt to test the integrity of the catalog (as per Adobe’s troubleshooting guidance). However, no matter what I do, LRC always attempts to open the last opened catalog (the currently corrupted one). Hold ALT while opening LRC, nothing. Hold CTRL while opening LRC, nothing. Attempt to open LRC by opening a different catalog, and it just attempts to open the already corrupted catalog. Are there any other ways to force LRC to the catalog select dialog? Additionally, I have seen other users mention reaching out to Adobe support directly as they may have additional ways to fix corrupted catalogs. I