Low-resolution Ai remove

Forum|Forum|6 months ago
September 5, 2025
1 reply
279 views

For some time now, the Generative AI remover has been using horribly low-resolution images in the areas it changes. In its current state, it’s not usable.

Windows

A

Aleke

Community Manager

Hi @prlolos32185349lsx9, welcome to the community!

Could you tell us a bit more about what you're experiencing? Which version of Lightroom are you using? Does this issue happen with every generation, or do the variants it creates seem to be better quality?

Also, if you could share your System Info, that would be super helpful. You can find it in Lightroom by going to Help > System Info. Just copy it into a text file and attach it here, or feel free to share it via Google Drive, WeTransfer, or any other file-sharing service you prefer.

Thanks so much! 😊
Alek

*(If you mention me with an @, like @Aleke, I’ll get a notification and can respond faster.)*

P

prlolos32185349lsx9Author

Participant

Hi @Aleke , thank you for the quick response. I always use the latest version of Lightroom (not the Classic one). I first noticed this problem in September, and I’ve also seen it in Photoshop: if I use AI to remove something or uncrop an image to make it larger, the added area looks like 360p. I thought it was a temporary bug and didn’t use AI Remove much until now, but it happens every time I use AI Remove or uncrop something. Here are my system specs:

Lightroom version: 8.5.1 x64 [ 20250821-1548-c6398d5 ] (Aug 21 2025)
NGL Version: 1.41.0.11
WF Version: 7.4 a9dfbad
VF Version: 1.0.154
HIL Version: 40501
CAI Version: c2pa-c/0.6.0 c2pa-rs/0.46.0
PH Version: 5.2.3

Operating system: Windows 11
OS Version: Windows 11 Home (2009)
Application architecture: x64
System architecture: x64
Computer model: ASUS System Product Name / 13th Gen Intel(R) Core(TM) i9-13900KF
Logical processor count: 32
Processor speed: 2.9 GHz
Real memory available to Lightroom: 65348.9 MB
Real memory used by Lightroom: 4260.3 MB (6.5%)
Virtual memory used by Lightroom: 9920.7 MB
Memory cache size: 4814.4 MB

Internal Camera Raw version: 17.5 [ 2318 ]
Maximum thread count used by Camera Raw: 17
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 1552MB / 30626MB (5%)
Camera Raw real memory: 1558MB / 65348MB (2%)

Displays: 1) 2560x1440, 2) 3840x2160, 3) 2560x1440
System DPI setting: 144 DPI
Dark Mode: No
Desktop composition enabled: Yes
Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No

Graphics Processor Info: DirectX: NVIDIA GeForce RTX 4070 Ti SUPER (32.0.15.8108) - 15.5 GB
Graphics Processor Detail: loaded: Yes, supported: Yes, compute: Yes, init: I4_GPU4, hard: success, soft: success, al: Yes, dl: No
OS Media Capability: true

Anshul_Saini

Community Manager

Hi @prlolos32185349lsx9, thank you for sharing the detailed system info. To dig deeper into what’s happening with AI Remove, could you please:

Please share a sample file after you have made all your edits so we can run Generative Remove on the same image and compare the results.
Let us know specifically what edits you wanted to achieve (for example, object removal, uncropping, background fill, etc.), so we can see where the quality is breaking down.
If possible, record a short screen capture of your workflow while applying AI Remove. That will help us understand exactly how you’re using the tool and where the output starts to look low-resolution.

This will give us the best chance to reproduce the issue and investigate why the generated areas are turning out blurry or low quality.

Thanks again for your patience, and looking forward to your files and recording.

Best,

Anshul

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded