Watermark and provenance signals
AI watermark detector
Check whether content has available AI watermark, provenance, or metadata signals and learn what remains publicly unverifiable.
Run a signal check
No detector model loads until you press Check.
Current support
Public watermark detection is provider-specific. AI Detect separates visible provenance from probabilistic text signals.
What this checks
- Provider watermark support is tracked in a structured registry.
- C2PA metadata can identify provenance when present in supported files.
- Statistical text classifiers are treated as risk signals, not proof.
What this does not prove
- Private provider watermark algorithms may not be publicly detectable.
- Watermark metadata can be stripped during copy, export, or platform processing.
- Text-only watermark checks depend on the provider and generation pipeline.
FAQ
- Can this prove whether content was written by AI?
No. AI Detect reports signals such as provenance metadata, watermark support status, and statistical text risk. It does not claim legal or authorship proof.
- Does text leave my browser during a local check?
Browser-default checks run local text features and provenance checks after you press Check. Server enhanced checks are separate and will be labelled before use.
- Why can a result be unknown?
Many providers do not expose public watermark detectors, and metadata can be absent or stripped. Unknown is a valid result when no reliable public signal exists.
Provider registry
Current watermark support
| Provider | Text watermark | Detection | File provenance | Tamper risk | Updated | Sources |
|---|---|---|---|---|---|---|
| Anthropic / Claudeanthropic, claude, claude-sonnet, claude-opus | plannedSynthID-Text-style statistical watermark | plannedAnthropic has described Claude text watermarking and says a detection API is planned, but no public Claude verification adapter is connected yet. | C2PAsupported_when_present | weak against rewriteClaude text watermarking is described as a statistical wording signal. Substantial rewriting can weaken it; C2PA file credentials are a separate metadata/provenance layer that can be stripped or lost. | 2026-08-17 | |
| Google / Geminigoogle, gemini, synthid | researchSynthID Text | availableSynthID Text is documented for compatible generation pipelines, but it is not a universal detector for arbitrary pasted text. | n/a | weak against rewriteSynthID-class text signals are statistical and should be treated as probabilistic. Media and file provenance can involve separate metadata or pixel-domain marks with different removal risks. | 2026-08-12 |
Removal pressure
Watermark tamper-risk registry
AI Detect uses remover research as adversarial context only. It does not run removal code, and it treats missing watermark or provenance evidence as an unknown state.
| Risk class | Target | Mechanism | Risk | How to read absence | Sources |
|---|---|---|---|---|---|
| Invisible Unicode and carrier cleanuplayer-a-invisible-unicode | Text with zero-width characters, bidi controls, tag characters, exotic spaces, or edit-based carriers. | Deterministic text normalization can remove visible-invisible carrier characters without needing a provider detector. | high | If this class of carrier is absent, the text may be clean, already normalized, or previously scrubbed.Whether obvious text-carrier artifacts are found when a detector is connected. | |
| Statistical text watermark weakeninglayer-b-statistical-rewrite | Token-sampling watermarks such as SynthID-style, Kirchenbauer green-list, keyed-Gumbel, or similar wording-distribution marks. | Substantial rewriting, paraphrase, or regeneration can move token choices away from the original marked distribution. | medium | A weak or missing statistical watermark can mean unsupported detector access, too little text, normal edits, or an intentional rewrite.Provider support status for public watermark verification. | |
| C2PA and file metadata strippingfile-provenance-metadata | Images, PDFs, Office files, HTML/Markdown, audio/video containers, and other files carrying provenance metadata. | Container cleaners can remove C2PA manifests, EXIF/XMP hints, document properties, YAML front matter, and similar metadata layers. | high | No C2PA manifest found means no local manifest was found; it does not prove the file was never AI-generated.Whether a browser-side C2PA manifest is present in supported file checks. | |
| Pixel and media watermark uncertaintymedia-pixel-watermarks | Images, generated media, or audio/video that may include imperceptible in-content watermarks. | Removal risk depends on the watermark family, transform robustness, regeneration, compression, cropping, and available verifier. | varies | Metadata absence does not answer whether an in-content watermark or soft-bound provenance exists.C2PA/provenance metadata when present. |
Reviewed source: https://github.com/guillaumemeyer/watermarks-remover at bcf497260af4.
Workflow upgrade
Need repeatable reviews?
Move from one-off checks to saved reports, batch review, and API-ready signal records when the workflow needs it.