Common questions

No. Reading, inspection and cleanup happen in your browser. Website and advertising requests are separate from image processing.

Try another valid JPEG, PNG or WebP. A damaged file, unsupported format or browser resource limit can prevent processing. Keep your original.

Yes: up to 20 files, 20 MiB each and 100 MiB total. A failed file does not prevent other files from completing.

The removed embedded data is no longer in that copy. Keep the original PNG and export workflow JSON before cleaning. Share those deliberately when you want others to reproduce your setup.

JPEG, PNG and WebP · 20 MiB each · 20 files per batch · Up to 40 million pixels. Browser decoding is checked; for animation, only the first frame is verified.

For metadata removal, start with Clean AI info: it preserves the compressed image data without re-encoding. To convert a still JPEG or WebP to PNG, or make a fresh PNG export, choose Re-encode. Your browser decodes the image, draws it on Canvas and exports PNG. Appearance, colors, bit depth and file size may change; animation is rejected. Keep the original.

PNG/APNG and WebP animation data is preserved by container cleanup. Re-encoding animation is blocked. GIF is not supported.

The default container cleanup preserves image data, color profiles and needed orientation. Re-encode creates a new PNG and may change color interpretation.

No. It removes supported embedded metadata. Platforms may use other signals, and required disclosures still apply.

Supported embedded records can include PNG prompts and workflows, XMP and C2PA provenance. Coverage depends on the file. Inspection shows record categories, not an AI-generation verdict.