

Lightroom Classic 14.4, Lightroom Desktop 8.4, and Lightroom Mobile 10.4 have all been released today. They introduce some exciting new features in all versions of Lightroom. As usual, there are also bug fixes and new lens support. And a big headline for Fuji shooters – Lightroom Classic now supports tethering without purchasing a third-party plugin!
Premium Classic Members of our website, click here for even more details on the changes to Lightroom Classic (you will need to be logged in to access the link).
Premium Cloud Members of our website, click here for even more details on the changes to Lightroom Ecosystem (you will need to be logged in to access the link).
New bugs…
- Classic: Identity does not retain font and color choices after update (Windows).
- Classic: Using Super Res and Edit in PS, file fails to open in PS.
- Classic: (Polish Language) – “Copy Settings” Dialog Window Cut Off.
- Classic: Book Module – Used/Unused filters are not showing the correct selection.
- Classic: Nikon Z5 II – White Balance Issue.
- Classic: Import Copy As DNG loses metadata set by metadata import preset.
- Desktop: Brush in intersect mode does not show the cursor.
Enhance without creating a DNG (Classic & Desktop)
If you’ve enjoyed using the Enhance tool to increase the size of your best photos using Super Resolution or to benefit from the AI-generated noise reduction (Denoise), you’ll be excited to find that these tools are now available directly in the Detail panel, without needing to generate a separate DNG file. This also means you can go back and change the amount of Denoise applied without having to generate another DNG file. Great news!!

However, before you rush off to apply Denoise or Super Resolution to every photo, there’s one big warning:
Although it no longer creates a separate DNG file, it does still use a significant amount of space. Because it generates pixel data, it differs from a normal slider or checkbox. For example, when we tested them on a 24 MB raw file, applying Super Resolution created approximately 48 MB of extra data, while applying only Raw Details generated around 18 MB of extra data. Denoise had the lowest impact, creating only about 5 MB of extra data.
In Lightroom Classic, the new pixel data is stored in the .lrcat-data file alongside the catalog. In Lightroom Desktop Cloud mode, it’s saved to the cloud database. If you write to XMP in Lightroom Classic, or you use Lightroom Desktop in Local mode, it also creates an enormous .xmp sidecar file for proprietary raw files, or writes to the header of other file types, increasing their file size. If you accidentally apply one of these edits to all your photos, your catalog could quickly grow enormous, so exercise caution when syncing edits or creating presets.
Distraction Remove – People (All versions)
There’s a new Distraction Removal tool, which is designed to remove people who aren’t the subject of a photo. It uses AI to automatically select any distracting people, and then employs Generative AI to remove them and repair the background. The detection is based on the current crop area, so if you want to remove people who are currently hidden by the crop, remove the crop before running the People Removal.


Distraction Remove – Reflections (Classic & Desktop)
The new Reflections Removal tool uses AI to eliminate reflections created by photographing objects through glass, such as items in a shop window, artifacts in a museum, or the view through an airplane window. You do need to be quite close to the glass, so it doesn’t work well for windows in real estate photography. It’s not designed to work with other kinds of reflections, such as water or mirror images.
Unlike People Removal, it only uses AI to identify which elements are behind the glass and which are the reflection, and then enhances those differences, so it’s not generating new pixels. It can make a huge difference to the photo, so it’s worth applying early in the editing process, as it’ll affect your other editing choices. As with many tools in Lightroom, it works better with raw files than with rendered (e.g., JPEG, TIFF, HEIC).


Update AI Settings (Classic, Desktop, iOS, iPadOS)
Replacing the red dots in the Toolstrip, there is now an icon showing if AI settings need to be updated. If it needs updating, the icon changes to orange and there is a list if you click on it showing the AI tools that will be updated.



But why on earth would you need it? Some tools, such as Masking, Lens Blur, and Adaptive Profiles, create a mask based on the image pixels, so when the image pixels change, the mask needs to be recreated. For example, imagine there’s a seagull in the photo when you create a Sky mask to darken the sky. If you then use the Remove tool to remove the seagull, the mask isn’t automatically updated, so you’re left with a ghost of the seagull.

Other tools, such as Generative Remove, Denoise, or Super Resolution, generate the pixels themselves, so when the base image changes, the new pixels need to be regenerated. For example, if you use Generative AI in Remove and then enable Denoise, the Remove repairs must be regenerated because they’ll be too noisy.
Automatically Download Originals When Using AI Tools (iOS, iPadOS & Android)
Lightroom on mobile doesn’t automatically download the full-size original from the cloud by default, because the smart preview is fine for most editing. However, the AI tools that generate new pixels, such as Generative AI and People Removal in the Remove tool, are the exception. For quick social sharing, the replacement pixels generated from a low-resolution file may be perfectly acceptable, but if you need a higher quality output, you’ll want to use the full-resolution file.
There’s a new global preference entitled Download originals when using AI tools, which automatically downloads the original from the cloud when you try to use a Generative AI tool. When using the Remove tool, you can override that global setting for individual photos by tapping the button in the top left corner.
Quick Actions
Scene offers a range of automatic adjustments that vary depending on the content of the photo. For example, adjusting the Water slider adds a mask to any bodies of water found in the photo and adjusts its Contrast, Highlights, Blacks, Temperature, Saturation, Clarity, and Dehaze. These quick settings may be enough on their own, or they can serve as a starting point that can be further adjusted using the individual tools and sliders.

Other Changes
- Classic
- New Filters & Smart Collections – options now include if a photo has Reflection removal, Distracting People removal, Denoise, Raw Details, or Super Resolution.
- If you have Automatically Write to XMP enabled in Catalog Settings, there are a couple of small changes to improve performance. Writing to XMP is now automatically paused while an Import is running, and when you’re working on a photo in the Develop module, it now saves every 10 seconds.
- If you check Remember the last selection from a source during the session in the Preferences dialog > File Handling tab, Lightroom now remembers your last selection for the 25 most recently accessed folders, collections, and smart collections (excluding special collections, such as All Photographs and Quick Collection). This temporary memory resets when you quit Lightroom.
- Duplicate Detection During Import – As of this release, a matching filename is no longer required, so files with identical capture date/time and file size are now recognised as duplicates, even if their filename differs.
- Identity Plate (Windows only) new/updated text Identity Plates can only use a single text style. Previously, you could have different fonts, colors, or sizes for different text selections. If you want to do that now, just create a PNG file in Photoshop to use as a graphical Identity Plate.
- Missing Folders – If an entire folder is missing, and you click on a missing photo exclamation point icon, Lightroom now asks if you want to locate the missing folder or just the single file.
- Desktop
- PNG is added as an additional export format.
- Android
- QR Codes for Web Galleries now use the Album cover as the background.
New camera support:
- Fuji
- X-E5 (preliminary support)
- Google
- Google Pixel 9a Front Camera
- Google Pixel 9a Ultrawide Camera
- Google Pixel 9a Wide Camera
- OM Digital Solutions
- OM-5 Mark II (added in ACR 17.4.1)
- Panasonic
- Panasonic LUMIX DCS1M2ES (Final support)
- Panasonic LUMIX DCS1M2
- Sony
- Sony FX2 (ILME-FX2) – (Preliminary support added in ACR 17.4.1)
- Sony FX3A (ILME-FX3A) – (added in ACR 17.4.1)
- Sony Xperia 1 VII Front Camera
- Sony Xperia 1 VII Ultrawide Camera
- Sony Xperia 1 VII Wide Camera
- Sony Xperia 1 VII Zoom Camera
- Sony ZV-1A
- Click to view the full list of supported cameras
New lens profiles:
- Canon
- Canon RF 75-300mm F4-5.6
- SIGMA
- SIGMA 17mm F4 DG C023
- SIGMA 20mm F1.4 DG A022
- SIGMA 24mm F2 DG C021
- SIGMA 24mm F3.5 DG C021
- SIGMA 35mm F2 DG C020
- SIGMA 45mm F2.8 DG C019
- SIGMA 50mm F2 DG C023
- SIGMA 65mm F2 DG C020
- SIGMA 90mm F2.8 DG C021
- Sony
- Sony FE 50-150mm F2 GM
- Sony Xperia 1 VII Front Camera
- Sony Xperia 1 VII Ultrawide Camera
- Sony Xperia 1 VII Wide Camera
- Sony Xperia 1 VII Zoom Camera
- Viltrox
- Viltrox AF 25mm F1.7 E
- Viltrox AF 25mm F1.7 XF
- Viltrox AF 25mm F1.7 Z
- Viltrox AF 28mm F4.5 XF
- Viltrox AF 35mm F1.7 E
- Viltrox AF 35mm F1.7 XF
- Viltrox AF 35mm F1.7 Z
- Viltrox AF 50mm F2.0 FE
- Viltrox AF 50mm F2.0 Z
- Viltrox AF 135mm F1.8 LAB Z
- Click here for the full list of available Adobe Lens Profiles
New tether support (Classic only)
- Canon
- Canon EOS R50 V
- Canon EOS R1
- Canon EOS R5 Mark II
- Fuji
- Now supports tethered capture for Fujifilm cameras
- Click to view the full list of cameras supported for tethering.
Bug fixes:
This is a major update so lots of work was put into the new features, but it did also include bug fixes. Adobe only publishes the ones that were reported by users.
- [ACR] – JPG export strips exif information even with include all metadata selected
- [ACR] – Support for raw file for Sony ZV-1A
- [ACR] – Lumix S1RII underexposed 12 bit Raw files
- [Classic] – Ability to turn off panorama mode for web sharing
- [Classic] – File Not Found shown in Metadata panel’s File Size after reconnecting a drive
- [Classic] – Locate folder > Error is displayed when tried to relink the folder present on NAS
- [Classic] – Export Fails with error dialog when Lens Blur is used
- [Classic] – SDK: Can’t call LrBinding.makePropertyTable() from scripts in Scripts folder
- [Classic] – SDK: LrDevelopController.getSelectedTool() doesn’t return “local_point_color”
- [Classic] – Crash (10266620)
- [Classic] – Tethered Capture imports two JPEG files rather than RAW + JPEG when JPEG is treated as a separate file
- [Cloud] – Can no longer run Enhance > Super Resolution on JPEGs, TIFFs, & PSDs converted from Denoise
- [Cloud] – Some AI Mask Overlays do not appear
- [Cloud] – Local mode shows blank or empty when not connected to internet
- [Cloud] – Brush Mask creates an errant diagonal straight line stroke (Win)
If you find a bug, click here to learn how to report it to Adobe.
How do I update?
To update on the desktop, go to Help menu > Updates or click the Update button in the CC app. The update servers take a while to push the updates around the world to avoid overloading the servers. You can also open the Creative Cloud app, click the … icon (top right), and select Check for Updates to give it a nudge. To update on mobile, visit the App Store (iOS) / Play Store (Android).
Are the books updated?
The eBooks for Adobe Lightroom Classic – The Missing FAQ and Adobe Lightroom – Edit on the Go have been updated to include the new features.
The eBooks can be downloaded immediately after purchase. If you already have a current Premium Membership for the relevant eBook, the latest eBooks are available for download in your Members Area.
Premium Classic Members of our website, click here for even more details on the changes to Lightroom Classic (you will need to be logged in to access the link).
Premium Cloud Members of our website, click here for even more details on the changes to Lightroom Ecosystem (you will need to be logged in to access the link).
Are the books updated?
Hi Victoria, Thank you the remainder email on Batch update A1 edits.
You currently have two books (Premium), one covering Classic and the other for desktop and mobile. Is there any plan to introduce one for the web version or incorporating into the desktop and mobile version?
I have noticed that there are some functionalities in web which are not in the mobile version of Lightroom.
( I couldn’t edit my first comment😕)
I ment say that web part of the Lightroom sections appears as not integrated with rest of the text. Some web options enhancing people’s skin tones are not in IPad version. If one changes it in web, what happens to the changes if one try to edit again in IPad? Do they disappear or one has to return to web for further edits? I think these anomalies affect the mobile/ipad than the classic.
Great question. There’s already some Web stuff in Edit on the Go, which is the desktop/mobile book. Those Quick Actions (which includes the skin one you mentioned) are in the Editing Tools chapter > Speed Editing Using Quick Actions on Mobile and Web lesson.
Those quick actions are shortcuts to standard LR edits, so in the case of skin quick actions, they create masks. If you use those quick action shortcuts on the web (or phone), the resulting edits will be accessible and editable in the normal Masking tool in the iPad app.
I do have plans to add a few more web details into that book, so if there’s any specific features you have in mind, do let me know.
Something else I’ve noticed about the denoise function – by the way, I’m really happy with it, especially since it doesn’t create an extra DNG file, which is great for my workflow.
When I apply it to a photo with a high ISO value of 8000 (using the default denoise value of 50), and then use the AI Remove tool afterward, the noise seems to come back more than in the original photo. Has anyone else noticed this?
The noise seems more noticeable than it was on a Denoise DNG? Or the remove repair is still a bit noisy on any Denoised file, whether it was a DNG or not?
I’m talking about the new denoise function (so not using a separate DNG file). When I remove something using AI Remove in a file with denoise active, I encounter additional noise in about 90% of the cases at the spots where the objects were removed—so clearly that you can exactly see where something was taken out. This effect also occurs if I first remove something and then apply denoise.
So this is new… you hadn’t seen the same issue when using Denoise as a separate DNG. It would probably be worth reporting with screenshots, just so everyone’s clear on exactly what you’re seeing. Here’s instructions on how to report it to Adobe: https://www.lightroomqueen.com/send-bug-report-feature-request-adobe/
I will do that
https://community.adobe.com/t5/lightroom-classic-bugs/more-noise-after-using-generative-ai-remove-on-a-raw-file-with-denoise-lr4-4-classic/idi-p/15422951#M62274
I only recently upgraded to version 14.4 after completing three major sport events.
What I’ve noticed is that the catalog file size has increased significantly, presumably due to the denoise processing.
In version 14.3, the file size was 320 MB, and now in 14.4 it’s 8.02 GB.
Has anyone else noticed this?
I only realized it when I was backing up from Lightroom to my NAS — the process took a very long time.
The lrcat file? Or the lrcat-data file? If the latter, yes, I assume you’ve enabled Denoise for a lot of photos?
it’s the .lrcat file.
That’s unexpected. 320MB sounds exceedingly small unless there weren’t many photos in the catalog, and 8GB sounds quite big unless there’s a lot of photos. That big a jump sounds odd unless you shot a lot at those three major sport events. Have you optimized the catalog recently? How many photos?
I always create a separate catalog for each event due to the specific keywords (names of athletes and clubs). In this case, I had a total of 17,654 shots, of which 2,416 were uploaded to an online photo album on Flickr. Some of the 2,416 photos were processed with denoise. All shots were imported into LR 14.3, and only after finishing the other two events (with their own separate catalogs) did I upgrade to LR 14.4.
I close the catalog at least once a day, always performing an optimize and backup.
I’m intrigued. 8GB is big for an lrcat file unless there’s lots of History steps. If you don’t need the History anymore (or you can try on a copy of the catalog), perhaps see if clearing the history for all of the photos shrinks it massively?
Sorry, but I can’t reply on your latest comment. I already make a copy of the catalog and deleted all the not published photos, then optimized the catalog twice and the .lrcat is still 7,79 GB. Normally I have not so many development steps, only import preset, transform and crop. Sometimes denoise. that’s all. Maybe I’ll try to export this as a new catalog….
Great idea. Make sure you optimize after deleting all the not-published photos too.
So I did an export of the catalog, but it has no effect on the size. Fortunately, I work with several catalogs and have only encountered this problem with one of them. I think I’ll just have to live with the fact that this catalog file is so large for this event—unless someone else has a suggestion?
A long shot, but do you write the metadata to the files? My memory is a big vague but I came across something in the last few days that mentioned unexpectedly large catalogs when writing xmp.
Yes, I do write the metadata to the files, in my case the xmp file next to the nef file. I see a significant grow in size of a xmp file with denoise applied. Normally 14,3 kB and now around 10,5 MB. Also with my other events, but there is not a abnormal growth of the lrcat file.
Is there a way to force update of AI masks on multiple images at once on Ipad?
Not at this time, no.
Everything seems great with the update (I love the denoise changes), except that I’m having trouble with the second monitor screen; it keeps popping over on top of the first monitor screen, I did the process your recommended on June 23 about how to uninstall and reinstall, and it simplified the problem. Now all I need to do when this happens is use Alt-Tab on Windows 11 to get backs to both monitors showing what they are supposed to, but I’m having to do that over and over again, sometimes every time I click on anything (but sometimes not quite so obnoxious). Any ideas or suggestions?
Thanks.
In Preferences > Display tab, which monitor do you have it set to default to?
Now I have chosen the secondary monitor instead of the primary monitor. Not tonight but soon I will see whether that makes a difference. Part of the difficulty is that sometimes it behaves as I expect but other times no. Thank you so much for pointing me to this setting I wasn’t aware of before.
I can’t launch the new LrC. It tries to open, a black dot appears below the icon. But then it fails to launch. On Mac OS 15.5. I was on line with Adobe for 5 hours on Saturday and still no luck. I tried uninstalling, and reinstalling Creative Cloud and LrC 3 times. I’ve tried the Option>Command>Shift>LRC to try and retain catalogs. I’m at my wits end. Disabled VPNs. I’m on a shoot in Ukraine! Any help welcomed
Oh that sounds like a nightmare! I’m guessing you’ve tried installing the previous version of Lightroom (so 14.3.1)? And you’ve tried trashing preferences? And you’ve tried creating a clean catalog to see if that opens ok? And you’ve tried a uninstalling, rebooting, then reinstalling?
I have! I had a second round with an Adobe tech and did all that again. I’m getting a “senior tech” hopefully today. Problem is I have to stay up half the night! I’ll let you know how it goes. Thanks
Update. My case was elevalred to a “senior tech” and an appointment made, which the did not keep. I have an Apple genius bar appointment to see if it’s an OS problem. I had some minor problems when it updated. Still no LrC. But PS and other Adobe apps work.
If I was troubleshooting it, I’d try two more things. I’d try a different user account (like the Guest account) to see if it was something specific to that user account. And if it didn’t work there, it points to an installation issue, so I’d back everything up (prefs, etc. for all Adobe apps, not just Lightroom) and use the Adobe CC Cleaner app to wipe all trace of Lightroom installation and then reinstall. But only do that on good wifi as it’d have to reinstall all the apps.
Success. Apple store said to reinstall OS and start a new user account. They recommended a new install…not from a back up because something in the system may be just reinstalled. It took a while because all apps had to be reinstalled from scratch. But, yes, Victoria, you were spot on.
I’m so pleased you’re back up and running!
The jump in files size for application of denoise in LrClassic is only evident in the XMP in my test
I did not see any increase in any file in the lrcat-data folder
My CR2 files denoised averaged about +13MB per XMP file. I have auto write XMP changes set.
Does auto write XMP bypass the lrcat-data folder?
No. *.lrcat-data is the place the catalog finds the information – writing XMP files is a user-choice, the catalog doesn’t use them.
Sorry don’t understand your reply. Doesn’t answer the question!
The article above states “ In Lightroom Classic, the new pixel data is stored in the .lrcat-data file”
My test it did not! It only writes to XMP hence the question
Does auto write XMP bypass the Lrcat-data folder???
Lightroom Classic relies on its catalog (the lrcat file and lrcat-data), so they’re always written regardless of whether you’re also writing to xmp.
I beg to differ. I applied Denoise as a batch to about 400 files shot at ISO greater than 1000 from Fuji GFX 100s ii. The data file on my catalog (400,000 files, data file size previously only about 800MB) has overnight jumped to 36GB. I back these up routinely to dropbox, so it is disastrous for my workflow. And, worst of all, there is no way that I can see to then delete these denoise files after exporting JPG output from the edited RAW files. This has to change, and quickly
Differ all you want. I have no increase on Canon.CR2 files denoised except in XMP, about +13MB per XMP file.
You fail to mention what Data file increases for your Fuji? Do you mean XMP? Is it files in the “Lrcat-data” folder? You need to be precise!
I have Auto XMP turned on & use CR2 files.
So to ask an “Expert” please. Does auto write XMP bypass the lrcat-data folder?
No, writing to xmp does not bypass the lrcat-data file.
The update from 14.2 to 14.4 introduced significant lag in the Develop module when using the left/right arrow keys to move through the images. Reverted to 14.2 and LrC is fast again.
What happened for you in 14.3? And what system specs?
I skipped 14.3 and went directly from 14.2 to 14.4 and then back to 14.2.
M2 Mac Studio, 64 GB, 4 TB, macOS 15.4.1.
Got it. Report it to Adobe ( https://www.lightroomqueen.com/send-bug-report-feature-request-adobe/ ) but they’ll probably need you to install 14.3 to see whether you see the issue there or not.
I updated from 14.2 to 14.3.1 and do not see the lag that was present in 14.4.
I also noted that there are reports of this behavior in previous versions (13.5) so maybe this is a regression? I have not filed a bug report yet.
Thanks.
Interesting. Yes, definitely worth reporting. Thanks for checking.
Same here. The lag started for me when I moved from 14.3 to 14.4, on a Mac Studio M1, 64GB OS 15.5
Sometimes 5-10 secs lag when stepping to next image in develop. But not always…
Before that I was very happy with the speed and latency of LR.
Same lag for me as well when moving images left to right in develop module in LR Classic. Moved from 14.3 to 14.4. MacBook Air M1, 16GB, OS 15.4.1.
And actually same issue with ca 3 second delay for getting the “Copy Settings” pop-up window to appear (same as mentioned by Bryan further below on 22 June).
Weird. Please do make sure you both report it to Adobe so they can figure out what’s going on for you.
I’ve been a LR user since it was called Rawshooter and never experienced as many issues as I have with this latest release to the point where it is unusable. Is there any sign of a bug fix release? I’ve tried reinstalling LRC, I’ve recreated my catalog which I thought had sorted things but haven’t. All in all a bit of a shambles.
Odd, we’re not hearing much in the way of traffic on new issues. What kind of problems are you seeing?
Unfortunately the new Denoise locks up LR (vs running in the background) leaving the user unable to continue working in LR. IMO this really inhibits one workflow. What I find interesting is that Adobe was obviously aware the denoise process would not operate in the background with this change and they went forward with it regardless. If a solution (hopefully in progress?) to fix that was not ready, a better approach would have been to either not implement the change or simply allow the users to determine the name of the resulting dng which many had asked for on the reporting site when the dng process was first introduced.
As it stands, this is a very big problem for my workflow. I’ve used LR ever since the original beta and never have I had to resort to going backwards, until now. Kind of hard to imagine the thought process they used that allowed this change to go into production.
When Denoise was introduced, it was intended to be used on your best photos rather than applied to large numbers. However, people then build their own workflows and use the tools in different ways, so we are hearing a fair bit of noise on this. Hopefully, Adobe will find a way to please everyone.
Really hope so Victoria. Clearly there is a pressing need to not lock up LR as it processes. While others are able to utilize the neural engine, Adobe has again turn that capability off. Getting that turned back on will definitely help.
Hi
Running into compatibility issues trying to install LrC 14.4.
PC is running Win 11 Pro, 24H2, OS build 26100.4351 so everything is up to date.
Processor i7-10700K @3.8Ghz : RAM 32Gb : Graphics NVIDIA 4Gb GeForce GTX 970.
LrC 14.3.1 installed without any issues so I’m not sure what the issue is here.
Any suggestions or just wait for Abode to come out with a fix?
Wow, this update completely broke tethered shooting for me. I have a Fuji GFX100S hooked up to an M2 Max MBP and I was really looking forward to adjusting aperture and shutter from within LRC, but instead had to manually operate the shutter button, while LR persistently showed an older Version of my set as the new image (even though a new RAW file still appeared on my internal SSD). Did all the usual restarts and reboots to no avail and had to install the previous version again where everything works just as it should again 🤷♂️
How did it break tethered shooting for you, when Lightroom didn’t previously have Fuji tethering? Perhaps you previously had Fuji’s tethering plug-in installed, and switched to using Lightroom’s own one this time?
You’re right, currently I have Fuji’s Tether Plugin Pro for GFX installed, without which GFX cameras and LrC wouldn’t play nice. This has worked fine for years, just this latest LrC update changed things. Though I wouldn’t know how.
So before the update, I would adjust the camera’s settings manually, connect it and shoot using Lightroom.
How it breaks tethered shooting is just LrC’s shutter button isn’t working with the update installed, I have to manually release the camera’s shutter button for it to take pictures, which kind of defeats the purpose. Especially since in my case the camera is often difficult to access with the kind of sets I’m working with. Weidly enough, I can adjust the camera’s settings from within Lighrroom now.
I tried using the update again and at least now the images appear correctly in Lightroom, but the shutter button still isn’t working.
I would love to get this working for a magazine shoot next week, but I’m stumped
Have you tried disabling the new plug-in so you can continue using the old one? Or vice versa?
Unfortunately Fujifilm doesn’t comply with the EU Digital Services Act, so the GFX plugin can’t be downloaded anymore from Adobe Exchange. Meaning I don’t dare uninstall it, because I can’t download it again and don’t have the install file anymore. It’s quite the conundrum
Oh tricky! You shouldn’t need to uninstall it though, just disable it in the Plug-in Manager dialog. You should find the disable button somewhere down the right-hand panels. Or disable Adobe’s one to see if that sorts out your existing plug-in.
Distraction Removal is an interesting and useful feature, but as might be expected, a bit buggy. Here is the bug I just found. When I select a file from my Lumix DC-FZ80D in either RW2 or JPG format, neither the Reflections nor People bars expand. For files created by other cameras this does not occur. I’ve discovered at least two work-arounds: convert the RW2 to a DNG, or do some other processing, e.g., apply Denoise to the image.
I omitted my environment: In LRc on Windows 11.
Further explorations. If I’ve expanded Reflections or People on an image that allows it, and now change the selected image to one that would not allow it, then Reflections or People remain expanded, but the one that is not expanded might (or might not) disappear entirely. The one that remains expanded cannot now be collapsed. Very confused behavior.
Could you try this tip given by an Adobe staff member please?
– Open Remove tool and press Alt key.
– Observe that visibility icon at the left end of “Distraction Removal” panel header is replaced with a switch icon.
– Now click on the switch icon ( with Alt key pressed ).
– Observe that Distraction removal features are now completely grayed out.
– Now click on the switch icon again ( with Alt key pressed ). This would re-enable the features.
Super slow compared to the last release, on my Mac Studio M1 Ultra machine. Regularly getting “Gathering Information” in the upper left corner when I’m just trying to load a photo, or change a color label, while in Develop mode. And getting the Copy Settings window to appear sometimes takes up to 3 seconds.
Adobe really needs to do a better job testing these updates in terms of performance. Or get better beta testers. It’s disappointing, because the rest of this update rocks.
We’re not hearing many similar reports, so I’d wonder what else is going on. When something like this happens immediately after a release, it’s often due to an installation problem, so that’s where I’d start troubleshooting… a clean reinstall.
Clean Lightroom Install Procedure
Close Lightroom
Restart the computer
Use the Adobe Creative Cloud App to uninstall Lightroom
Restart the computer
Install Lightroom via the Creative Cloud App without launching any other programs.
Restart the computer
Launch Lightroom
Wait 5 minutes
Same here on Windows.
When Denoise is applied, RAW Details is automatically included in the process. So I’m not quite sure how Denoise is considered to have the lowest impact in terms of additional data. As far as I can tell, you can’t apply Denoise without also applying RAW Details — or am I missing something?
Think about JPEG compression… if there’s less noise, data compresses better. So while adding raw details takes up a lot of space, once Denoise is applied, the data can be losslessly compressed better, so it takes up less space.
It’s great that LR has simplified and speeded up workflow time by the new updates.
I’m finding two things disappointing though:
1-The reflection removal tool seemingly only works if you have a reflection covering the whole image. When I used it on windows containing reflections which were just a part of the image there was no removal at all.
2-Because AI is powering the de-noise it has a tendency to subtly change things, particularly faces. They don’t quite look like the person anymore. This is something I already noticed in other AI based de-noise apps (Topaz for example). I know the changes can be ‘throttled back’ via slider, but I’m already seeing images of people on social media who don’t quite look like themselves. I suspect a lot of users won’t bother with adjusting.
Yes, Reflection Removal has been trained by a very targeted data set, so it mainly works when you’re close to the glass. There’s potential to create a similar tool for reflections that are just a small part of the image, but that will need a different data set for training.
That’s interesting about Denoise… the tool has been around for a long time as part of Enhance and I haven’t seen other reports, so it would be interesting to know if this is something new you’re seeing. Either way, it would be worth uploading examples to Adobe to help them improve it.
Victoria, in the blog post you mentioned the following:
“In Lightroom Classic, the new pixel data is stored in the .lrcat-data file alongside the catalog.”
Does this mean we need to backup the .lrcat-data file to be able to restore and see our images with the new Denoise or Super Resolution applied?
Yes, you should be already, as it also includes masks and generative remove repairs. It’s included in Lightroom’s catalog backup.
Great – I didn’t know it was included in Lightroom’s catalog backup.
Thanks!!
Hi Victoria,
Thanks for all the info above. I’ve been playing around with the new no DNG denoise feature which is a massive improvement. However I write everything to XMP and store my photos on two external ssd’s one master & the other backup. Is there a way to only have the extra Denoise data only write to XMP and save the data only to the sidecar file on my external drives? I don’t want the extra Denoise data clogging up my catalog as that’s stored on my MacBook which has a far smaller drive than my external ssd’s do. If not is there a way to delete these extra Denoise data files stored in the catalogue periodically? Also in my tests I’m only getting a sidecar file between 1.5 & 3 mb on my external ssd with Denoise selected which also automatically selects raw details.
Many thanks
No, you can’t delete the Denoise data from the lrcat-lrdata, but the good news is it’s only about the same size as your xmp’s, so smaller than the ones I tested.
Your other option would be to use Lightroom Desktop’s Local mode, which only uses xmp without a catalog, but there may be other Classic features you rely on. Could be worth considering if the catalog space is a deal breaker though.
Hi Victoria,
thank you for the information and the nice article. Do you heard about the new culling features Adobe will provide in the next months? Do you know, if this will be included in Lightroom Classic as well and when Adobe will release it?
Best regards, Thomas from the Excire Team
Due to non-disclosure agreements, we can’t share anything beyond what’s already been made public by Adobe in their latest blog post. Here’s the sneak peek video: https://adobe.prf.hn/click/camref:1011lrifT/destination:https://blog.adobe.com/en/publish/2025/06/17/create-ideate-faster-with-new-creative-cloud-firefly-innovations
Thank you and looking forward to it.
All the best, Thomas
Very Good
If we are using full size preview to carryout AI options on LrM, does that mean we need to keep the full size previews for future use, printing etc. This also mean additional memory is utilised and need arises to have larger capacity iPads.
What would happen if the full sized previews replaced by switching to smaller ones after editing? Would we loose the AI edits?
Assuming the photos are synced to the cloud, the full resolution repair would get synced to the cloud, and when you later swapped back to a smart preview, you’d see a downsized version of the repair.
So the short answer is, no that’s fine. The original would only be needed while calculating the Remove repair, then you can swap back to smart preview size.
Thanks Victoria, I will put it to test by selectively re-do some old photos.
Under “Other Changes”, you wrote: “Identity Plate (Windows only) new/updated text Identity Plates can only use a single text style”, but under “New bugs…” you mention that this was a bug. I don’t think you intended to include that as a “change” (unless we’re trying to tell people ‘It’s not a bug, it’s a feature!’ 🙂)
They made an intentional change (which they called a new feature), and in the process, they created an additional bug that wasn’t discovered until after the release. Oooops!
I just noticed in LrC that both Distraction Removal features (Reflections and People) cannot be selected if the picture is synched in the cloud. Is this a bug?
probably it’s ‘as intended’. These tools most likely (and unfortunately) use cloud AI processing and not local ML models (like masking does), hence cloud requirement.
Good news for you, John… although it uses AI, it’s run locally.
oh, thanks for the info! Will get to check it out in a few days. Was almost sure Adobe locked it down behind cloud AI, so I am glad to be proven wrong in this matter.
That’s unexpected Guiseppe. It should work whether the photo’s synced or not.
Guiseppe, are you on Windows or Mac? I’ve had reports from 2 other people seeing the same thing, so I’d suggest adding your comments to this bug thread: https://community.adobe.com/t5/lightroom-classic-discussions/people-and-reflections-removal-features-are-greyed-out/td-p/15375297
There’s a possible fix now on this thread: https://community.adobe.com/t5/lightroom-classic-discussions/people-and-reflections-removal-features-are-greyed-out/m-p/15376026#M406715
Please do let us know whether it solves it for you or not. If not, we might need to know which graphics card you have, as that’s the second most likely suspect.
That worked, thanks.
I’m on a Mac and I noticed it happened on pictures which I previously edited on the iPad and moved to my main catalog. Other synched pictures were not affected.
I am running LrC on a Mac Studio and also noticed the greyed out Reflection/People removal feature. The toggle referenced in the linked thread does serve as a work-around, but I have not worked out under what circumstances the feature gets disabled. I also note that People detection does not always ID all or even some of people in a given image. Looking forward to some best practices for that feature.
An excellent day. Waited a while but the new Denoise AI for LrC was well worth it.
The update removing the DNG step for Denoise significantly decreases the time taken on a fast GPU. On my 4080 Super it took about the same time (~6 seconds) to Denoise on the GPU as it did to save and add the DNG to the catalog, so the total time has decreased by around 50%, plus saving of disk space for the DNG which was around 2x the RAW size, and no need for an image stack in the catalog.
An additional surprise benefit is that the Denoise slider updates the processed image almost instantaneously, allowing for very fast tuning of the amount applied.
Thank you Adobe!
Missing is the keyboard shortcut as it’s now just an isolated checkbox item.