Lightroom Classic

Hi everyone,   I’m reaching out after two full days of troubleshooting and hitting a wall.   Despite setting everything up correctly in Lightroom Classic, I cannot get it to sync only Smart Previews to the cloud. Lightroom always uploads the RAW files (NEF), even when Smart Previews have been built.   Here’s what I’ve done:   Imported RAWs (NEF) from my hard drive into Lightroom Classic. Built Smart Previews for every image at import. Disabled the option in Preferences for a specific folder location for Lightroom’s synced images. Created a synced Collection containing only Smart Preview–ready images. Verified in Library metadata that Smart Previews are present.     But no matter what, when I enable sync, Lightroom uploads the full RAW files to the cloud and mobile, using up unnecessary space. Even when I try testing with just two images, the same behavior occurs. In the mobile app and web interface, the uploaded file is clearly the RAW, not the Smart Pre

Since updating to the latest 14.4 LrC update, processing a RAW image through DXO PureRaw 5 (which then imports it back into LrC) results in two copies of the imported image in the Lightroom catalog but referencing a single file in the OS - each copy in LrC has independent settings, as if one is a virtual copy, but deleting one image will delete both from catalog and OS..  Both images show in the filmstrip with the same file name, and no "copy 1" or similar.This is since the LrC 14.4 update and with DXO PureRaw 5.2 - the same PureRaw 5.2 works on LrC 14.3 without creating duplicate images in the catalogue.Screen recording attached.Macbook M1 Max - Mac OS 15.5

My 14 inch macbook pro uses the m1pro processor to upgrade to mac os ventura, and then uses the gpu of lightroom12.0.1 to accelerate it into limited availability 

How do I stop notifications on a tread that I've posted on and had a satisfactory answer? I'm getting lads of notifications for identical questions to one I asked!

Ver: 14.4Anytime I try to do basically anything, the program freezes then crashes. This was an issue about six months ago but was resolved (I don't know how), and seems to be back. Sometimes the crash happens immediately upon boot-up, sometimes during import, sometimes during copy/paste, sometimes when trying to switch between photos, etc. I have already tried the immediate troubleshooting tips of turning GPU acceleration off, clearing the cache, starting up in a brand new catalog, and clean installing the program. None of these have solved the issue. I have also checked the integrity of my drives and all appears to be good there too. My computer specs are also here:Processor 13th Gen Intel(R) Core(TM) i9-13900KF 3.00 GHzInstalled RAM 64.0 GB (63.8 GB usable)NVIDIA GeForce RTX 4070 TiNVIDIA Driver: 576.80

Hello, i wrote a python script (version3.10 in my computer) which is called by a lua script in lightroom 14.4. The python version called by the lua script is version 3.9.6 of python, that i dont find in my computermy command in my lua file is: local command = 'python3 ' ..'"'.. scriptPath .. '" ' ..'"'.. path .. '"' The question is where is the version of python that lua lightroom uses ? Is it possible to change it ? Thank you very much

I have the problem "some export operations were not performed" since months now. I updated Adobe LR Classic and since V12.4 i have suddenly (!) the problem that some random number (NOT ALL!) exported images (of the same batch) are not exported. All i get is the message: "some export operations were not performed". Nothing else. This is horrible to work with. Im paying for this product and there is neither a fix nor a valid forum solution anywhere online, since over a year.    Please, Adobe fix this. It has been overdue. Its also not a user mistake or computer settings problem. Same camera, same session, same filetype, same procedure as always. However, some images are randomly exported, others not. IT IS A BUG! FIX IT YESTERDAY! System: Windows 11, Adobe LR from 12.4 to  13.2, RTX 4070 TI, AMD 7700X, 32GB DDR 5, Samsung 990PRO, etc.This worked until last year. Since updating LR the export is not working properly. I followed all the tips and hints found online. NOTHI

Lightroom Desktop has been pretty stable and fast enough for me for the past 12-15 months but during the last month Lightroom has been maxing out my main system disc - performance graph in Task Manager hits 100%, everything grinds to halt, Lightoom more often than not crashes.Anyone know what I can do to fix (or at least diagnose) the problemWindows 112TB NVMe system drive with apps and Lightroom Catalogue 1TB free space4 TB NVME Data SSD - 2.5TB free space1 year Old Lightoom Classic up to date (14.3.1)Windows up to date

Bonjour, J'ai lightroom qui plante : ecran noir et PC bloqué lorsque je charge des photos dans la bibliothèque quand les aperçus se crée. C'est un problème récurent qui rend lightroom inutilisable. J'ai configurer lightroom pour avoir les aperçus minimum J'ai besoin de votre aide !!!  Voici le report d'erreur : erreur BEX64Module défaillant : video_toolkit.dll_unloadedc0000005 → violation d'accès mémoire Mon PC : Lightroom 14.4AMD Rysen 5 260032 go de RAM Geforce rtx 4060 (dernier driver pilote studio)  + ecran asus proart PA279CRV  4KSSD NVME samsung 980 1 to pour windows et lightroomSSD NVME samsung 990 plus 4to pour les photos 

I have recently installed another external drive and copied the Lightroom folder onto it from the current external drive.Whether this is coincidence or not I am not sure.  But when I have now finished editing a file I save it to file as a PSD document, as I have always done. However when previously it would re-open with the history of changes it not longer does. I can see the edited image in the catalogue with the history, so this issue only occurs when i export the inage as a PSD file renamed into the relevant folder and then open it back into LrC.I also retied making a Virtual copy of the image with its history that shows the masks, but again when it is exported out and comes back into LrC it simply shows as the first time it has been opened.Any thoughts or assitance welcome pleaseThanks

'ai acheté sur le net lightroom 5.7.1 mais impossible de l'installer windows 11

Hello fellow LRC users! I'm working through a work account so my system info is probably a little different from what you might be using but I've been getting an error the last few days after updating to (Mac) Sequoia 15.4.1. When using LR Classic (version 14.3.1), my team are all getting an XRD System Update error randomly when using LRC. It doesn't seem to be affecting anything critical- meaning we can just hit ignore (we've already sent countless reports) and continue on, but I was wondering if anyone else is encountering this error or if maybe it might be that our system admin needs to update random drivers? (Pic included so you can see the error)  

After a last update, the Copy Settings command no longer works and Lightroom locks. How can do it?

Ich benutze seit Jahren Ligthroom zu meiner  vollsten Zufriedenheit.Jetzt allerdings habe ich ein Problem:Aus dem Urlaub habe ich Bilder in RAW auf IPhone 16 pro über Icloud auf den Rechner übertragen, und zwar Kästchen rechts oben „weitere Downloadoptionen“ – „unveränderte Originalversionen. Aus den RAW-Dateien sind DNG-Dateien geworden.) jetzt sind aus den RAW-Dateien DNG-Dateien geworden. Bei dem Versuch nun, wie immer die Bilder in meinen Katalog zu importieren passiert folgendes:Importieren - Quelle suchen - öffnen - es erscheinen die Bilder im Fenster (hinzufügen), auf importieren drücken - Fenster wechselt – die Bilder verschwinden, es steht "Dateien werden importiert" - nach 25 Bildern steht der Vorgang still - es passiert nichts mehr - auf das "X" rechts oben, um den Vorgang zu beenden, öffnet sich ein neues Fenster: „es werden keine zu importierenden Fotos oder Videos gefunden. EndeLigthroom neu gestartet, Rechner mehrmals neu gestartet, neuen Katalog angelegt, andere Bi

X-Trans files look clean and sharp in Capture One. They do not in Lightroom. This has been an established fact since the first X-Trans sensor. A workaround recently has been the denoise tool to convert RAF to DNG, which then presents a far cleaner and sharper image.   However, you have now removed this part of the process, killing the only way to get decent X-Trans image representation from within Lightroom.   Why?

Hello,We're investigating and testing workflows involving several people based on Lightroom Desktop/Cloud in the initial workflow and Lightroom Classic downstream in the process. Based on Adobe's documentation we thought we could "flow" images downstream to end up for final storage in LrC.Now it however seems that albums that have been shared with a user are not syncing from that person's Desktop/Cloud environment to Classic. The albums shared show up perfectly in Desktop/Cloud, but do not get synced to Classic. Other albums do sync.I could not find any settings, or mentioning of this online. Is this a known limitation of the syncing, or are we doing something wrong?Rgds,Björn

Hi,I import photo's in LR Classic. I copy and convert to DNG and I make 1:1 previews as I import. When the import is finished everything looks ok but the meta data won't load. I have to close the program and restart. Than I can see the meta data and make changes. I am on the latest version Build [202506051112-5918896a]. Although this was the same with the older versions.Gr Toy Janssen

les raccourcis clavier (6 à 9) pour ajouter ou supprimer des libellés ne fonctionnent plus sur le pavé numérique uniquement. impssible de les utiliser.La seule soulution est d'utiliser le clavier avec la touche maj + 6; maj + 7; maj + 8; maj + 9.Une perte de gestion du temps très importante pour le flux de travail.Merci de corriger le problème.Cordialement 

I am using Lightroom Classic 14.4I moved LC to my D drive but my C drive is still be used up. How do I find and remove LC files from my C drive?  Lightroom Classic version: 14.4 [ 202506051112-5918896a ]License: Creative CloudLanguage setting: enOperating system: Windows 11 - Home Premium EditionVersion: 11.0.26100Application architecture: x64System architecture: x64Logical processor count: 12Processor speed: 3.6GHzSqLite Version: 3.36.0CPU Utilisation: 1.0%Power Source: Plugged InBuilt-in memory: 16314.1 MBDedicated GPU memory used by Lightroom: 30.9MB / 12115.0MB (0%)Real memory available to Lightroom: 16314.1 MBReal memory used by Lightroom: 717.6 MB (4.3%)Virtual memory used by Lightroom: 1101.1 MBGDI objects count: 748USER objects count: 2507Process handles count: 2668Memory cache size: 0.0MBInternal Camera Raw version: 17.4 [ 2272 ]Maximum thread count used by Camera Raw: 5Camera Raw SIMD optimization: SSE2,AVX,AVX2Camera Raw virtual memory: 13MB / 8157MB (0%)Camer

Hi.  I am new to the community and am not sure of the protocols.  I have an issue.  I was advised to try a preferences reset on my lightroom classic as it was slowing down sporadically.  Unfortunately this has broken my external hard drives links to the photographs (all the folders show with question marks), as I did not connect the hard drive when I performed the reset.  Is there a simple way to reverse this or to reconnect the links.  My catalogue is roughly 16000 photos (raw and jpeg).  Any assistance will be greatly appreciated.  I am working on windows.

I've been making printer profiles for years using iMatch, and have had no problems with LR Classic until now. At the moment when I create a template and go to choose a profile to put in it, I either get 'managed by printer' or one or two old profiles even of different printers. After many hours of playing about (including trashing Prefs) the only way I can get the correct profile (from the sys32/spool/drivers/color windows folder) to register in LR is to edit the printer template (in the LR Settings folder) manually and delete the autoincluded profile and substitute the new one, saving the altered template. That seems to work and LR shows the new profile after closing and reopening. The one thing I must NOT do is to click on OTHER in the LR profiles list - that just locks LR solid, and the only way out is to use Task Manager to exit LR, reboot and start again!! I'm not the only one to find this - I read another post where clicking on Other did the same thing.   So what is the prob

I am trying to access the lightroom API mentioned here - https://developer.adobe.com/firefly-services/docs/lightroom/api/lightroom_edits/For that I created an OAuth web app client id and client secret and followed the doc for getting the access token - https://developer.adobe.com/developer-console/docs/guides/authentication/UserAuthentication/ims#authorize-request   I am trying to hit the edit API but I am getting  { "error_code": "403003", "message": "Api Key is invalid" } error. I am using client id in the X-api-key header.Unable to figure our what's wrong here. I have a lightroom subscription

Software and system: I’m using Adobe Lightroom CC v. 14.4 on a MacBook Pro M4 max with 64 GB ram.    Problem description: When navigating between images using the left and right arrow keys, Lightroom becomes noticeably slow. Normally, switching between photos is smooth and immediate, but now the images don’t load properly. It often gets stuck showing the same photo, even when I press the arrow key to move forward.   Important context: The issue occurs even with a small number of photos. In the past, I’ve worked with 700 images without problems – now I’m only working with around 50 unedited photos. I’m simply sorting through them, not editing. The problem typically starts after reopening the program to work on a new set of images. The first session after reinstalling Lightroom usually works fine.     Troubleshooting steps I’ve already tried:   Cache settings:   I’ve gone into Preferences → Camera Raw Cache Settings and clicked “Purge Cache.”

I'm trying to learn how to get the most from my new Z6III and was using the LRC 14.3.1 "tethering" functionality but realised it was always capturing two JPEG files ecen though camera set to RAW+JPEG. I switched to using NX Tether 2.3 and without making any changes to the camera find that it captures an NEF and a JPEG file. Am I doing somethi ng wrong or is it a bug in LRC?