SynthID Detector Goes Global: How to Spot AI Images

By Muhammad Ramzan Aatish

A photo of a US senator lying in a hospital bed went viral a few months ago. Millions of people saw it before fact-checkers got hold of the actual file and found the giveaway hiding inside it: an invisible SynthID watermark, still intact after the image had been screenshotted, recompressed, and reposted across half a dozen platforms. The photo was AI-generated. The watermark told the truth when nothing else could.

That same watermark system now belongs to everyone. Google has opened its SynthID detector to the public worldwide. No waitlist, no press credentials, no researcher application. You upload a photo, a video, or an audio clip, and the portal tells you whether Google’s AI, or one of its partners’, made it, highlighting the exact segments most likely to be synthetic.

The SynthID detector is Google’s free verification tool that checks whether a photo, video, or audio file carries SynthID, the invisible watermark Google embeds in AI-generated content. It scans for a statistical pattern hidden in the pixels, frames, or sound waves, then reports which parts of the file were most likely made by AI. It only works on content from systems that apply the watermark in the first place.

The gate just opened

Until this week, the SynthID detector lived behind a velvet rope. Google showed it off at its I/O developer conference last spring, then handed access to a small circle of journalists, media professionals, and researchers. Everyone else could read about watermarking while the fakes kept circulating.

The numbers Google attached to the announcement are big enough to raise an eyebrow. The company says it has now watermarked more than 180 billion images and videos, plus 240,000 years of audio, and that built-in checks inside Search, the Gemini app, and Chrome handle over a million verification requests every day. Those are Google’s own figures, not independently audited, so take the precision with a grain of salt. The direction is what matters: watermarking at this scale stops being an experiment and starts being infrastructure.

Honestly, the portal should have been public two years ago. The technology was already watermarking content back then; the only thing gated was letting ordinary people check it.

How to check a suspicious file

The SynthID detector gives you three routes, depending on what’s in front of you. The most thorough is the portal itself: upload the file and it returns a segment-by-segment breakdown, showing which regions of an image or which stretches of audio look AI-made. On a phone, the fastest path is the Gemini app, upload the image and ask whether it was created by AI. And in Chrome, you can right-click an image or use Circle to Search to check for watermark and content-credential markers without leaving the page.

I followed one of the early real-world tests of this as it fell apart in public. Back in January, a viral Reddit post posed as a whistleblower exposing a food-delivery company, complete with an AI-generated employee badge as “proof.” Tech journalist Casey Newton uploaded the badge to Gemini, which confirmed the SynthID watermark, the badge had come straight out of Google’s own image tools. The poster replied “Thats ok. Bye,” and deleted their Signal account within hours, as PiunikaWeb documented. Millions had already seen the claims. The watermark didn’t stop the hoax, but it ended the argument about the evidence in a single check.

One thing to internalize before you start uploading everything in sight: a negative result proves nothing. “No watermark found” could mean a genuine photo, a file from a generator that doesn’t watermark, or a watermark somebody scrubbed off. If you’re trying to learn how to detect AI generated images reliably, pair it with old-fashioned verification, reverse image search, checking the original source, asking who benefits from you believing it.

What the watermark actually is

For anyone wondering what is SynthID beyond the brand name: it’s not a visible stamp or metadata tag. For images, two neural networks train together, one subtly alters pixel values to embed an invisible statistical pattern, the other learns to spot that pattern later. The design goal was survival: the mark is supposed to persist through screenshots, cropping, resizing, rotation, and JPEG compression. That hospital photo surviving multi-platform recompression is the idea working as intended.

Text works differently. SynthID for text nudges the model’s token choices during generation, a technique the researchers call tournament sampling, where candidate tokens compete in rounds scored by pseudorandom watermarking functions. Google published the method in Nature and open-sourced it, and it’s now shipping inside Hugging Face Transformers. Across roughly 20 million live Gemini responses, the company reported no meaningful change in quality as judged by thumbs-up and thumbs-down rates.

The catch here is that text is where the whole scheme is weakest, and Google doesn’t hide that. Short passages, factual Q&A, and anything heavily paraphrased or translated can slip past. Independent researchers have shown paraphrasing attacks defeating text watermarks with near-total effectiveness. If someone rewrites AI-generated text by hand, no statistical pattern survives that.

Where it falls short

Scrolling through the Hacker News thread from when OpenAI signed on earlier this year, the mood was skeptical in a way that’s hard to dismiss. Hundreds of comments, and the through-line was consistent: useful against casual fakes, probably not against anyone trying hard. One camp questioned how fast the mark can be stripped; another wondered whether this is a genuine safety measure or mostly a PR move. That’s a fair summary of where things stand, and it’s worth saying plainly because Google’s own marketing leans toward the optimistic reading.

The coverage problem is structural. The detector only catches content from systems that watermark, mainly Google’s own tools (Gemini, Veo, Imagen, Nano Banana, Lyria, Flow, ProducerAI, Vids) plus partners OpenAI, NVIDIA, and Kakao, with Apple listed as ‘soon’ in Google’s own announcement. Anthropic explicitly doesn’t participate, using its own text watermarks and C2PA instead. Microsoft and Meta run separate standards of their own. So a clean result from the SynthID detector says nothing about a video from any of those other pipelines.

Demonstrated attacks are the sharper worry. Paraphrasing defeats text watermarks almost entirely, and independent image tools have reported dropping detection from near-perfect to about one in five.

Then there’s the spectral claim. Independent researcher Alosh Denny published a March 2026 project analyzing roughly 123,000 Gemini-generated images, reporting a 91% drop in phase coherence at quality loss invisible to the eye. Those claims rest on his own measurements, Google hasn’t published a response, so treat the robustness debate as live, not settled.

So can you trust a clean result? Only as one signal among several. That’s the honest answer, and it’s the one the research supports.

Two things people get wrong

The first misconception is baked into the name people give it. SynthID is not an AI detector, moderators of the r/isthisAI subreddit had to make that an explicit rule after users kept treating watermark lookups as general AI detection. A University of Washington-led study of those communities (Yeung et al., published on arXiv) found real confusion: one user expected ChatGPT to spot watermarks and was baffled when it couldn’t; only a tiny fraction of commenters ever used detection tools at all. The distinction matters. A classifier guesses whether something is AI-made. SynthID verifies a signature that was deliberately placed. Different question, different answer.

The second misconception is the mirror image: assuming no watermark means human-made. It doesn’t. It might be genuine, or from a non-participating generator, or scrubbed. Researchers studying the system put it bluntly: a negative result proves nothing.

Who watermarks, who doesn’t

The partner map has moved fast enough that most explainers are already stale. Here’s the current picture of who applies the Google AI watermark:

This fragmentation is the real story underneath the launch. A watermark that only some labs apply is a partial solution by definition, which is also why the EU’s transparency obligations for synthetic content matter here, as the site covered when Article 50’s duties took effect. Regulation is pushing toward machine-readable marking across the board; until that lands, every detector is checking a subset. For background on those rules, see the EU AI Act transparency breakdown.

What to actually do with this

A few concrete moves, depending on which side of the camera you’re on. Anyone whose work involves how to detect AI generated images day to day should make the SynthID detector one stop in a short routine: portal or Gemini check first, then reverse image search, then the source. Takes two minutes and beats arguing in comment sections.

If you create with Google’s tools, know your outputs are watermarked automatically. Platforms like YouTube already auto-label content based on these signals, and those labels can’t be removed by the uploader. That’s worth knowing before you publish, not after.

And if you’re wondering can SynthID be removed, researchers have demonstrated that it can be degraded or defeated, especially for text. What you won’t find here is a how-to; the honest answer is that no watermarking scheme has proven permanently robust, and anyone telling you otherwise is selling something.

FAQ

The SynthID detector going public is the kind of infrastructure moment that looks boring and turns out to matter. The Google AI watermark only works if people can check the marks, and until this week most people couldn’t. It won’t end deepfakes, nothing will, single-handedly, but it ends a specific, common argument: “prove this is fake.” Now you can, in about thirty seconds, as long as the file came from a system playing along. The rest is still on you.