Zero-width controls
No-width separators, line-break hints, and Unicode behavior tests.
Examples: Zero Width Space, Zero Width Non-Joiner, Zero Width Joiner
Open the exact toolUse this character hub to compare common invisible Unicode characters, copy a specific blank-looking character, and test whether your pasted output is preserved. Start here when you are not sure whether you need a zero-width control, one blank character, a Unicode space, or generated blank text.
The hierarchy is simple: homepage copy tool for the fastest start, this page for character taxonomy, invisible character for individual code points, blank character for one blank-looking unit, and invisible space character for spacing behavior.
Invisible characters are useful for Unicode testing, spacing checks, layout experiments, captions, bios, and display-name compatibility tests. They are not a privacy tool, and they should not be used for spam, impersonation, evasion, or misleading behavior.
No-width separators, line-break hints, and Unicode behavior tests.
Examples: Zero Width Space, Zero Width Non-Joiner, Zero Width Joiner
Open the exact toolSingle-character placeholders where a field may require text presence.
Examples: Hangul Filler and similar blank-looking Unicode characters
Open the exact toolVisible spacing, typographic gaps, non-breaking spaces, and layout tests.
Examples: Normal Space, No-Break Space, Thin Space, Em Space, Ideographic Space
Open the exact toolRepeated blank-looking output when one character is not enough.
Examples: Short, medium, or custom-length invisible text samples
Open the exact tool| User goal | Best first test | Go to |
|---|---|---|
| I need one blank-looking character | Start with Hangul Filler, then verify the code point | /blank-character/ |
| I need no visible width | Start with Zero Width Space and test the target field | /invisible-character/ |
| I need a visible spacing gap | Compare Normal Space, No-Break Space, Thin Space, and Em Space | /invisible-space-character/ |
| I need a longer blank-looking sample | Use a bounded generator instead of manually repeating characters | /invisible-text-generator/ |
| I need to debug a copied result | Paste it into the Test Box and inspect the count/code point behavior | /invisible-keyboard-input/ |
Invisible characters are normal Unicode text, but every app decides how to store and render them. The same character can be preserved in a browser field, removed by a mobile app, or shown as a square by a font that does not support the blank rendering.
| Where you paste | What can happen | Best diagnostic |
|---|---|---|
| Username or display-name field | May reject invisible-only values or require visible text | Test one character first, then try visible text plus a small spacer |
| Bio or caption editor | May trim leading/trailing spaces or collapse repeated whitespace | Preview after saving, not only while editing |
| Message or chat box | May remove zero-width characters or refuse blank-looking messages | Use short samples and follow platform rules |
| Rich text editor | May normalize Unicode spaces into normal spaces | Compare against Normal Space and check after publishing |
| Mobile app vs desktop app | Rendering and trimming can differ by client | Test the device where the text will be viewed |