How SynthID Remover works
A fixed, documented pipeline—no hidden browser trick and no claim of guaranteed removal.
1. Direct private upload
After validation and human verification, the browser receives a short-lived, content-type-bound upload URL for one private R2 object. The file does not pass through the public website Worker body.
2. Pinned diffusion reconstruction
A temporary GPU runs a digest-pinned container with fixed package and model revisions. The image uses the pinned Google vendor profile: a deterministic SDXL ControlNet reconstruction pass at strength 0.15, 50 inference steps, and tiled processing for larger images.
3. Metadata cleanup and fidelity gates
The processor re-encodes the result without EXIF, IPTC, XMP, or C2PA containers, preserves the original dimensions and alpha channel, and checks structural similarity and edge correlation. A result that misses either quality threshold is rejected.
4. Short-lived result
A passing result is available to the opaque job token for one hour. Scheduled cleanup removes it, and a 24-hour bucket lifecycle rule is the hard backstop. The temporary GPU instance is destroyed and verified gone after every outcome.
What completion means
Completion means the fixed processing pass ran, targeted metadata was absent after re-encoding, and the fidelity gates passed. It does not mean a provider detector confirmed removal, and it does not establish that the file is human-created.