Design the future of fashion, win Firefly Pro 👗✨
Connect with fellow editors in our Lr Classic community.
Recently active
Lightroom Classic v15.6 brings a smoother editing experience with improved Reflection Removal, making it easier to clean up reflections in windows, glass, and water. This release also introduces faster masking controls with Check All and Check None options, along with support for new cameras, lenses, and important bug fixes. What’s NewThe September 2026 release of Lightroom Classic v15.6 brings meaningful improvements designed to make photo editing faster and more precise. The standout enhancement is Reflection Removal, which now delivers cleaner results when removing reflections from windows, glass surfaces, and even water. The updated technology reduces smudges and ghosting artifacts, helping photographers recover details more naturally in challenging scenes.This release also streamlines masking workflows with new Check All and Check None options in the Masking panel. When creating landscape or people masks, you can now instantly select or clear all available mask options with a sing
When presented with a New Post screen in the Adobe Community, you are given three options for Conversation Type: Discussion, Bug, and Idea. If you were searching in Discussions, the New Post window will default to Discussions. If you are searching in Bugs, the New Post window will default to Bugs and likewise for Ideas. Many customers instinctually report problems they are experiencing as “Bugs”. It is natural to think that a problem you are having might be a bug. A bug is defined, for our purposes, as “something in the software that is not functioning as it was designed to function”. Interpreting whether a behavior is a bug or not is not always easy, however. Here are some reasons why you might want to consider posting first to Discussions rather than jumping straight to reporting in Bugs: Most items reported as Bugs are not actual bugs. In a typical group of reported bugs, only about 3 out of 25* bugs reported turn out to be actual bugs. Of those, typically 2 ou
Bugs should only be reported for the latest or current version of Lightroom Classic. If you believe you have a bug, it must be verified on the latest version of Classic. New bug reports will not be accepted for older versions of the software. If you believe you have encountered a bug, it is important to first search the existing bugs to see if your issue and a possible solution or workaround have already been reported. If so, please add to that thread. If not, it may be prudent to start a new thread.Greater than 90% of the bugs reported are not actually bugs. Before starting a new thread, please read:P: Do I post in Discussions or Bugs? When logging a new bug report, it's required by the Lightroom Classic team for the information in the report to include steps to reproduce the bug experience. Once we can reproduce an issue, then we can start to investigate a fix. Bug reports without reproduction steps will be moved to discussions.If, after some troubleshooti
Adobe is excited to receive requests for additional features you need to enhance your workflow. What can you do to increase the chances of being heard? Don't use the words "Feature Request" in your post's title. Search for and add to existing feature requests rather than creating duplicates. There is no advantage to creating a second request for any existing feature request. One request per thread!When creating an Idea or Feature Request thread, please keep requests for features to ONE request per thread. Doing this will allow others to vote on a single, specific feature and not confuse Upvotes amongst a list of feature requests. If an Idea thread has multiple requests in it, a moderator may ask you to split the multiple requests up into multiple threads so others can vote. In the event there remain multiple requests on a thread, the first item requested will be the arbiter of where the thread will be cross-referenced or merged. Describe how the featu
I’m using Lightroom classic since I want all of my files locally.I am scanning using a Nikon Coolscan 9000 every negative and slide I ever took from the time I started photographing in the early 70s until I finally went digital in mid 2000. I estimate there are 50,000 frames all scanned at 4000dpi. The Silverfast work flow works great for color, especially the infrared based scratch and dust removal. That all changes for B&W. The Silverfast software based scratch and dust removaal really doesn’t work. So I’m back to Adobe for pretty much the rest of the project. I’d been using the standalone version of Photoshop Elements up until V10, but I’m scanning even the B&W into 16 bit format. Elements down samples to 8 bit so I lose headroom. I briefly used the full version of Photoshop (which included lightroom) in 2014 but tabled the project. Now I want to explore lightroom.My usage is “project” based. Essentially each roll of film scanned is a unique “project” and the files a
I currently shoot a lot of Bracketed shots for exposure blending, and with each shot having a different shutter speed the auto-stacking can fail to accurately stack the grouped shots - especially when the shutter speed gets up into 10+ seconds!I would love an option for Auto Stacking to work on the time delay between the shutter closing and the shutter opening again, so it is a true measure of the gap between shots. In this way I can auto-stack on all bracketed shots even when the shutter speed is seconds long. Calculate the time between shots by adding the shutter speed to the capture time of the first shot, and then compare this to the capture time of the next shot, and if I am using Continuous shooting, this gap will be only a fraction of a second, regardless of the shutter speed.Gary
When cropping a landscape-oriented photo to a portrait orientation, you can easily do so by dragging with your mouse.However, you cannot crop a portrait-oriented photo to a landscape orientation using the mouse in the same way.In Camera RAW, you can perform both types of cropping using the mouse.Pressing the "X" key allows you to toggle between portrait and landscape orientations.*To start cropping, begin dragging from near the center of the image.Lightroom Classic 15.6 , CameraRAW18.7 , Win11
I have updated the GPU drivers, but still the issue seems to persist. Other edits seem to work fine; only the denoise function is converting the image to B&W. Below is the system info copied from the Lightroom— Lightroom Classic version: 15.5.1 [ 202608131348-cab7eed5 ]License: Creative CloudLanguage setting: enOperating system: Windows 11 - Home Premium EditionVersion: 11.0.26200Application architecture: x64System architecture: x64Logical processor count: 16Processor speed: 3.6GHzSqLite Version: 3.36.0Adobe GSDK Version: 1.4.0.213CPU Utilisation: 4.0%Power Source: BatteryBuilt-in memory: 32153.8 MBDedicated GPU memory used by Lightroom: 12.6MB / 128.0MB (9%)Real memory available to Lightroom: 32153.8 MBReal memory used by Lightroom: 1840.6 MB (5.7%)Virtual memory used by Lightroom: 2096.9 MBGDI objects count: 693USER objects count: 2619Process handles count: 2137Memory cache size: 213.6MBInternal Camera Raw version: 18.5.1 [ 2687 ]Maximum thread count used by Camera Raw: 5Camera
System Windows 11 desktop built by Puget Systems 32 GB RAM NVIDIA GeForce RTX 3070 Ti, 8 GB VRAM Current Lightroom Classic 15.6 release Catalogs and previews on internal SSD; original photographs on internal drives ProblemLightroom Classic has become extremely sluggish and frequently hangs on my Windows 11 desktop. Operations that should be nearly instantaneous can take many seconds or longer. The problem occurs in Library and Develop and makes Lightroom impractical to use.The same photographs and edits perform substantially better in Lightroom Classic on my MacBook Pro Max.Reproduction with a new catalogMy principal aurora catalog contains approximately 76,000 photographs. Initially, I suspected a problem with that catalog or its previews.However, I created an entirely new Lightroom catalog on the Windows desktop and imported a small selection of DNG photographs. Import completed in less than one minute, but the new catalog exhibited the same sluggishness and hangs.A separate,
# Bug Report: Library Filter Date Column Does Not Retain Collapsed Years and Months After Restart**Product:** Adobe Lightroom Classic Version 15.6**Operating system:** Windows 11 **Affected versions:** Longstanding issue across multiple Lightroom Classic versions; currently reproducible in Lightroom Classic 15.6 **Component:** Library Module ? Library Filter Bar ? Metadata ? Date **Severity:** Low functional severity; persistent workflow inconvenience **Reproducibility:** Consistent across application restarts## Problem DescriptionThe Date column in the Library Filter Bar persistently restores certain years and months to an expanded state whenever Lightroom Classic is restarted, even after the user manually collapses all years.The issue occurs when viewing **All Photographs**.Specifically, Lightroom automatically expands:- **2014:** January, February, March, April, July, November, and December, including their individual dates.- **2022:** January, including its individual dates.All
I am running Lightroom Classic on a Mac mini (M6 processor, macOS GoldenGate) and notice that for a couple of weeks it can’t sync the same set of photos (5) to the cloud. Syncing does work (just created a new collection with 40 photos in it which synced perfectly to the cloud) but it is these 5 photos (from seemingly random collections) which refuse to do so.Already tried a couple of things:Rebuild Sync Data, which took a couple of hours to re-sync all synced collections (but at the end the very same 5 photos were left in the list Removed one of the 5 photos (as a guinea pig) from “all synced photos” then watched it being removed on the cloud collection and the re-adding it to its shared collections: it doesn’t sync, it gets removed from that collection but not from the “all synced photos”! and the number of photos to sync (which went down to 4 after removing it from “all synced photos”) remains stuck at 5 again. Removed all edits (read somewhere that some lingering outdated AI edit m
I experience sync issues in Lightroom Classic for some photos when I add them to a Collection that is synched to the cloud. Only photos that contain Generative AI remove operations are affected. The photos were edited before attempting to add them to a synched collection.I am running Lightroom Classic 15.5.1 on an M4 Pro Mac mini that runs MacOS 26.7.I have found a partial workaround, but it is slow and time consuming. The affected photos appear in the Sync Errors group in the Catalog area at the top of the LH panel. For each of the affected photos, I have to regenerate all of the Removal objects to completely regenerate the data; I have to select each removal object individually to regenerate because there is no bulk operation for a photo. On some photos this may additionally have consequences for masks and I often have to also refresh the masks.Regenerating the AI removal objects does not by itself immediately fix the sync - Lightroom remains stuck. For the sync to complete, I need t
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
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
This post applies to Lightroom Classic and the Lightroom Ecosystem products. Camera Raw feedback can be found here. Generative Remove makes it easier to remove unwanted objects and distractions with a simple gesture, even on complex backgrounds. For more accurate results, be sure to include the object's shadow in your selection and/or expand its size. Detect Objects uses AI to find the objects underneath a brushed area. The masked areas will now appear larger than the Early Access version of this feature. You can also circle objects for quicker selection now. We have also updated the spot selection experience to make it easier to manage variations, switch the fill type, refine the selection area, or re-generate as needed. Batch updating is also now supported for Generative Remove spots. Try out the latest updates and share your feedback with us here. Please also include the following details in your post: App versi
Immediately after importing new photos into Lightroom Classic, the SDK appears to expose an inconsistent or stale catalog state to plug-ins.In my case, two problems occur at the same time: catalog:getTargetPhotos() returns only one photo regardless of the actual selection in Lightroom. Keywords that have just been assigned to the newly imported photos are not reliably available to the plug-in through photo:getRawMetadata("keywords"). Closing and restarting Lightroom Classic immediately fixes both problems without making any other changes.After restarting Lightroom, the exact same plug-in code correctly detects the selected photos and the keywords assigned before the restart.Environment Lightroom Classic: [insert exact version from Help > System Info] Operating system: Windows 11 Lightroom Classic SDK plug-in Catalog containing an existing hierarchical keyword structure Newly imported RAW files Steps to reproduce Start Lightroom Classic normally. Import a new set of photo
You have issues with your latest LrC update. Also with this webpage as it just trashed my last attempt to report these bugs. Please fix this webpage! These issues, which never occurred before your last update now occur EVERY TIME I use my normal workflow.That workflow: Import my raw NEF file Enter “Develop” Use the <File><Plug-in Extras><Process with Topaz Photo (Studio) Let Topaz run its automatic noise reduction and, optionally do some other stuff such as sharpen (but not required to reproduce the bugs described below) Return the denoised DNG file from Topaz back to LrC and enter Develop module Attempt to enter masking. DOES NOT WORK. Change Profile from the default “Camera AUTO” to “Adaptive Color”. Now I can enter masking. But… Subject masking DOES NOT WORK. When I attempt it, the masking subwindow pops up and immediately disappears. Object masking works and I am forced to use it to get my work done. Once I’m done, I go to export my photo. I get the normal po
Il est intéressant d’avoir des masques IA qui distinguent Peau du visage et Peau du corps.Le problème est que bien souvent les traitements (clarté, lumière, etc.) du cou ont tout à voir avec le visage et pas du tout avec les bras ou les mains…Il serait donc bien, au moins en option, de pouvoir associer visage et cou et laisser le reste du corps sur une autre sélection.
I have used Lightroom Classic for nearly 20 years and have a large catalog (about 70,000 images). As you would expect, I’ve also spent countless hours organizing the photos, editing and assigning keywords.A few months ago, I suddenly began to experience a new problem. Suddenly, the “Exif and IPTC” fields on the right side of my screen were all blank (no keywords visible, no location info, no copyright info, etc.). The small “spinning wheel” could be seen but it never stopped spinning.I searched these forums extensively and also many other sites. There were recommendations that included resetting preferences, deleting the metadata helper file, and more. Ultimately, nothing has fixed the problem.I note that deleting the metadata helper.db file does help for a short period. In order words, if I delete it and then start Lightroom Classic, the IPTC and EXIF data reappears, however, after anywhere from 5 to 20 minutes, it disappears again and the spinning wheel returns.In addition, eve
This post applies to Camera Raw and Lightroom Classic. Dust Removal is no longer in Early Access status and can be found in the Remove edit panel for Camera Raw & Lightroom Classic. Dust Removal helps remove distracting spots in an image that may be caused by dust on a camera's sensor and is also effective on dust on the rear lens element. Once enabled, your image will be scanned, and any detected dust spots will be automatically removed using Content-Aware Remove. For refinement, you can select one or multiple spots to delete or refresh. Batch removal is also supported; simply select the "Dust" checkbox under "Remove" in the copy settings dialog.Please note that scanned negatives are not in the scope of this feature at this time. Dust spots on scans tend to be located in the focal plane, with the negative and very sharp, while sensor dust is typically positioned out of the focal plane and therefore not in focus. Scanned negative dust typically appears as white spots on a darker b
Since changing to new Macbook pro and Creative Cloud subscription service, Lightroom has been either slow or unresponsive. It seems to be worse with newest version and with Golden Gate OS, although same problem with Tahoe. Memory on computer: 1.4 TB. This is a widely experienced problem but there does not seem to be a response from Adobe.
I was doing some experimenting with my Canon R6 Mk ll on landscape photos today. Some shots were just RAW, some were HDR, and some were HDR PQ. While looking at the files in Lightroom Library, the ones that are HDR stand out (and they are .JPG files)… but the HDR PQ and regular RAW files look almost identical… (and they are both CR3 files).Is there anything I can click in the Customize Metadata Panel that will show this type of file information?
Since a few weeks, my Lightroom Classic (15.3.1 release on macOS Tahoe 26.5.1) gets stuck or stops responding on simple tasks like:Building standard or 1:1 previews (it gets stuck on ‘Building previews: 3 of …’ but never actually creates one preview) Photo Merge (HDR, Panorama or HDR-Panorama, here the cursor immediately starts spinning and the merge preview does not even pop up) Importing (I can select a source (for example an SD card) but it gets stuck on Checking for duplicates, even when I turn off 'Don't import suspected duplicates’) Exporting (in export I can select all the settings and hit Export but the progress bar remains stuck at zero.I have to use Force Quit to quit Lightroom when it’s not responding.This happens 9 out of 10 times I open up Lightroom, the occasional 1 time everything works fine and I can go on for hours merging huge panoramas or building previews of 100s of photos without problems. But whenever I close and reopen Lightroom the next time it doesn’t work anym
I have read about this on several sites and Im still confused.I have a lightroom classic catslog and all associated photos on my Macbookpro (4tb drive). The main folder is all my photos from 2023. I want to back these up to an external drive and free the space on my computer for this years (2024) photos. 1. I used the EXPORT AS CATALOG from the File menu. This appears to have backed up the photos on my external drive. However they are still on my macbook. Im just very confused about what seems like it should be a simple procedure. Im reticant to delete anything without understanding how this works. in iphoto its so easy (Move your photolibrary to an external disk-1 step!). Can I please get some solid, step by step direction to backing up my ohotos and catalog so I can remove 2023 from my laptop to make space? I intuit that I keep the same catalog (am I correct) on the laptop but point it to 2023 files on the back up disk. Then save the 2023 files o
Hi Adobe support, I signed up for the free trial of Adobe Lightroom but forgot to cancel before it ended. I was charged 80 dollars and wasn’t intending to continue with a paid subscription. Could you please provide a one-time courtesy refund?
Remix with Firefly Community Gallery
Thousands of free creations to fall in love with and remix in Firefly.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.