SSkrubly
en▼
← All articles

4 November 2026 · 7 min read

Where AI Detection Is Heading: Watermarks, C2PA and Detector Limits

AI detectors give probabilities, not proof. How watermarks and C2PA provenance differ, what the EU now requires of generators, and what to do today.

An image with a provenance badge and an invisible watermark pattern beside a probability meter

AI detection appears to be moving from guessing to labelling. Detectors that examine text or pixels give an estimate, and they can be wrong in both directions. So more effort is going into provenance, which records where a file came from, and watermarks, which are built into content when it is generated. EU rules now push AI providers towards machine-readable marking too. None of this will settle every case, since many files carry no signal at all, so for now the sensible approach is to combine several checks and treat each result as evidence, not a verdict.

Why can't AI detectors give a definite answer?

A detector looks for statistical patterns that tend to appear in AI output. Nothing in a sentence or a pixel inherently proves how it was made. Human writing can look formulaic, AI writing can be edited, and image compression can wash out patterns. That is why a result is a probability, and a high score is not a finding of fact.

A 2023 paper shows the stakes: 'GPT detectors are biased against non-native English writers', by Weixin Liang and colleagues, found that several widely used detectors consistently misclassified non-native English writing as AI-generated, and that simple prompting could also help text evade them. Tools have changed since then, and results vary, but the authors' caution about using detectors in evaluative or educational settings still deserves attention.

What is the difference between detection, watermarks and provenance?

ApproachHow it worksStrengthWeakness
Detector (text or pixels)Looks for patterns after the factWorks on any file you give itProbabilistic; false positives and false negatives
Invisible watermarkA signal added when the content is generatedCan survive some edits, and is hard to seeUsually only readable by a matching tool, and only for generators that use it
Provenance (C2PA)Signed record of origin and edits attached to the fileCan say who made what, with cryptographic backingCan be removed; absence proves nothing
Generator tags (metadata)Plain labels written by the toolSimple to readEasily lost or edited
Human checksSource, context, second angle, reverse image searchWorks on what the file cannot tell youTakes time, and can still be fooled

How do C2PA Content Credentials work, and what can't they prove?

Content Credentials are the C2PA standard's way of recording provenance. The C2PA describes them as a cryptographically secure way to capture and express where content came from. They can show that an image was generated by a certain tool, or that a photo has not been changed since capture. It is more like a signed label than a detector.

The C2PA FAQ also describes 'soft bindings', such as invisible watermarks or fingerprints, which can help find a credential again after it has been separated from a file. That is why metadata and watermarks are often discussed together rather than as rivals.

Read any C2PA or generator tags embedded in an image. In your browser, nothing uploaded. 'No markers found' proves nothing either way.

Open the AI Image Checker

Will watermarks solve the problem?

Probably not alone. Google's SynthID is a well-known example: Google says it embeds invisible watermarks in AI images, video and audio, and adjusts word probabilities to mark text. It also offers ways to check for that watermark. But a check like that can only find its own signal. A negative result does not mean a file is human-made; it may come from a generator that does not use that watermark. Open models that people run themselves may not add one at all.

So watermarks could make a growing share of content easier to identify, especially from major providers, while leaving a gap that will not necessarily close. How robust they will be against determined removal is an open question, and worth reading vendor claims carefully.

What does the EU require for marking AI content?

Article 50(2) of the EU AI Act requires providers of generative AI systems to mark outputs in a machine-readable format so they can be detected as artificially generated or manipulated. The Commission says the transparency obligations apply from 2 August 2026. Following the AI Omnibus amendments, its AI Act Service Desk shows a transition for systems placed on the market before that date: their providers have until 2 December 2026 to comply with Article 50(2).

Publishing AI images for work? Who has to label what under the AI Act.

EU AI Act labelling rules

Where could AI detection go next?

These are directions to watch, not predictions:

What should you do today?

If you are checkingDo thisDo not
An imageRead embedded markers, run a reverse image search, look for the earliest sourceTreat 'no markers' as proof that it is real
A piece of textUse a detector as a prompt for questions, and look at drafts and sourcesAccuse anyone on a score alone
Your own writingKeep your drafts and version history, and check flagged passagesPanic over one number
Your own AI imagesKeep originals and disclose where requiredStrip provenance to hide required disclosure

Get an estimate of how AI-written a text reads, with the most AI-like passages highlighted. An estimate, not proof.

Open the AI Content Detector

Skrubly's two checkers deliberately do different jobs. The AI Content Detector estimates from patterns in text, so it can be wrong. The AI Image Checker does not judge pixels: it reports C2PA and generator tags embedded in the file, so it can only speak when those tags are there. Neither is a final answer, and the same goes for any tool.

Quick answers