Generators sign their output three ways — an invisible pixel watermark, a cryptographic provenance manifest, and plain metadata tags. SynthGuard handles all three locally in your browser. No upload, no server, nothing left pointing back to a generator.
A clean metadata panel feels like success — but the strongest AI watermark isn't in the metadata at all. SynthID is woven into the pixels and survives stripping, cropping and compression. There are really three separate things to deal with:
C2PA, Content Credentials, EXIF/XMP “Made with AI”. Easy to strip — and where most tools stop.
SynthID, embedded in the image itself. Survives metadata deletion. Needs signal disruption, not a delete button.
Even with no watermark, detectors score the diffusion fingerprint. The full humanizer rebuilds camera authenticity.
SynthGuard handles the first two directly, and the third with the full photo humanizer. Read the deep-dives on SynthID, C2PA and Content Credentials.
What gets removed
Generators rarely sign their output just once. Here's each marker, what it is, and how the pipeline handles it.
INVISIBLE · PIXEL-EMBEDDED
Google DeepMind's watermark, embedded in the pixels of Imagen, Veo and Gemini output (and the tokens of Gemini text). Survives JPEG compression, cropping, scaling and colour shifts — which is exactly why deleting metadata does nothing to it.
PROVENANCE · CRYPTOGRAPHIC MANIFEST
The signed provenance manifest attached by DALL·E 3, Adobe Firefly and a growing list of cameras and editors. Platforms read it to decide whether to show an "AI Info" label — it's the single easiest signal for them to act on.
METADATA · EXIF / XMP TAGS
Generators also write plain metadata flags — EXIF, XMP, IPTC fields and the "digitalSourceType: trainedAlgorithmicMedia" hint. Trivial to read, trivial to strip — but on their own they're only half the picture.
VISIBLE · BURNED-IN OVERLAY
The on-screen logo overlay some tools burn into video frames is a different problem from invisible watermarks — it's pixels in the picture, not a signal. Removing it is a crop or inpaint step, separate from the humanization pipeline.
Provenance signals
How it runs
The whole flow stays inside your browser tab — no file ever reaches a server.
Image or video — single file or batch. Nothing uploads; the file stays in your browser tab.
C2PA and metadata tags removed; the invisible SynthID mark disrupted in the bands its verifier reads — without touching what your eye sees.
Re-test with the free in-browser AI Image Detector before you publish. Eight forensic signals, instant verdict.
Export a clean file with no provenance pointing back to a generator — ready for any platform that checks.
By generator
Each generator signs its output differently. The right tool depends on whether you're working with a still image or video.
Privacy model
Pixel data stays in browser memory. We physically cannot see what we never receive.
Disruption runs in a sandboxed worker thread — disable your network and it still works.
Nothing is stored or logged. Close the tab and it's gone.
Drop many files at once; each processes locally on its own thread.
FAQ
Only for metadata-based markers like C2PA, Content Credentials and “Made with AI” EXIF/XMP tags. The invisible SynthID watermark is embedded in the pixels themselves and survives metadata deletion, cropping and compression. Removing it requires disrupting the signal in the image, not just clearing fields — which is what the humanizer's SynthID layer does.
A visible watermark is a logo or text burned into the picture (the on-screen mark some video tools add). An invisible watermark like SynthID is a statistical pattern woven into the pixels that only a verifier can read. SynthGuard targets the invisible and provenance markers plus metadata. A visible burned-in logo is a separate crop or inpaint step — handle that first, then humanize the result.
The humanizer disrupts the SynthID synchronisation signal in the spatial and frequency bands its verifier relies on, so detection collapses toward chance — while the image stays visually identical. No tool can promise a watermark is gone forever, because verifiers update, so always re-check on the free detector before publishing.
No visible change at default settings. The disruption sits below the human perception threshold — the same principle that lets the watermark stay invisible in the first place works in reverse to remove it.
Video, yes — the video humanizer applies the same per-frame disruption and strips container metadata. Audio watermark removal is not part of the current pipeline.
Most of those either only clear metadata (which misses SynthID) or upload your file to their servers. SynthGuard runs entirely in your browser — nothing is uploaded — and combines metadata stripping with actual pixel-level disruption.
It removes the provenance and watermark triggers that fire the label. But platforms also run pixel-level classifiers, so for a clean pass you usually want the full humanizer — strip the watermark and rebuild camera authenticity (PRNU, FFT, EXIF). See the photo humanizer for the complete pipeline.
Removing a watermark from content you generated yourself is legal in the jurisdictions we operate in. You remain responsible for the terms of the platform you publish on and for honest disclosure where it's legally required — for example, realistic depictions of real people or events. SynthGuard does not provide identity-impersonation or deepfake features.
Open the humanizer, drop your file, and remove the watermark in your browser — invisible mark, provenance manifest and metadata, all in one pass.
All third-party names, logos and trademarks (e.g. Hive, Optic, Sensity, Sightengine, Illuminarty, GPTZero, Instagram, TikTok, OnlyFans, Fanvue, SynthID, C2PA) are the property of their respective owners. SynthGuard is an independent service and is not affiliated with, endorsed by, sponsored by, or partnered with any of these companies or platforms. Detector and platform names are used solely for descriptive comparison under § 6 UWG / Art. 4 Directive 2006/114/EC.
We use a small number of cookies to keep you signed in. With your consent we'd also like to load privacy-friendly analytics so we can improve SynthGuard. See our Privacy Policy.