Skip to content
SynthIDX

See Whether a Watermark Is Still Readable

AI Watermark Detector

Runs a SynthID check and a pixel classifier, then explains what each result can and cannot prove.

Sign in to run. Free credits included.

Two independent reads from one upload: the file’s declarations and its pixel statistics · Says plainly when a result is a probability, a declaration, or a question only Google can answer · Your file uploads straight to storage and is used only to produce your report

What each check reads

This page runs two checks on a single upload, and they look at different evidence. The first reads what the file declares about itself. A provenance record such as a C2PA Content Credential, an EXIF generator field, an IPTC label, or a written SynthID declaration all fall into this group. The report lists which records are present and which platform or generator they name. The C2PA standard behind those credentials is published at https://c2pa.org/.

The second check ignores declarations and reads the pixels. A classifier trained on real photographs and generated images scores the texture, noise, and frequency patterns that tend to separate the two. It reports an AI-likelihood tier and, when the evidence is strong enough, a source family. The read survives a metadata strip, which is why it is useful on files whose provenance records are gone.

Neither check verifies Google’s invisible SynthID watermark. That watermark is a pattern planted in the pixels at generation time by a detector Google keeps to itself. The DeepMind SynthID page describes how the pattern is embedded: https://deepmind.google/models/synthid/. Testing the pattern itself belongs to Google’s official verification portal. This page reads every layer it can reach and names the one it cannot.

The two results answer different questions, so they can disagree. A file can name a generator in its metadata and still show AI-like pixel statistics. It can also declare an AI origin while the classifier reads it as photographic. Neither result cancels the other. The page reports both and lets you weigh them together.

How it works

How to run both checks in one pass

  1. Step 1: Choose the original file

    The page accepts PNG, JPEG, WebP, BMP, TIFF, HEIC, HEIF, and AVIF images up to 20 MB. Start from the file as close to its source as you have it, because re-shares and screenshots lose the declarations the first check reads.

    Tip

    The first save from the generating app keeps the most declarations. A screenshot of the same image keeps almost none.

  2. Step 2: Run both checks

    One upload starts two read-only operations: the signal report over the file’s declarations and the pixel classifier over its statistics. A full check costs 10 credits, and the panel shows the price before anything runs.

    Tip

    Credits are consumed only when a job actually runs, and new accounts start with 100 free credits.

  3. Step 3: Read the two cards together

    Each operation returns its own card. The signal report says what the file declares and where the declarations conflict. The classifier card gives the AI-likelihood tier and the source family, or an abstention when nothing matches. Treat the pair as evidence, then follow up with Google’s portal if the pixel watermark is the question.

    Tip

    Quote the tier alongside the verdict. "Definitely AI-like" and "possibly AI-like" carry different weight.

Three layers, and what each one can tell you

  • SynthID

    The signal report surfaces a written SynthID declaration and the platform it credits. The pixel pattern behind the declaration stays with Google, whose portal is the only place to test it.

  • Metadata

    C2PA manifests, EXIF generator fields, and IPTC labels travel in readable metadata. The report lists which layers are present and which platform or generator they name. When the layers contradict each other, the clash appears in the report as an integrity warning.

  • Classifier

    The pixel read ignores metadata and returns an AI-likelihood tier: definitely AI-like, possibly AI-like, likely human, or undetermined. It is a screening signal about the statistics of this file, not a statement about who made it or why.

What a negative result does not prove

A negative result is not proof that no watermark exists

An empty declaration report means this file carried nothing readable at the moment of the check. AI images lose their provenance through screenshots, re-encodes, and platform uploads all the time. The invisible pixel watermark may still sit in the image, and a third-party check cannot test it. Only Google’s official portal can rule on SynthID itself.

Detector access stops at Google’s portal

The SynthID pixel detector is proprietary and closed to other tools. This page reads declarations, locally decodable signals, and pixel statistics, and it says which result came from which layer. Where a provider keeps its detector private, the honest answer is that the question is out of reach, not that the answer is no.

Classifier output is a probability, not authorship

Statistical reads drift as generators change, and heavy compression or editing can push the tier in either direction. Real photographs get flagged, and generated images pass. The tier describes how strongly this file matches the training data, and it is one input to a judgment, never the judgment itself.

Provenance records are claims, not facts

A manifest describes what a file said about itself when the record was written. Crop the pixels afterward and the record no longer covers what you see. Some declarations are also forged or transplanted. Read the integrity clashes the report lists before treating any declaration as settled fact.

When Full Cleanup is the next step

Detection answers a question. It does not change the file, and for many readers that is where the job ends. Full Cleanup is the next step in a narrower set of cases: the image is your own output, you have the right to edit it, and the declarations it carries are ones you no longer want attached. That includes visible logos you added through a generator, C2PA credentials naming the model, and an invisible signal you want reduced before you hand the file to someone else.

The AI Watermark Remover page runs that job as a single pass. It rebuilds the regions under visible marks, strips the metadata layers, and reduces the invisible signal in the same run. A full cleanup costs 100 credits, and one job covers one image. That pass is designed to change the file’s surface, not to guarantee any detector reads zero afterward. Detectors evolve, and a cleanup that clears one reading may leave another.

Do not use Full Cleanup on provenance you do not own. Stripping credentials from someone else’s work breaks the record that platforms and newsrooms rely on, and in several jurisdictions it is a legal problem rather than a technical one. If the question is simply whether a file carries a watermark, stop at the report. If the pixel verdict matters, take the file to Google’s portal. If the file is yours and you want the declarations gone, the remover is the tool for that job.

FAQ

Frequently asked questions

Plain answers about what the SynthID check reads, what the pixel classifier estimates, and which questions only Google can settle.

Explore more tools

SynthID Detector

Read SynthID and OpenAI declarations, C2PA credentials, and the raw metadata listing behind them.

Open tool

AI Image Detector

Score the pixels alone with a statistical classifier, with a confidence tier and a source-family read.

Open tool

AI Watermark Remover

Run Full Cleanup on your own images: rebuild visible marks, strip credentials, and reduce the hidden signal.

Open tool

Remove AI Label

Reads the platform side: which metadata fields trigger an AI label, and how to clear them.

Open tool

C2PA Remover

The signed credential layer the declaration check reads, explained and stripped on its own page.

Open tool

All tools

Every remover and detector on one page, grouped by what each one cleans or checks.

Open tool

Check a file before you change it

The report separates declarations, pixel statistics, and the one question only Google can answer. If the file is yours and the declarations should go, Full Cleanup is one pass away.