How SynthIDClear Works
A transparent look at how we remove hidden metadata locally without touching image quality, plus what metadata cleaning does and does not cover.
100% browser processing
Every byte of parsing, metadata stripping, and verification runs inside a local browser Web Worker. Your images never leave your device.
Lossless by default
SynthIDClear copies compressed pixel streams untouched and slices out only metadata chunks — avoiding JPEG/WebP generation loss and keeping 16-bit PNG quality.
Color profile safeguard
Wide-gamut Display P3 and sRGB color profiles stay intact by default so modern AI renders and smartphone photos never look washed out.
Technical Reference: Chunks Stripped vs. Preserved
| Format | Segments / Chunks Stripped | Segments / Chunks Preserved |
|---|---|---|
| JPEG | APP1 (EXIF, XMP), APP3–APP13 (incl. APP11 C2PA/JUMBF, APP13 IPTC), COM (comments), trailing bytes after EOI | SOI, APP0 (JFIF), APP14 (Adobe color), DQT, DHT, SOF*, SOS, EOI, and APP2 (ICC_PROFILE) when enabled |
| PNG | tEXt, iTXt, zTXt (AI prompts & XMP), eXIf, caBX / jumb (C2PA), tIME, trailing bytes after IEND | IHDR, PLTE, IDAT, IEND, tRNS, sRGB, gAMA, cHRM, pHYs, bKGD, and iCCP when enabled |
| WebP (RIFF) | EXIF, XMP , C2PA, JUMB, trailing bytes — plus clears EXIF (0x08) and XMP (0x04) bits in VP8X and recomputes RIFF size | VP8 , VP8L, ALPH, ANIM, ANMF, and ICCP (keeps 0x20 bit in VP8X) when enabled |
| HEIC / AVIF (ISOBMFF) | Exif items, mime XMP items, c2pa / jumb boxes & UUIDs, iref links, zero-wiped mdat extents, and trailing bytes | ftyp, hdlr, pitm, image mdat bitstreams (with updated iloc offsets), and colr (ICC) when enabled |
Completely removed (File metadata)
- C2PA / Content Credentials: JUMBF boxes (
caBX,APP11,C2PA) carrying provenance manifests and generator signatures. - AI Prompt & Workflow Chunks: Stable Diffusion
parameters, ComfyUI JSON graphs, and XMPDigitalSourceTypetags. - Personal & Device EXIF / IPTC: GPS coordinates, camera serial numbers, lens model, timestamps, creator software, and trailing bytes.
Not removed (Pixel watermarks)
- Imperceptible Pixel Watermarks: Signals such as Google SynthID or Stable Signature are embedded directly into pixel patterns to survive metadata stripping and re-encoding.
- Visual AI Classifiers: Platforms may inspect visual characteristics independently of file metadata.
- Platform Disclosure Policies: Always follow platform rules requiring disclosure of realistic AI media.
Common questions
How can I verify that SynthIDClear does not upload my images?
Open your browser DevTools Network tab while cleaning images or simply disconnect your Wi-Fi after loading the page — everything continues working locally.
How does SynthIDClear stay fast and stable on phones?
Batches process up to 2 images at a time to keep memory usage low, and temporary browser URLs are cleaned up automatically.
Why are pixel watermarks different from file metadata?
File metadata lives in container headers (EXIF, XMP, C2PA, PNG text) that can be removed cleanly without altering pixels. Pixel watermarks like Google SynthID embed patterns directly into the pixel values so they survive metadata cleaning.