Skip to main content
Rikk Flohr-Retired
Adobe Employee
Aug 13, 2024 2:32 PM UTC
Question

P: Generative Remove Feedback (Lr Classic & Lr Eco)

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 version
  • System details
  • Example image(s) if you wish to share

Our team continually monitors this thread to track issues for future improvement. Thanks!
 
Lisa Ngo: Lightroom Product Manager

 

Posted by:

1682 replies

Participant
Jul 5, 2025 12:53 AM UTC

Sorry, but the "Remove" tool is worthless.  Moreover, for generations we have called it "spotting."  Adams, Cunningham, Van D---, E. Weston, and way before, all called it "spotting."  The spotting tool in LRC is so convoluted that I just export to my image file, and from there "spot" using the file tools.  The file reader makes immaculate, two step removals.   

Translate
johnrellis
Legend
Jul 5, 2025 6:41 AM UTC

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]

 

@TimothyFY2025: "The spotting tool in LRC is so convoluted..."

 

 

Are you talking about the Heal tool?  What's convoluted about it? I just used it to remove dust from several dozen slide scans this afternoon, and it was dumb simple -- click on a dust spot and it disappears.

 

Translate
Participant
Jul 3, 2025 9:49 PM UTC

Half of the time it clones even though it's on the remove setting. Def not what I'm paying good money for.

Translate
johnrellis
Legend
Jul 3, 2025 11:07 PM UTC

@Steven31501606e2fj: "Half of the time it clones even though it's on the remove setting. Def not what I'm paying good money for."

 

1. Uncheck Detect Objects before brushing a selection -- it doesn't work well, especially with skinny objects and along the edges of photos.

2. See this short article for how to remove objects more reliably:
https://www.lightroomqueen.com/generative-remove-replace/

Most complaints about Remove are addressed in the article. But if it doesn't help, please attach a full-resolution JPEG exported from the unmodified original photo (not a screenshot). With nearly every one of the many dozen problem photos posted here, we've been able to show how to quickly remove the desired objects.

Translate
Participant
Jul 2, 2025 1:07 PM UTC

A remoção funciona bem mas passado algum tempo desaparece.

Translate
johnrellis
Legend
Jul 2, 2025 7:38 PM UTC
Participant
Jun 29, 2025 2:28 PM UTC

I have an issue with the removal tool AI genrator.

I use it on some photos and I come back to the first photos, all I did is gone.

And if i do not come back to the photos and just do an export, it is the same: all I did is gone.

I have the same issue with reduction Noise with AI.
And some times when I use this tools, i have an error message:

?:0 attempt to index a nil value

I have a Apple M4 Pro and the latest version of lightroom Classic.

Translate
johnrellis
Legend
Jun 29, 2025 4:16 PM UTC

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]

 

@Thomas Bertini, the orange-circle icon in your screenshot:

 

indicates that LR can't write the <catalog>.lrcat-data file for some reason, either because LR has corrupted it or there is a permissions issue. LR stores computed AI settings in that file. Try these steps:

1. Do the menu command Help > System Info. If you're not on the latest version (currently 14.3.1), do Help > Updates.

2. In LR, do Edit > Catalog Settings > General > Show. That will open Windows File Explorer / Mac Finder on the current catalog folder.

3. Exit LR.

4. Move the file <catalog>.lrcat-data to the Desktop.

5. Start LR.

6. In Library Grid view (not Loupe view), select all photos and do Photo > Develop Settings > Update AI Settings. That will recompute all the AI masks, which could take a while. 

 

Recently, however, these steps haven't worked for many people.  If they don't work for you, I recommend starting a new thread rather than continuing the discussion in this very crowded thread.

Translate
Known Participant
Jun 29, 2025 4:40 AM UTC

Seriously, you guys have to make your system not have these false flags of 'guidlines'. It actually did allow me to to use the generative Ai remove in this photo on the forehead. But it then wouldn't do anything else on the face. 

Translate
Participant
Jun 27, 2025 2:40 PM UTC

Is there a way to view and select previous AI generations after regenerating multiple times - similar to Photoshop? If not, will this issue be addressed in future updates?

Translate
johnrellis
Legend
Jun 28, 2025 12:03 AM UTC

@Torrey G: "Is there a way to view and select previous AI generations after regenerating multiple times - similar to Photoshop?"

 

LR doesn't have that feature like in Photoshop. However, when you're looking at more than the first 3 variations and see one that you think is plausible, make a snapshot by clicking the + button in the Snapshots panel. Then you can later review all the saved snasphots very quickly. I use this fairly often.

 

"will this issue be addressed in future updates?"

 

Unfortunately, Adobe rarely discloses their plans. There have been a few requests for such a feature in this thread (where Adobe wants Generative AI Remove feedback), but it's hard to tell precisely how many because there are so many unrelated posts here.

Translate
Participant
Jun 27, 2025 11:36 AM UTC

Hello ! Can we make a shortkey to turn on and off the  "USE Generative AI" ?

Translate
johnrellis
Legend
Jun 29, 2025 4:53 AM UTC

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]

 

@kovacs29009990eryo: "Can we make a shortkey to turn on and off the  "USE Generative AI" ?

 

The shortcut is Opt / Alt Shift G. You can see all the Remove shortcuts by clicking the miniscule "?" button in the upper-right corner of the Remove panel:

 

Translate
Participant
Jun 26, 2025 5:35 PM UTC

Seria interessante, ter uma opção expecifica para remover frizz, isto é, fios de cabelos soltos, isso facilitaria muito,
crianda uma interface entre a IA de mascaras com a remoção generativa.
provavelmente tem uma opção de ajuste manual caso necessario. 

Translate
Participant
Jun 25, 2025 10:21 PM UTC

Hello, 

 

I keep getting error messages with Generative AI removal as it keeps saying "Something went wrong.  Please try again."  I close the app for 10 minutes, reopen it, try again and still gives me error messages.  It was not acting like this for the past 3 hours as it was working properly.  Now it won't because of high demand or with no reason at all.  I need this resolved as I'm editing various photos that needs certain objects removed.

Translate
Known Participant
Jun 26, 2025 12:09 AM UTC
The program is very puritanical! It is so strict (for good reason) that
it's almost from the 1800's! But, in 99.9% of the cases, does an amazing
job — and keeps incrementally improving.


--
Sent from Gmail in PC
Translate
_jdj_
Participant
Jun 25, 2025 6:28 PM UTC

Using geneartive remove in LRC 14.4. The generated areas are quite low-rez compared to the original photo. Here I have removed an area to the right and it is clearly not as "crisp" as the left part.

 

Translate
johnrellis
Legend
Jun 25, 2025 6:40 PM UTC

@_jdj_: "Here I have removed an area to the right and it is clearly not as "crisp" as the left part."

 

Many have observed here that the replacements made by Generative Remove sometimes don't match the photo's tone or noise. To get better matches, these techniques sometimes help:

1. Adobe recommends applying Denoise before Remove. This can reduce the noise, making it more likely the replacement will match.

2. The replacement patch supplied by Adobe Firefly has a maximum size of 2048 x 2048 pixels. If the selected area in the photo is larger than that, then the replacement patch gets upscaled (and blurry). Try removing smaller selections if possible.

3. Conversely, try making a larger selection, even including the entire background. Upscaling of the replacement sometimes won't be noticeable then.

4. Sometimes there's a distinctly visible boundary where the tone or noise don't match. You can often use the heal tool around the boundary to get better feathering and make it less noticeable -- apply Heal in small brush strokes. Or use a Brush mask with maximum feathering, dropping local Texture, Clarity, and Sharpness to their minimum values. Sometimes, making a very raggedy selection around the object makes the boundary less noticeable.

5. For grain/noise in particular, see this post for how to ameliorate the problem by adding the grain back or reducing the grain:
https://community.adobe.com/t5/lightroom-classic-discussions/p-generative-remove-feedback-lr-classic-amp-lr-eco/m-p/14917497#M382464

Translate
_jdj_
Participant
Jun 25, 2025 7:40 PM UTC

Ok - I did not know about the 2kx2k limitation; that is probably the cause. The background at the time of the shoot was not wide enough so I removed a narrow but very high edge of the photo. I will remove more "squarish" parts in the future!

Translate