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

@louloubell: "somehow there should be a warning/advice to those who don't know not to crop before trying to remove or they will be as frustrated as many of those posting here."

Agreed. There are even more confusing situations that will silently crop pixels and confuse Remove, such as applying Lens Corrections or using one of many cameras for which LR automatically crops a 10 - 16 pixel border from the photo (that you can't stop).

@gotr903: "Im able to select and it gets shaded out    when I hit apply it does not disappear just adds a white line around it?"

Set the Opacity slider to 100. Does that fix it?

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

@Amy23951275i2q6: "It seems to just replace it with similar railings, but I want the whole railing gone"

This is an example of Big Brother Adobe not allowing you to show an oblivious, love-struck couple about to fall off a deck without railings. 😆 

More serously, after a lot of experimentation, I think this is an example of where you need to select all the disconnected pieces of the object and any shadows it casts. Otherwise, Remove will generate a replacement that matches the remaining pieces and shadows.  This tip appears in the FAQ at the top of this thread and in this more extensive article:

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

In this case, you have to select all the railings and the subtle shadows they cast on the deck:

Also, I found good replacements by selecting all the water appearing between the railings.  Since I'm working with your screenshot, I can't tell how well this will work on the full photo. Also, be sure to undo any Crops, Lens Corrections, or Transform before applying Remove.

If you're still having trouble, please attach a full-resolution JPEG exported from the unmodified original photo.

How does one unsubscribe from this forum thread without unsubscribing from all Adobe communications?  I unchecked the box that says "Email me when someone replies" but that didn't work.

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

@waltweiss: "Your "censorship" has on several occasions refused to function because of supposed guidelines.  In most cases it was people wearing bathing suits."

Do you get any kind of notification when Remove doesn't remove a person in a bathing suit? There haven't been any other reports of this here.

I downloaded about 20 beach photos from Google of men and women, half in skimpy bathing suits and half with full-frontal nudity, and each time Remove did a good job of removing them. For example:

More likely, you're encountering the "replace instead of remove" issue.  See this 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, so we and Adobe can see the issue in detail. With nearly everyone who has posted a problem photo, we've been able to show how to remove the desired objects.

@MarkNF: "the software generated different versions of what I was trying to remove and did not actually remove anything. "

See this 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, so we and Adobe can see the issue in detail. With nearly everyone who has posted a problem photo, we've been able to show how to remove the desired objects.

@MARCEL34521755ixpi: "if you crop the photo before using it, the result is much less good, small parts of the object remain."

Adobe explicitly designed Remove to look at the entire photo, so if you use Remove on a cropped version, you may not be selecting all the pixels of an object, and Remove will generate a replacement that tries to match those remaining pixels.

Their thinking is that if you apply Remove to just the cropped pixels and then change the crop, there won't be odd bits of objects left un-removed.

But this behavior has confused many, many people here thinking that Remove doesn't work very well ("Photoshop works better"). Cropping is the first thing most people do in their workflow.  

So some of us have proposed either that Remove looks only at cropped pixels, or that Remove generates a warning when Crop, Lens Corrections, or Transform have been applied, or that when the Remove panel is open, Crop, Lens Corrections, and Transform are temporarily disabled.

@F1XX: "Does this work also in the white corners you get with perspective correction/rotate (when you do not constrain crop to maximize image area)?"

Unfortunately not -- those corners are off-limits to all LR commands. You'd have to fix them in Photoshop.

"but post headline says "across all surfaces"."

That's Adobe's internal jargon for all the products in the Lightroom family: Classic, Desktop, Mobile, Web, Camera Raw.

@Dirk3844418208z3: "If I removed something and then I do the Denoice AI option it comes back with something strange I already wiped with the AI option."

According to the FAQ posted at the top of this thread, Adobe recommends this order for applying the tools:

"The recommended order for applying is: Denoise; Remove (includes Generative AI Remove); Crop/Edit; AI masking. If you deviate from that you may see the removed object remains 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."