Generator · pre-upload
Lightroom AI Denoise and C2PA
AI Denoise is a routine quality step, but on export it is recorded as AI enhancement and written into XMP, sometimes C2PA — and the real photo gets labelled.
On-device/No upload/Quality unchanged/No sign-up
Drop images here, or click to choose
JPG, PNG, WebP, AVIF, HEIC · 15 MB each · up to 30 per batch
You can also paste a screenshot with ⌘V / Ctrl+V
Cleaning options
Want to look first? Themetadata inspectorlists every field in the file, so you can see exactly what is there before deciding what to strip.
AI Denoise and Super Resolution leave XMP and C2PA markers behind
Different export paths can write different things. The reliable approach is to inspect one sample before batch processing.
Where it writes
| Location | Notes |
|---|---|
| XMP | AI-enhancement fields and history |
| C2PA | Some versions write content credentials |
| EXIF Software | The Lightroom version number |
Pre-upload checklist
- 11. Use the AI-only mode to keep the camera settings
- 22. Or clean everything with the defaults
- 33. Verify once before delivery
- 44. Upload that copy, with no editor or forwarding in between
Common traps
- Re-exporting after denoising writes it all again
- The default clean also removing the settings your client wanted to see
If it is still flagged after cleaning
That means the trigger was never in the file metadata. It could be an invisible pixel-level watermark, the platform's own visual classifier, or history held on the platform side. None of those live in the metadata layer, and cleaning again will not change them.
The full boundaries are in thedisclaimer; if you just want to confirm the file really is clean, use thewatermark check.
Common questions
Does AI Denoise count as AI generation?
Technically it is not generation, but the metadata does not distinguish the two.
How do I keep the lens details?
Use the AI-only mode, which keeps the geometry and exposure tags.
Does it affect quality?
Cleaning does not touch pixels.