File metadata, accurately described
AI Metadata Remover
Find and remove supported prompts, workflows, model names and generator records embedded in image files.
Drop an image here
JPEG, PNG or WebP · Up to 25 MB
How it works
Useful privacy, without privacy theater.
Removing file metadata does not remove pixel-level watermarks and does not guarantee that an image will evade visual AI classifiers.
- InspectRead supported metadata locally.
- Clean and verifyReparse the output and compare image payloads.
What it removes
- AUTOMATIC1111 parameters: prompt, negative prompt, seed, sampler and model
- ComfyUI prompt and workflow JSON, including compressed PNG text
- Generator names in Software, CreatorTool and the IPTC digital source type
- XMP packets and comments, which often repeat generation details
Questions, answered
What this tool does and does not do.
Does this make an image undetectable as AI-generated?
No. This removes generation records stored in the file's metadata. It does not touch pixels, so an invisible watermark such as SynthID and any classifier that judges the image itself are entirely unaffected.
Which generators does it recognise?
AUTOMATIC1111 parameter strings, ComfyUI prompt and workflow JSON including compressed PNG text chunks, generator names written into Software or CreatorTool, and the IPTC digital source type.
Are prompts stored in JPEG files too?
Yes. PNG is the common case because generators write text chunks, but a JPEG can carry the same details in an EXIF UserComment or an XMP packet, and both are covered.
Does it detect that an image was AI-generated?
Only when the file says so. Reporting no AI metadata means nothing was found in the file, not that the image was made by a human.
Related tools
Further reading
- PNG Text Chunks and AI Generation MetadataHow tEXt, zTXt and iTXt store prompts, seeds and ComfyUI workflows—and why compressed chunks hide from most tools.
- How to Verify Metadata Was Actually RemovedChecking a cleaned file yourself, and what a verified result does and does not prove.
Every claim above describes the current build. Read our privacy approach or check the supported formats and known limits.