Zero-Width Characters
Detect supported characters such as Zero Width Space, Zero Width Joiner, Zero Width Non-Joiner and Word Joiner.
Find invisible Unicode characters, zero-width spaces and unusual spaces in your text. See the exact character, code point, count and position before removing anything.
Paste your text below to scan for supported hidden Unicode characters. Review the X-Ray view and findings, then remove or normalize only the character types you choose.
Paste text below to find hidden Unicode, zero-width characters, and unusual spaces.
Your cleaned text will appear after scanning.
An invisible character detector scans the actual Unicode characters inside text and reveals characters that are difficult or impossible to see. CountFlows shows supported zero-width characters, unusual spaces and directional controls with their Unicode code point, name, count and position. If your problem is broader formatting such as Markdown, HTML, punctuation or general AI-text cleanup, use the AI Text Cleaner instead.
See characters that are normally hidden from view.
Get the Unicode code point, name and exact location.
Remove or normalize only the character types you choose.
You do not need to know Unicode codes before using the tool. Paste the text, run the scan and review the character report before applying cleanup.
Paste the text you want to inspect into the Original Text box.
Select Detect Invisible Characters to scan the underlying Unicode sequence.
Detected characters appear as visible labels such as U+200B inside the text preview.
See each character's name, Unicode code point, number of occurrences and positions.
Use the recommended selection or manually choose the character types you want changed.
Review the cleaned output and copy it when you are satisfied with the result.
Usually, it does not look like anything. Two strings can appear identical on screen while containing different Unicode sequences underneath.
Normal view
Nothing unusual is visible between the words.
X-Ray view
The detector reveals the Zero Width Space stored between the visible characters.
The scanner focuses on common hidden and non-standard Unicode characters that can be difficult to identify visually. It separates them by purpose because not every detected character should be treated the same way.
Detect supported characters such as Zero Width Space, Zero Width Joiner, Zero Width Non-Joiner and Word Joiner.
Find no-break, narrow, thin, hair, figure, ideographic and other supported Unicode spacing characters.
Identify supported left-to-right, right-to-left, embedding, override and isolate controls.
Detect characters such as U+00AD Soft Hyphen and U+FEFF, which may be difficult to notice in ordinary text.
Zero-width characters are Unicode code points that can exist in a text string without occupying ordinary visible space. The best-known example is U+200B, the Zero Width Space. Because the character still exists in the underlying string, software can count or compare it even when a person cannot see it.
Zero-width does not automatically mean useless. U+200C Zero Width Non-Joiner and U+200D Zero Width Joiner can affect how characters connect in writing systems, and ZWJ is also involved in emoji presentation. For that reason, CountFlows detects these characters but does not automatically recommend removing them.
Unicode documents U+200B separately from normal space characters and defines ZWJ/ZWNJ as characters with legitimate text-processing uses. Unicode Standard reference
These examples show why character-level inspection is more useful than a simple “remove everything invisible” button.
| Unicode | Name | Type | Default approach |
|---|---|---|---|
| U+200B | Zero Width Space | Invisible | Remove |
| U+00AD | Soft Hyphen | Invisible | Remove |
| U+FEFF | BOM / Zero Width No-Break Space | Invisible | Remove |
| U+00A0 | No-Break Space | Unusual space | Normalize |
| U+202F | Narrow No-Break Space | Unusual space | Normalize |
| U+200C | Zero Width Non-Joiner | Language-sensitive | Review |
| U+200D | Zero Width Joiner | Language / emoji-sensitive | Review |
| U+200E | Left-to-Right Mark | Directional | Review |
| U+200F | Right-to-Left Mark | Directional | Review |
| U+202E | Right-to-Left Override | Directional | Review |
No. Some hidden characters are common cleanup candidates, while others can carry legitimate formatting or linguistic meaning. A reliable detector should tell you what the character is before changing it.
Common candidates such as stray Zero Width Spaces, Soft Hyphens and BOM characters can be selected automatically. Non-standard spaces can be normalized to an ordinary space.
Joiners, non-joiners and bidirectional controls can have legitimate uses. They remain visible in the report but are not automatically selected by the recommended cleanup mode.
Computers compare the characters stored in a string, not only what the string looks like on screen. An extra code point can therefore change how text behaves without producing an obvious visual difference.
A hidden character inside a variable, copied command or identifier can make two visually identical strings different.
Hidden Unicode can remain inside data saved through forms, CMS fields, spreadsheets or databases.
Exact search may fail if an invisible character exists inside the phrase being matched.
A visible phrase may not match your replacement rule when an extra zero-width character exists inside it.
Invisible Unicode is especially confusing in technical text because developers often inspect what is displayed while software evaluates the underlying string. A hidden code point can affect comparisons, keys, identifiers or validation even when the text appears unchanged.
Visible value: "admin"
Hidden value: "ad[U+200B]min"
To a person: may look similar
To software: different character sequenceThe X-Ray view is designed for this situation: it exposes the hidden code point without rewriting the rest of the input.
Invisible and non-standard Unicode characters can appear through normal text processing. Common sources include websites, word processors, PDFs, rich-text editors, messaging apps, file encodings and copied code. Some characters may also be deliberately inserted for formatting or technical purposes.
Their presence therefore tells you what exists in the text, not who created the text or why the character was inserted.
U+FEFF is used as a Byte Order Mark at the beginning of some Unicode text streams. When it appears unexpectedly inside copied or processed text, it may be difficult to see and can behave like an unwanted hidden character.
Unicode defines U+FEFF as the character used for the byte order mark in relevant Unicode encoding schemes. Read Unicode's BOM FAQ
Replace supported invisible findings with visible code-point labels inside a preview of the original text.
See the Unicode code point, character name, type, count and positions.
Use position details to locate hidden characters inside multi-line text more precisely.
Choose exactly which detected character types should be removed or normalized.
Common cleanup candidates are selected while sensitive joiners and directional characters remain optional.
Convert supported non-standard spaces to a normal space instead of deleting the gap completely.
Scan large text while limiting the visual X-Ray output to keep the interface responsive.
The scanner does not require an AI model or remote text-analysis API.
Both tools can inspect hidden Unicode, but they serve different search intents. This detector is a general Unicode debugging tool for any text. The ChatGPT Watermark Remover is specifically organized around checking copied ChatGPT text and watermark-related questions.
| Need | Invisible Character Detector | ChatGPT Watermark Remover |
|---|---|---|
| General hidden Unicode inspection | Best choice | Supported |
| Code, data or copied text debugging | Best choice | Not the main focus |
| Exact code points and positions | Yes | Yes |
| ChatGPT watermark-specific questions | Not the main focus | Best choice |
| ChatGPT copy-paste investigation | Supported | Best choice |
If your question is specifically about copied ChatGPT content, use the ChatGPT Watermark Remover.
The character scan and cleanup logic run in your browser. CountFlows does not need an AI model, external AI API or database lookup to identify the supported Unicode characters in the text.
For confidential or regulated information, continue to follow your organization's own security and data-handling requirements before placing information into any website.
Choose the next tool based on whether you need broader cleanup, AI-specific inspection, comparison or precise replacement.
Clean formatting
Clean Markdown, HTML, punctuation, spacing and broader formatting artifacts from AI-generated or copied text.
Open toolCheck AI text
Inspect copied ChatGPT text for supported hidden Unicode and watermark-like character artifacts.
Open toolCompare versions
Compare the original and cleaned versions to review visible changes side by side.
Open toolMake precise edits
Find and replace specific words, phrases or characters using custom replacement rules.
Open toolPaste the text into the Invisible Character Detector and select Detect Invisible Characters. The scanner checks supported Unicode code points and reports the character name, code point, count, position, line and column. The X-Ray view makes detected characters visible inside the original text.
A zero-width space, U+200B, is a Unicode character that has no visible width. It can exist between visible characters even though you cannot see a normal gap. It may affect exact search, string comparison and text processing.
Yes. U+200B Zero Width Space is a recommended removal candidate in this tool. Other invisible characters may have legitimate uses, so they are handled more conservatively.
No. Characters such as the Zero Width Joiner, Zero Width Non-Joiner and directional controls can be meaningful in some languages, emoji sequences and bidirectional text. CountFlows detects these characters but does not automatically select them for removal.
Invisible or unusual Unicode can enter text through websites, word processors, PDFs, messaging apps, rich-text editors, source code, file encodings and copy-paste operations. Their presence alone does not identify where the text originally came from.
They can cause problems when software compares the underlying character sequence. Hidden Unicode may affect exact string matches, identifiers, search, validation, copied commands or structured data even when the visible text looks normal.
No tool should imply that every Unicode character that may render invisibly in every font or context is covered. CountFlows detects the supported zero-width, unusual-space and directional characters defined by its scanner and reports exactly what it finds.
The detection and cleanup logic run in your browser and do not require an AI API or server-side text analysis.