P: New AI-powered Generative Remove (Early Access) available across all surfaces.

[Rikk Flohr: Photography]

This post applies to Lightroom Classic and the Lightroom Ecosystem products.
Post Camera Raw feedback here

The Lightroom team is sharing an early look at Generative Remove, which makes it easier to remove unwanted objects and distractions, even on complex backgrounds, with a simple brush stroke. Generative Remove is powered by Firefly AI.

How to use Generative Remove on a desktop:

• You can find Generative Remove under the newly renamed Remove panel (aka “Heal”).
• Make sure the “generative AI” checkbox is enabled before you start brushing (note: when unchecked, Lightroom will use Content-Aware Remove to fill your brushed spots). 
• By default, you will be given a moment to refine your selection with an add or subtract brush. Remember to include shadows for a more accurate result! You can also skip this step by holding down ‘CTRL’ on windows or ‘CMD’ on mac as you finish your brush stroke. 
• Once you’re ready to apply and have accepted the terms, Generative Remove will use Firefly AI to remove your distractions and intelligently fill in the space that’s left by the removed objects. 
• Note: stable internet connection is required to use this feature.
• Generative Remove also lets you choose from multiple variations, so you can pick the one you like best, giving you full creative control. 
  
  Checkout the FAQ and Best Practices

Please give it a try and share feedback and/or report variations in this community forum. It would greatly help to include details like which app you are using (i.e., Lightroom Classic or Camera Raw) and other system details. Our team will continually monitor this thread to track issues to improve the future experience.

Lisa Ngo: Lightroom Product Manager
Posted by: Rikk Flohr 

Update:

Here are some tips if you are having issues with the feature replacing your object instead of removing it. 

• Enlarge your selection - if your brush stroke is too tight, you will have unexpected results.
• Remember that removing an object means painting over it, its shadow, its reflection, and any non-contiguous pieces. If you leave behind a shadow, a reflection, or a disconnected piece (e.g., a hand on a shoulder), the AI will attempt to create something to cast the shadow, reflect, or complete the unbrushed discontinuous item. You can avoid these issue by following the guidance provided in this linked tutorial. https://www.lightroomqueen.com/generative-remove-replace

The recommended order for applying edits is:

1. Denoise 
2. Heal (includes Generative AI Remove)
3. Crop (includes traditional Cropping, Lens Correction, Transform, or any operation changing the geometry of the image)
4. Edit
5. AI Selective edits
   
   If you deviate from that, you may see the removed object remain as a ghost image. If this occurs, you will have to use Update AI Settings, which can be found under the Develop module 'Settings' menu.

[Corniger]

Since it's called remove and not replace, remove should be the only thing it does.

It's nice we get to drive traffic on the Lightroomqueen Blog, why are there no Adobe resources with clear instructions? They should know best....

[Victoria Bampton LR Queen]

It's nice we get to drive traffic on the Lightroomqueen Blog, why are there no Adobe resources with clear instructions? They should know best....

By @Corniger

My post gets straight to the issues real people are tripping over, so it's getting reposted a lot. If you prefer Adobe resources, try this from Julieanne Kost https://www.youtube.com/watch?v=BkXDukmBNcg and this Adobe help document https://helpx.adobe.com/lightroom-classic/help/remove-tool.html

[Corniger]

Thanks for the links!  I've also exhausted various YouTube content that didn't work for much simpler assignments, thus looked and sounded to me like influencer marketing, using specific images that in fact do work.
I'm not complaining about outsiders like you doing Adobe's job, just about the fact this is even necessary. Without said outsiders, users would be lost. If at least Adobe themselves would link to content that does have correct information! I have, in fact, literally wasted years on blogs and YT (and also paid learning resources, as well as during my studies...) learning retouching technique that was simply BS all along, so I'm always wary.  Adobe Help alone is full of deprecated or imprecise info. 

[Victoria Bampton LR Queen]

You're welcome @Corniger. Julieanne works for Adobe and is very knowledgeable, so her stuff is always a good bet. The help docs are a bit more hit-and-miss, although we do try to report issues when we find them. It's a full-time job trying to keep everything up to date. Whereas I (and a number of the other experts in this thread) have been doing this from the start, very few Adobe staff have been around so long, so it's more difficult for them to spot issues in older material.

[johnrellis]

@Corniger, I've reposted the link to the Lightroom Queen article because I've found it's the best explanation to date about how to use Generative Remove. I've reposted it many times here because LR is asking users to provide feedback here, and no one is going to slog through 1300 such posts, and it's apparent that many (most?) don't read the top post very carefully (which summarizes best practices and links to the same article).  I'm not a social media "influencer" and I have no vested interest in the Lightroom Queen, though I participate in the high-quality forums there.

[johnrellis]

@Corniger, "Since it's called remove and not replace, remove should be the only thing it does."

Having now worked with hundreds of examples of my own and those posted here, I've learned that the closer you look at the intuitive remove/replace distinction, the squishier it gets. A few examples:

- There's a visually distracting tree in the background that you want to "remove". Remove "replaces" it with a less-distinctive tree that blends in with the nearby trees.

- On a bookshelf behind the main subject, there's an ornament next to books with a distracting glare of bright sunlight that you want to "remove". Remove "replaces" it with a row of books matching the pattern of other books on the same bookshelf.

- A woman is wearing a pair of very unflattering glasses, through which you can only partially see her eyes, and you'd like to "remove" the glasses. Remove "replaces" the glasses and eyes with a different set of eyes (no glasses) that are more visually distinct, but you have to choose which pair of eyes (different sizes and shapes, some frowning, some wide open) best matches your intentions.

In nearly all the reports of remove/replace I've worked with in the forums, where users have posted the original photos, we've gotten good "remove" results by following the best practices in the first post and the Lightroom Queen article. When users don't follow those best practices, Remove often generates a replacement that tries to match the remaining unselected pixels containing shadows, reflections, edges of the object to be removed, etc., so the replacement has a higher likelihood of looking more like what was intended to be removed. 

It can be fussy following those best practices: Remove sometimes notices subtle shadows, reflections, or unselected discontiguous parts of the object we don't initially notice and generates a replacement that looks similar to what we want to "remove". I struggled to remove a sailboat from the water until I finally noticed there was a distinct though rippled reflection of it a fair bit below in the picture, and Remove was "replacing" the boat with other boats matching the reflection.  I'm glad that Remove forced me to notice the reflection.

And the "Early Access" (beta) ensures there are rough edges in the user interface making it very likely users won't select all of the necessary bits -- pixels that have been cropped out explicitly or implicitly by crop, lens corrections, transform, and the hidden initial cropping of borders that LR does with many cameras, and the weird behavior of how discontiguous brush strokes behave differently from contiguous brush strokes.

[Corniger]

Thanks a lot for your input and explanations - also, very much appreciated.

Still, there's the semantics between "remove" and "replace". Yes, in fact, when I remove an object, it is practically being replaced by an "empty" background. Visually, it has bee removed. And that's how I,  and apparently many others, would interpret the term, on linguistic grounds. I don't want to nitpick around this any further, but that's like picking the eraser tool and instead, it paints over the erased item - you can't see it anymore, it has been erased.

I have followed all those suggestions and postings thoroughly, all the input I could get. A few easy examples:

I shot an event recently that had lots of messy clutter in the background.

• A remote control on a wall,
• a metal rod leaning against the wall, roughly as thick as a thumb,
• a water bottle lying on a chair behind a laptop,
• a water bottle standing in front of the projection wall,
• a bluetooth speaker standing in the same area,
• an espresso machine as well.    

Single brush stroke remove always worked for:

• both water bottles (even the one behind the laptop on the chair, which I didn't expect at all, complicated as opposed to a BT speaker on a white cabinet in front of a white wall)
• the remote 

Single brush stroke remove sometimes worked for:

• metal rod - it was frequently just being made thinner, skewed, tapered, a dark blotch. All those images very very similar, on some it worked on first try. Eventually, after deleting the remove event and retrying (always 1 stroke, form inside the frame to outside and all the way down), the rod disappeared

Area removal never worked for the BT speaker and coffee machine. I selected an area 2-3 times the size of the item for the BT speaker and encompassing all shadows and more for the espresso machine. I always got a smaller/different BT speaker (or "some object") and the same result for the espresso machine, sometimes a colorful flower vase or some fantasy objects. The bottle, standing in exactly the same area on the same piece of furniture disappeared immediately.

I repeatedly tried removing the object that just didn't want to go, thoroughly painting over 3-4 times in one stroke, not to miss a bit. Not a chance. In Photoshop, I would have the adjacent empty area, copy, paste, blend, gone.

That's why I'd prefer "Remove" and "Replace" separated and unambiguous.

[Harv25727449l7y4]

Exactly!   Sometimes it works amazingly well.  But I just now had this situation:

- photo of old Model 'A' Ford at a car show - front view with side-mounted spare tires/wheel

- exhibitor had placed a Teddy bear on the running board leaning on the spare wheel

- I selected the Teddy bear using Generative Remove and the Teddy bear was replaced by am image of a young boy.  I have no idea with the kid's image came from! 

[Ian Lyons]

@Harv25727449l7y4 

Typically, the model will use replace when the object and any shadows, projections or reflections have not been fullly selected/masked.

You can see how to avoid this in the below linked tutorial.

https://www.lightroomqueen.com/generative-remove-replace/

[Corniger]

What I don't understand is the semantics of the tool. There should be a "Remove" and a "Replace" tool then. Sometimes, I have to go through the 3 output variations just to find a perfectly removed item on Nr.3. "Remove" should be unambiguous to the AI.
Other than that, it's coming along nicely. As opposed to "Generative Expand" in PS, which is a waste of time & resources most of the time, but that's another topic!

[Fernando33119179d9zc]

Brutal!!!

[sfazio12]

Love how it removed spots, but yesterday the spot removal no longer is removing to bug in my images.

[AnaLima]

A Remoção Gerativa também permite que você escolha entre várias variações, porem nao permite ainda que voce diga o que deseja , fiz um teste e ele me trouxe muitas variações mas nenhuma delas estava a contento.

[JBedfordPhoto]

Great start! I love the addition of this tool to LRCC 13.3 - amazing that Adobe was able to slap this technology onto RAW files. 

The first improvement that I see could be made is a feathering option for the selection. The transitions under light fall-off are still quite hard-edged and noticeable. 

[Barry Young]

Better seams and outlines is something we are working on.

Barry

[umlautnord]

This is very good to hear.

[Ben Willmore]

Sweet!

Doesn't work to start by defining an area with Clone tool, switch the already applied retouching to Remove and then turn on the Generative AI checkbox. It presents the usual progress bar, but does not produce a generative result. (LRC on M3 Macbook Pro running Sonoma on HEIC panorama from an iphone)

Would love to see you allow us to use it to fill the empty/white areas at the edge of an image after appling Transform features such as upright, but it currently can only work within the original image area.  

[JustGuy]

Hi, started using Generative remove today.  I had taken a series of images and found that the sensor on a camera, not often used had been fungussed!? It was a great day and was disappointed that all the images were wasted. However, I found that Generative Remove has cut the work down in this instance quite dramatically, and saved the day, but it still onerous. Luckily the areas affected are block colour but in the more detailed areas I found that I needed to use a much smaller cursor size, but it worked, after a fashion. 

Adjustable Feathering the cursor might help. I also had a glitch (hockey-stick glitch) every so often (pictures attached) which I could not explain - just went to undo and waited a few seconds.  In addition, would it be possible to save the actions of Generative Remove as a mask that could be used on the other imagesof the same batch? Thats all. Thanks

[Ian Lyons]

Using Generative Remove for spot removal is not recomended as it is much slower than using the standard heal tool.

Please refer to the FAQ provided by Adobe for guidance on whcih of the Remove tools is bested suited to particular tasks.

https://helpx.adobe.com/lightroom-cc/using/generative-remove-faq.html

[Alejandro37602070ha2a]

Hola, solo queria saber si esto consume creditos firefly porque parece que cada vez que lo uso en lightroom esta consumiendo. es correcto? 

[Alain37654892v42f]

Merci pour la description de la procédure à suivre, le résultat est là et plutôt convaincant ! 

[ThierryH]

Great feature. I would love feathering, as well as the object rectangle selection for this tool. After a few times the Refresh option is missing.
I don't see any information in the documention/responses about what de-selecting the checkboxes "Generative AI" and "Object Aware" do. Is it correct that you must also uncheck the latter to remove that person/object/etc.? Maybe some people do not see that. Being aware of selecting everything etc., I had an issue with removing an intruding elbow from the border on a non-cropped image.

Selecting a person's glasses with "Object Aware" off, I get the person without her glasses which is the purpose. However, the person eyes looks at the camera now, from an extreme angle and the eyes are weird (too big, ugly, angrilly) every time. There should be at least some variations with the eyes looking as the original.

[johnrellis]

@ThierryH: "I don't see any information in the documention/responses about what de-selecting the checkboxes "Generative AI" and "Object Aware" do. Is it correct that you must also uncheck the latter to remove that person/object/etc.?"

No, the two options are independent. The Generative AI option says to use the new Adobe Firefly service to generate a replacement for the selection.   The Object Aware option controls how to make the initial selection -- when unchecked, it's exactly what you've brushed, but when checked, it uses the same algorithm as Object Mask to identify an "object" that becomes the selection to be replaced.

[johnrellis]

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

@ThierryH: "I had an issue with removing an intruding elbow from the border on a non-cropped image."

Generative Remove did a very good job of quickly removing the elbow from the JPEG you uploaded:

 

That indicates you were working with a raw to which Lens Corrections or Transform had been applied, or in less frequent cases, the Camera Raw engine had automatically cropped a border of 8 - 12 pixels around the edge. In all cases, Remove is (confusingly) looking at those hidden pixels. Temporarily disable Lens Corrections and Transform and then do the remove.  See here for more details:

https://www.lightroomqueen.com/generative-remove-replace/

If that doesn't help, upload the original raw to Dropbox, Google Drive, or similar and post the sharing link here.

[johnrellis]

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

@ThierryH: "Selecting a person's glasses with "Object Aware" off, I get the person without her glasses which is the purpose. However, the person eyes looks at the camera now, from an extreme angle and the eyes are weird (too big, ugly, angrilly) every time."

With your low-resolution JPEG, I got better results using Object Aware.  I looked at over 50 variations, and here are some of the better ones (hard to know if they'd be acceptable on the full-resolution raw):

        

The Refresh button never disappeared for me, but maybe there's a difference when using raws.