How to use this tool
This checker inspects selected Unicode characters in text copied from Claude or another source. It does not verify a proprietary watermark, determine whether a person used AI, or predict a detector score. Use it when you want to see the actual character findings before deciding whether cleanup is appropriate. The report is about the string you pasted, and the Analyze text action preserves that string rather than silently editing it.
Scroll the table sideways to see every column.
| Observed result | Supported conclusion | Unsupported conclusion |
|---|---|---|
| U+200B found | This string contains U+200B | Claude authored this string |
| No findings | No supported special marks found | Human authorship is proven |
| Joiner found | A sequence includes a joiner | The joiner should be deleted |
| Cleanup fixes lookup | This edit resolved this test | All AI detection is removed |
What a checker result actually establishes
A reported U+200B means the supported scanner found that character at the displayed position. It does not explain who inserted it, why it is there, or whether it was intentional. Copying through a webpage, document editor, clipboard, or publishing system can involve several transformations. Identifying a character is therefore only the first part of investigating a formatting problem.
Likewise, an empty report means no supported special characters were detected. It does not prove that a passage was written by a human, that it contains no invisible characters outside the scanner's scope, or that it is ready to publish. Keep the distinction clear when sharing a result. Describe the code point and the behavior being investigated rather than labeling a person or document as AI-generated.
Inspect a working copy
Save the original before pasting a passage for review. Start with the smallest sample that reproduces the problem: perhaps a product code that fails a lookup or a sentence that wraps strangely. Include enough surrounding text to make the issue understandable. If the original is confidential, construct a neutral example rather than sending the full passage in a support request.
Try an example loads a demonstration containing a real hidden separator. It replaces any existing input. The sample is a way to learn how findings appear; it is not a capture of a specific Claude response. Press Analyze text to generate the unchanged result, then examine the finding's code and position. No removal setting is active on this inspection page.
Understand the supported categories
The checker reports selected invisible characters, special spaces, em-dash variants, and control or directional marks. Those categories include characters with legitimate uses. A joiner can belong to an emoji sequence, and a no-break space can serve a layout purpose. The report does not assign a probability that a finding is unwanted. That decision depends on the passage and destination.
The scanner is not a complete Unicode inventory. Ordinary letters, standard spaces, tabs, and normal line breaks are not special findings. Use Show spaces or Show tabs to examine ordinary whitespace in the preview. If the suspected difference involves accents, similar-looking letters, or rich-text structure, this checker may not expose the cause. Investigate the relevant format or full character sequence instead.
Reproduce a concrete formatting problem
Suppose an invented identifier looks like REF42 but contains REF[U+200B]42. The bracketed label here represents an actual zero-width space. The checker can report that mark. If a receiving system requires exactly REF42, a removal experiment on a copy is reasonable. The evidence you want is that one explained edit makes the exact lookup succeed.
Now consider a joined emoji containing U+200D. The same report may contain a finding, but deletion could change the emoji's appearance. Preserving it may be the correct outcome. Comparing these two cases prevents an overbroad interpretation of a positive report. The practical question is whether the character belongs in this text, not whether the checker can find something unusual.
Move to cleaning only when the edit is justified
If you decide a change is needed, open the text cleaner or zero-width remover with a copy of the original. Conservative mode removes U+200B, U+FEFF, and U+00AD while preserving several joiners, special spaces, and dashes. It remains a fixed rule set rather than a judgment about language. Review every distinct kind of proposed removal.
Custom invisible removal can also delete U+200C, U+200D, and U+2060. For multilingual passages or emoji, check a representative sample before choosing that rule. Directional and control marks are reported but left unchanged for manual review. After any change, repeat the actual destination test and read the surrounding words. A successful cleanup is a resolved behavior with preserved meaning.
Read positions and counters carefully
Locations are displayed starting at one and counted in Unicode code points. A visible symbol may consist of several code points, so the number can differ from a visual cursor position or an editor's byte offset. Record the nearby text along with the numeric position when reporting an issue. That makes the finding easier for another person to reproduce.
Only the first thirty findings appear as badges, even when the counter reports a larger total. Long previews may also be shortened. Break a long document into useful sections instead of approving it from the visible beginning alone. Show spaces and Show tabs affect only the preview. Their visual dots and arrows are not inserted into the copied output.
Keep authorship and publishing review separate
Character inspection cannot replace fact checking, citation review, or disclosure requirements. If a publication, employer, or school asks you to disclose AI assistance, changing punctuation or hidden characters does not resolve that obligation. Preserve attribution and review the substance of the text. noclau provides no guarantee about how another service will classify a passage.
The website is independent and is not affiliated with or endorsed by Anthropic. Pasted text is processed in your browser by the application rather than sent to Claude or an analysis service. Ordinary website requests are described in the privacy policy. If you need help, share a minimal invented example, the finding, and the failed operation. Those details support a useful formatting investigation without making unsupported claims about the source.