Lightroom Classic

I wrote a free browser userscript that automatically expands nested replies, expands the input box of new replies to fill the window, changes the initial reply ordering to oldest first, and shows up to 30 top-level replies at once.  See here for details: 

🔹 O que o Lightroom tem de IANo Lightroom mais atual você encontra: Selecionar Pessoa / Pele / Rosto / Olhos / Lábios (IA de máscaras) Remoção com IA (Remove Tool / Content-Aware) Redução de ruído por IA Ajustes automáticos inteligentes Perfis adaptativos 👉 É uma IA mais manual e fotográfica, você ajusta fino.🔹 O que o Evoto AI faz (e o Lightroom não faz igual)O Evoto é mais agressivo e automático: Suavização de pele “beauty” com um clique Afinar rosto, ajustar proporções Clarear dentes, olhos, olheiras automaticamente Retoque em lote de retratos Estilo mais “editorial / estúdio” 👉 Ideal pra grandes volumes de retrato (casamento, formatura, estúdio).Estou tendo que recorrer a outras soluções para tornar meu trabalho mais rápido! Tem previsão de incorporar ferramentas de IA mais automatizadas? 

Hello everyone,big trouble: when I import pictures they look good at first, the whitebalance is fine. as soon as i go to my edit panel in Lightroom CC the colors of my (not yet edited) picture switch dramatically, its mostly the white balance that goes wild. Any ideas what is happening? I'd love to start my edit on the picture here on the left, instead of having to make corrections first. Especially with many pictures in the queue.(You might hate the whitebalance on the left compared to the right hand side, I understand, but thats only for the visualisation. On any screen, and also in-cam, it shows me the left side colors.)Appreciate any answers! Raphael

BonjourLe contexteJ’utilise Lightroom Classic sur deux ordinateurs, un mini Mac doté de la puce M1 et un autre mini Mac doté de la puce M4.Les photos et les sauvegardes (ou backup) des catalogues sont stockés sur un disque externe.Le problème rencontréMi-janvier, sur le mini Mac M4, j’ai fait la mise à jour de l’OS vers la dernière version macOS Tahoe. Depuis, je rencontre des anomalies dans les fichiers backup : Le fichier le fichier zip constituant un backup contient deux éléments, un fichier lrcat et un dossier lrcat–data, et désormais deux fichiers temporaires lrcat-shm et lrcat-wal. Ce backup n’est pas exploitable sur un autre ordinateur avec Lightroom. Lorsque je visualise le contenu du dossier catalogue sur mon mini Mac M4, je constate bien que les fichiers temporaires shm et wal ont été supprimés. Si je crée un fichier zip avec les deux éléments utiles, le fichier lrcat et le dossier lrcat–data, j’obtiens une archive qui est tout à fait utilisable sur un autre micro ordinate

I now have the Lightroom Classic version 15,1,1 camera raw 18,1  and the Tahoe 26,2.  When I wan to get red off some pictures; I now get an error message :  the file could not be moved to the Trash.  The files are on a volume that does not support Trash ! Would you like to delete them permanently ? And 2 buttons : 1 delete permanently and a second one “cancel”.  But before the 26,2 version there was not a problem at all. The Trash has the great advantage that if needed you could “reset” the files back to the place they were originally stored.  All of my photo pictures are stored on an external harddrive.  Even all my files (docs/ pdf / music ) are stored on several external HDs.  Any idea how to fix this ? On all these drives I have “reading and writing “ authority.

Today I am pretty sure LRC updated and I got some pictures that I took today and when I went into Develop the Color Profile is just showing Beta. There are no color profiles like Landscape etc. I looked through google etc saying could be that it wasn't shot in Raw. I checked my camera says Raw and the Files are ending in .ARW. Am I missing something that maybe I am not seeing?

Hola, al instalar LRC y al querer usar la función de quitar con IA me salta el error Eliminación generativa ha fallado. Ya había usado en otra versión está funcion, pero en esta última instalación ya no.Mi equipo : i3 10ma, 16gb ram, gráfica GeForce GT 1030 4gb. 

Reflection removal in so many cases works wonder, astonishing. However I noticed that sometimes when using denoise after the reflection removal, the reflection removal will be undone. Here is an example, a snapshot from Egyptian museum. Image 1, original.Image 2, reflection vanished.Image 3, de-noised, reflections are back. And when I try to make it the other way around (1st de-noise, than reflection removal) the process hangs and never terminates.  No reflections. Denoised, reflections are back. 

Bonsoir,Je sature depuis le jour où est apparu Lightroom 2025, j’ai contacté Adobe mais sans succès, j’ai naïvement pensé que la version 2026 changerai qqchose, mais rien n’a changé…J’ai un PC Portable depuis Mai 2024 :Windows 11Intel 7Nvidia 4060 8GoSSD 1 To partitionné en C 200Go et D avec le reste.16 Go de RAMSur Lightroom 2024, tout fonctionné parfaitement, c’était hyper rapide.J’ai un PC Fixe depuis Décembre 2025 :Windows11AMD 7Nvidia 5060 8GoSSD 1 To partitionné en C 200Go et D avec le reste.32 Go de RAMDans les 2 cas j’ai exactement le même problème.Lightroom fonctionne de façon aléatoire : Dans le module développement, le logiciel peut-être fluide, comme hyper lent (½ sec pour passer d’une photo à l’autre, pour ouvrir la fonction recadrage, appliquer des masques, l’ia générative ou la réduction de bruit...etc) L’export peut prendre 10/15min pour 200 photos, comme 3/5h pour 50 photos Le GPU est utilisé à 1% (Malgré que tout soit coché dans les options) et le CPU à 10/15%… Les RA

If I edit a PSD (2025) file that is in my LR catalog what magic do I have perform to get the edits to consistently update and show in LR?I can edit a PSD file, return to LR, and the changes don't show. Or I should say most of the time nothing shows. Most of the time Selecting Read Metadata From File does nothing. Sometimes if I take the edited image and go to the Develop module, the changes appear. But then going back to Grid view, the changes are no longer there. But...sometimes the edits pappear instantly. If I select the edited image in the catalog and choose to Show In Finder, the changes are there in the file previewI have no idea how to control this appearing/not appearing other than to delete the file from the catalog and re-import. That seems a little stupid.I'm going to list this as a bug since it's something that happens a lot 

After M1 MacBook Pro Upgrade to Tahoe, Lightroom Classic is running extremely slow, 3 HOURS to export 42 images. My workflow has come to a halt  Help   [Moved from ‘Bugs’ to ‘Discussions’ by moderator, according to forum rules. You cannot file a bug report for Lightroom Classic 14.5.1 on MacOS 26, because Lightroom Classic 14.5.1 is not supported on that version of MacOS.]

Capture_1 is my PSD in LightRoom.Right-click --> Edit in Adobe Photoshop (Beta)…Capture_2 is what I get in PhotoShop.

En voyage, j’utilise l’appli mobile sur IPad pour télécharger mes photos. Et je fait quelques retouches.De retour à la maison, je lance classic, et j’attends le téléchargement. Tous les aperçus se téléchargent, avec les retouches. Mais si je les ouvre, l’aperçu me dit qu’il n’a pas la photo d’origine. Or je les voit si j’ouvre CC.Je ne sais pas comment rapatrier mes originaux, avec les metadonnées de retouche, sur mon ordi..

Lightroom Classic 15.1.1 on MacOSX with 56,000 images.I have been using LRC facial recognition for years, with photos from a variety of different ages and camera sources. A few years ago, LRC was very good at identifying people even as they aged or from unusual angles. This behaviour has noticeably downgraded in 2025/2026. Faces are being shown as ‘unnamed’ even though they are of people who already have 5,000 previously identified examples.Previously, at load time, almost all new faces were being named, even if some of the identifications were incorrect. Currently, almost all new faces are unnamed. It has become so uncommon that I am surprised when occasionally my own face is correctly identified.Has there been a change in the algorithm, and if not, is there something that I can do to get the naming function to work properly again in my installation? I have tried ‘Find Faces Again’ but it just redraws the face region without making a better identification. 

Any time I try to import an image to LrC the image gets darker. Then, when I adjust the settings and export it, the image gets brighter, as if I'm editing a different version of a picture. This makes impossible to work in my LrC and I've been struggling with this issue for some time now. Please help!!! Altough my specs aren't really focused on image editing an studio stuff, I managed to work with LrC for a long time before this issue came in. I suspect it's a GPU driver thing but I've looked everwhere and couldn't find an answer. Again, I'm not talking about RAW images an the JPEG or JPG conversions that happens in LrC. This issue happens with ANY image imported to my Lightroom Classic, even a JPG downloaded from Google.I'm running Lightroom Classic with:Intel i7-7700Geforce Gtx 106016 GB RAM

Has anyone tried Mac OS 26 RC? Are Lightroom, Photoshop, and the Creative Cloud app now compatible with Mac OS 26? I've never updated a Mac major version since I switched to MAC, so I don't know if it's worth waiting for it to work reliably and stably, or if I can just go straight to the new system on September 15th. Thank you in advance for your answers.

LR has lost 1285 photos. I did NOT delete them. Mainly RAF, some Tiff, NEF, dng. Clients want copies, but cannot help them. Have others  found LR has lost their photos, amnd what was the solution to get them back?

Hello everyone,over the past few days, I've noticed that reflection removal no longer works properly in LrC 15.x.(currently using 15.1.1., still not working)This is the case in both Windows 11 and macOS 15.7.3 Sequoia, regardless of the quality setting. Even downgrading to LrC 14.5 does not improve the situation. Apparently, even for older LrC versions (which support this feature), “something AI-related” is loaded in the background, which enables the feature. It seems that the current AI is also downloaded for older LrC versions.Incidentally, the same problem also occurs in Photoshop! However, I am posting it here because LrC is my preferred tool.Here is an example that I took with my iPhone 13 Pro Max at the beginning of April specifically to test the function.I have to say, the result blew me away with excitement in April!Original out of Cam (April 2025):Removed Reflection Value + 100, Best (April 2025) GREAT RESULT!!Reflection only Value - 100, Best (April 2025)Removed Reflection Va

This has been discussed extensively, but I haven't found a satisfactory solution.Lightroom is extremely slow when checking for duplicates importing new images. I have a 2009 iMac that performs this process 10 times faster than my Mac Studio M4 with a 64GB RAM and 2TB SSD.CF (or SD) card containing the camera RAW files is formatted in FAT32 (the format used by the camera itself). I format the CF card to Mac OS Extended format, and save the folder with RAWs in it, the duplicate check is incredibly fast (just like on my iMac). The problem is that I can't use a CF card with that format in my camera.Someone suggested, in another post, an intermediate solution, which is to download the images to the computer and import them directly from there, but this involves more steps and ultimately results in a slower import from the card.I'd like to know why a 15-year-old computer performs this function much faster than a recent, super-powerful, and super-expensive computer.

Using a new Windows PC. LRC ran perfectly well until I installed the latest update. From that moment the Assisted Culling demo pop-up appeared every time I tried to import images. I’ve rebooted many times, used tips to do an action first and tried turning off the assisted culling. I don’t need it or want to use it. 

Are you experencing a painfully slow lag moving between images in the Develop module, since the 15.1.1 update? Usually between 3 to 11 seconds delay when simply moving from one image to another. If YES, read on... After 8 hours of 'support' from Adobe I now have a direct line to their Development Team and a live case open which they're investigating. They've asked me to provide system details and contact for anyone else experiencing the same.And don't panic, they've acknowledged the problem is the update, not your machine!Please comment here with your system spec. If you can add a screen capture video even better. I'll send them to the Dev Team and update you all on their progress! Cheers, Rich