100% free and private
Claude Watermark Remover
Clean invisible characters from text and AI metadata from supported files. Processing happens locally in your browser.
Maximum text length: 500,000 characters
Cleaned text
Paste the text you want to inspect and clean here.
Humanizer Skills for your editor
Clean text regularly? Automate the whole workflow.
The 8 Humanizer Skills bring Unicode cleaning, thorough reconstruction, proofreading, and clean typography directly into Claude Code, Codex, and other coding agents. German and English versions are included in one bundle.
The watermark audit is not an official SynthID detector and does not guarantee a particular detector result.
$117 one time, no subscription, plus VAT
Explore Humanizer SkillsFrequently asked questions
What the Claude Watermark Remover removes and where its limits are
Yes, for supported models. Anthropic’s current model list includes Fable 5.1, Opus 5.5, and Sonnet 5.5 for text watermarks on its own Claude surfaces. Support varies by model and can differ through cloud partners. Anthropic describes the imperceptible statistical signal as coming from low-stakes word choices, not invisible Unicode characters. It is still adding marking to other earlier models. This tool checks Unicode characters and supported metadata; it cannot detect or remove the statistical text watermark.
The cleaner covers standalone zero-width characters, bidirectional controls, tag characters, variation selectors, and unusual spaces. The safe default mode preserves valid characters used in emoji, text direction, and writing systems wherever possible.
No. Neither stage detects or measures statistical text watermarks. Stage 2 rewrites the content with the AI Humanizer, but that does not establish that a SynthID signal was removed or that detection confidence was lowered. There is no guarantee.
Stage 1 runs entirely in your browser and removes verifiable Unicode carriers and supported metadata. Stage 2 hands the cleaned text to the AI Humanizer, which rebuilds it from a content map. The audit checks two-word and four-word sequences, length, exact values, and then semantic equivalence. This second stage is optional and does not guarantee a SynthID result.
Initial inspection and cleaning run locally in your browser. The daily usage check sends only a short request without your content. If you then start the optional AI rewrite in the AI Humanizer, the text is sent to Gradually AI and the AI provider.
The first version supports plain text, Markdown, HTML, SVG, PNG, JPEG, and WebP. For images, the tool removes metadata. Visible logos or watermarks in image pixels stay unchanged.
No. For PNG, JPEG, and WebP files, the tool only removes supported provenance metadata without re-encoding the image pixels. A visible logo or a SynthID signal embedded in the pixels remains intact. You can retouch a visible logo in an image editor. This tool does not verify or guarantee whether an edit weakens SynthID enough.
For text, unusual spaces may be normalized and invisible controls may be removed. For images, image data is preserved while supported metadata is removed. Check the result before replacing the original file.
The local stage leaves visible text and ordinary formatting largely unchanged. The optional AI rewrite checks URLs, email addresses, dates, times, units, versions, technical identifiers, numbers, quotations, and code for exact preservation. A second review also compares claims, names, and logical relationships. You should still read complex HTML, Markdown, and technical material before publishing it.
Yes. The technical cleaner is not limited to Claude. It looks for general invisible Unicode carriers and supported metadata. A finding does not prove which AI tool created the content, and a clean result does not prove that a person wrote it.
In that case, the text or file contains none of the verifiable traces that the tool can safely remove. This does not prove human authorship or confirm that no statistical signal exists. The report only covers the characters and metadata the tool actually inspected.
Yes. An AI detector may still flag the text as AI-generated. Detectors can also misclassify human writing. Local cleaning removes technical traces, not every stylistic signal. A thorough rewrite may change a detector result, but it does not guarantee a particular classification or prove where the text came from.
Changelog
The latest updates and improvements to our Claude Watermark Remover
August 24, 2026v1.4.0
More targeted reconstruction
- Newly added numbers, URLs, identifiers, quotations, and code are rejected just like missing details
- Long verbatim prose passages become targeted hints for the second pass
- The second pass changes only flagged passages, then rechecks meaning and writing quality
August 24, 2026v1.3.0
Clearer flow and Humanizer Skills
- Added a Humanizer Skills link for Claude Code, Codex, and other coding agents
- Stage 2 now appears only after cleaned text is available
- Removed the decorative Unicode scan card and separate privacy and permission notices from the introduction
August 21, 2026v1.2.0
Quality-gated reconstruction
- Four-word sequences as an additional distance signal without forced synonym churn
- Protection for dates, times, units, versions, and technical identifiers
- Separate checks for meaning, completeness, clarity, and writing quality
- A Unicode cleanup pass before and after AI reconstruction
- Original fallback for short text or candidates that cannot be verified safely
Show older versions (2)
August 20, 2026v1.1.0
Two-stage reconstruction
- Private handoff to the AI Humanizer without putting text in the URL
- Up to two reconstruction passes for statistical text patterns
- Surface-distance checks plus preservation of numbers, URLs, email addresses, quotations, and code
- Stricter file validation and more precise metadata cleaning
August 20, 2026v1.0.0
Official launch
- Local cleaning of invisible characters in text
- Metadata cleaning for PNG, JPEG, and WebP
- Support for TXT, Markdown, HTML, and SVG
- Transparent report of removed and replaced characters
- Clear limitations without false detection claims