AI Watermark Checker: Is Your Text Watermarked?

How does this AI watermark checker work?

An AI watermark checker is a tool that inspects text for the marks AI systems and their pipelines leave behind — and the character level is the only level any third-party tool can verify. This checker reads your text code point by code point and compares each character against the known hidden and watermark-candidate ranges: special spaces (U+202F, U+00A0, U+2009), zero-width characters (U+200B, U+200C, U+200D, U+2060), byte order marks (U+FEFF), Unicode tag characters (U+E0000–U+E007F), variation selectors (U+FE00–U+FE0F), and typography tells like smart quotes and em dashes. Detection comes first — you see the evidence before anything is changed.

1. Paste your text above. The scan runs instantly in your browser — nothing is uploaded, logged, or stored (see how it works for the full methodology).
2. Read the named report. Every hit is listed by character name, code point, and count — "narrow no-break space (U+202F) × 12", not a vague "suspicious characters found". Named code points are what let you verify the finding anywhere else.
3. Decide: clean or keep. If the report shows characters you don't want, one click removes the watermark characters while leaving every visible word untouched. For output from Claude, Gemini, or any other model, the AI text cleaner runs the same pass.

And if the scan finds nothing? That's a result too: a clean report means your text carries no character-level watermark and no hidden Unicode at all — there is literally nothing invisible in it to find.

What can a watermark checker verify — and what can't it?

A character scanner gives a definitive answer for exactly one layer: characters. As of August 2026 that honest split looks like this:

The statistical column is growing: Anthropic announced on August 11, 2026 that Claude models launched on or after August 2, 2026 carry a SynthID-style statistical watermark, with no Unicode characters embedded, detection that needs longer samples, and a third-party detection API planned. The timing tracks the EU AI Act's Article 50, which requires generative-AI output to be machine-readably detectable from August 2, 2026 — so expect more statistical watermarks, not fewer. Until provider detection APIs exist, "is my text statistically watermarked?" is answerable only by the model's maker. What this checker gives you is the complete character-level truth — and honesty about the boundary.

Can Turnitin or professors see hidden characters?

Yes — assume anything you submit will be inspected at the character level. Turnitin's Similarity report ships integrity "Flags" that specifically detect hidden text (such as white-on-white characters) and "replaced characters" — Cyrillic homoglyphs like U+0430 posing as the Latin letter "a", an old trick for dodging plagiarism matching (see how homoglyph attacks work and how to spot them). Any teacher can also press Ctrl+Shift+8 in Word and watch no-break spaces light up as ° marks.

This is precisely why a checker exists: so you know what is in your text before anyone else does. A stray U+202F picked up from a copy-paste is explainable when you found it yourself and cleaned it; discovering it during an integrity review is a much worse conversation. Note what checking is not: Originality.ai's testing found that adding or removing invisible characters leaves AI-detection scores essentially unchanged, because detectors read word patterns. Checking and cleaning are transparency tools, not evasion tools — if your institution requires AI disclosure, disclose.

The security angle: check text you receive, not just text you send

Invisible characters aren't only a hygiene problem — they are an attack surface, and a checker is the defense. ASCII smuggling is the technique of encoding ordinary instructions as invisible Unicode tag characters (U+E0000–U+E007F), a complete hidden copy of the ASCII alphabet: a human reviewer sees nothing, while an AI assistant reads a command. That means a pasted email, resume, or "helpful prompt" can carry instructions you cannot see but your tools will obey.

• January 11, 2024: researcher Riley Goodside demonstrated "ASCII smuggling" — invisible tag-character instructions that steer LLMs. Johann Rehberger then chained the technique into a Microsoft 365 Copilot exploit that exfiltrated emails and MFA codes via invisible characters (disclosed January 2024, published August 26, 2024, since fixed).
• October 2025: FireTail tested major chatbots and found ChatGPT, Copilot, and Claude sanitize tag characters — while Gemini, Grok, and DeepSeek remained vulnerable. Google declined to fix, classifying it as social engineering.
• Variation selectors (U+FE00–U+FE0F, U+E0100–U+E01EF): 256 invisible values equal one hidden byte after any character, as Paul Butler showed by smuggling arbitrary data through a single emoji in February 2025. Mindgard and Lancaster University researchers (arXiv:2504.11168, April 2025) used the same trick to evade production LLM guardrails — including Azure Prompt Shield and Meta Prompt Guard — at rates up to 100%.

The defensive habit is simple: before you paste received text into your AI assistant, ATS, or terminal, run it through the checker. A clean report means no smuggled payload exists at the character level; a detection shows you exactly which invisible characters are present — compare them against the full invisible Unicode characters list — and one click strips them before they reach anything that would obey them.