Generator · pre-upload
Strip the C2PA credentials from DALL·E images
DALL·E and ChatGPT image exports often ship with a C2PA manifest attached — the first thing a platform reads, and therefore the main thing to remove.
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.
Mostly C2PA Content Credentials
Different export paths can write different things. The reliable approach is to inspect one sample before batch processing.
Where it writes
| Location | Notes |
|---|---|
| PNG export | C2PA manifest (JUMBF) |
| JPG export | Can carry C2PA as well |
| Platform reading | Meta platforms check C2PA first |
Pre-upload checklist
- 11. Clean C2PA — it is on by default
- 22. Clear XMP at the same time, in case it is read as secondary evidence
- 33. Inspect the result once more to confirm
- 44. Upload that copy, with no editor or forwarding in between
Common traps
- Cleaning only half of it — C2PA off, while the tool name stays in XMP
- Saving the file once more in another app after cleaning
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
Is C2PA always present?
Most exports have it, but not every path does. Inspecting the file is the reliable way to know.
Can the platform still tell after C2PA is gone?
If it relied on C2PA alone, no. It may also use a pixel watermark or a classifier.
Does it affect image quality?
No, only a data block is removed.