Invisible Character Detector
Detect and remove hidden Unicode characters, zero-width spaces, and non-printable characters that cause formatting issues.
Related Tools
How to Use
- Paste Suspicious Text — Paste text that behaves unexpectedly — failing string comparisons, showing odd spacing, or triggering encoding errors.
- Scan for Hidden Characters — Click Detect Characters to reveal all invisible Unicode code points, zero-width characters, and control characters embedded in your text.
- Review and Clean — Examine each detected character with its Unicode name and line:column position, untick any types you want to keep, then clean the rest with one click. Special spaces become normal spaces so words never run together, and the cleaned text can be copied or downloaded.
About the Invisible Character Detector
The Invisible Character Detector finds characters you cannot see: zero-width spaces, byte order marks, direction overrides, control codes and spaces that only look like spaces. It lists each one with its code point and line:column position, marks it inside your text, and cleans the ones you select. Developers use it when two strings that look identical refuse to match. Editors and data teams use it when pasted text breaks imports, word counts or search.
What it detects
The scan reads your text one Unicode code point at a time and sorts every hit into one of seven groups. The group decides what cleaning does with it.
| Group | Examples | Cleaning |
|---|---|---|
| Zero-width / format | U+200B zero-width space, U+200C/U+200D joiners, U+FEFF byte order mark, U+00AD soft hyphen, U+2060 word joiner, U+3164 Hangul filler | Removed |
| Bidirectional control | U+200E/U+200F marks, U+202A–U+202E embeddings and overrides, U+2066–U+2069 isolates, U+061C | Removed |
| Control character | U+0000–U+001F (except tab, line feed and carriage return), U+007F, U+0080–U+009F | Removed |
| Variation selector | U+FE00–U+FE0F, U+E0100–U+E01EF | Removed |
| Tag character | U+E0000–U+E007F | Removed |
| Special space | U+00A0 no-break space, U+2000–U+200A, U+202F, U+205F, U+3000, U+1680 | Normal space |
| Line/paragraph separator | U+2028, U+2029 | Line break |
A special space becomes a normal space, but it is dropped when a normal space already sits next to it, so cleaning never leaves a double space. Joiners and selectors that belong to an emoji are recognized and left alone: the zero-width joiners inside 👨👩👧, the variation selector in ❤️ or a keycap like 1️⃣, and the tag characters of subdivision flags. The scan reports how many of those it skipped.
Worked example
Three pasted lines that look normal on screen, shown here with the hidden characters in brackets:
[U+FEFF]Price:[U+00A0]$20
user[U+200B]name = admin[U+202E]txt.exe
👨👩👧 ❤️ 2[U+2009]000
The report says 5 invisible or special characters found. 3 more belong to emoji sequences and are kept. The table is sorted by count, then by code point:
| Character | Code point | Position | Cleaning |
|---|---|---|---|
| No-Break Space | U+00A0 | 1:8 | Replace with normal space |
| Thin Space | U+2009 | 3:11 | Replace with normal space |
| Zero-Width Space | U+200B | 2:5 | Remove |
| Right-to-Left Override | U+202E | 2:18 | Remove |
| Byte Order Mark / Zero-Width No-Break Space | U+FEFF | 1:1 | Remove |
Columns count code points, so each emoji part counts as one column; that is why the thin space on line 3 sits at column 11. After cleaning, line 2 reads username = admintxt.exe and the family emoji is unchanged.
Limitations
- It finds invisible characters, not lookalikes. A Cyrillic а posing as a Latin a is a visible letter and is not flagged.
- Only the code points listed above are checked. Other blank-looking characters, such as the Braille blank U+2800 or the object replacement character U+FFFC, are not reported.
- Some of these characters are correct in context. Persian and several Indic scripts need the zero-width non-joiner and joiner for proper spelling, and French typography puts a no-break space (often the narrow U+202F) before
; : ! ?. Untick those rows before cleaning. - The position list shows the first ten places for each character. The highlighted text shows all of them.
Practical tips
- When a lookup, JSON key or variable name fails to match, paste both versions here. A U+200B or U+FEFF inside one of them is the usual culprit.
- Check code you copied from chat apps or web pages for U+202E and the other bidirectional controls. They can make source code display in a different order from how it runs (the "Trojan Source" technique).
- Copy report gives one line per character type, ready to paste into a bug ticket.
- After cleaning, use Remove Extra Spaces for ordinary spacing problems, or Find and Replace to change one specific character.
- For a complete cleanup routine (spaces, line breaks, duplicates and encoding), see the Text Data Cleaning guide.
The scan and cleanup run entirely in your browser, so the text you check is never uploaded.
Frequently Asked Questions
What types of invisible characters does the tool detect?
The tool detects zero-width spaces (U+200B), zero-width non-joiners (U+200C), zero-width joiners (U+200D), byte order marks (U+FEFF), soft hyphens (U+00AD), non-breaking spaces (U+00A0), right-to-left and left-to-right marks (U+200F, U+200E), bidirectional embedding, override, and isolate controls (U+202A to U+202E, U+2066 to U+2069), variation selectors (U+FE00 to U+FE0F), invisible tag characters (U+E0000 to U+E007F), unusual spaces such as en, em, and thin spaces, and the Unicode control characters in the C0 and C1 ranges (except tab, line feed and carriage return, which are normal text formatting), among others. Joiners and selectors that are part of an emoji, such as a family or flag emoji, are recognized and left alone.
How do invisible characters get into my text?
They are introduced by copy-pasting from web pages, word processors, PDFs, and messaging apps. Some websites deliberately insert zero-width characters to fingerprint copied text and detect plagiarism. Rich-text editors may add byte order marks or directional markers automatically.
Can invisible characters cause bugs in my code?
Absolutely. A zero-width space in a variable name, JSON key, or file path creates a string that looks identical to the naked eye but fails every comparison. These characters are a notorious source of hard-to-diagnose bugs in programming, database queries, and configuration files.
How does the tool display invisible characters?
Each detected character is highlighted in the text with a colored marker. A detailed table lists every invisible character found, showing its first positions as line:column, Unicode code point (e.g., U+200B), Unicode name, a brief description of its effect, and what cleaning will do with it.
Are non-breaking spaces (U+00A0) considered invisible characters?
Yes. Non-breaking spaces look identical to regular spaces but have different Unicode code points. They prevent line breaks between words, which is sometimes intentional, but they can also cause unexpected behavior in search, comparison, and data-import operations. The tool flags them so you can decide whether to keep them (untick them before cleaning) or normalize them. Cleaning replaces non-breaking and other special spaces with a normal space rather than deleting them, so words never merge.
Can this tool detect text fingerprinting or steganographic content?
Yes. Some publishers embed unique sequences of zero-width characters into text to trace unauthorized copying. The detector reveals these hidden fingerprints, showing exactly where they are placed and what characters are used, allowing you to identify and remove tracking markers from copied content.