Hangul Filler
U+3164- Behavior
- Visible-width blank
- Use
- Useful when a real character should look blank but still have presence.
- Note
- Best first test for one occupied blank-looking character.
Single blank character
This page is intentionally one-character focused. Use it when you want one blank-looking Unicode code point, not repeated blank text or a generated block.
A single-character test should show one copied Unicode unit in the Test Box. If you need multiple units, use the blank text or generator pages.
U+3164U+200BU+00A0U+FEFFU+3000A blank character is one Unicode code point that appears blank or invisible when pasted into a field or message. This page is focused on single-character precision: you copy exactly one code point, confirm what it is, and test how a specific app handles that exact character before committing to it.
When precision matters, always confirm the code point before using it:
1. Copy the character from the tool above.
2. Paste it into the Test Box on this page.
3. Read the character count (should be exactly 1) and the code point label.
4. Confirm the Unicode name and width category match your intent.
5. Transfer the confirmed character to your target field.
This matters because different blank-looking characters behave very differently: a Zero Width Space (U+200B) has no width and is often stripped by apps, while a Hangul Filler (U+3164) has full character width and is more likely to survive.
| Character | Code Point | Width | Typical Behavior |
|---|---|---|---|
| Zero Width Space | U+200B | Zero | Often stripped by apps |
| Zero Width No-Break Space | U+FEFF | Zero | Used as BOM; may be treated specially |
| Hangul Filler | U+3164 | Full | Survives many fields; appears blank |
| Braille Pattern Blank | U+2800 | Full | Survives many fields; appears blank |
| Ideographic Space | U+3000 | Full (wide) | Large blank area; CJK contexts |
| No-Break Space | U+00A0 | Normal | Survives most; not always blank-looking |
No blank character works universally. Always verify the code point first, then test in the exact field. Character behavior can differ between the mobile app, the web browser, and the desktop client for the same platform.
Compare blank text for any-length output, invisible space character for full spacing taxonomy, empty character for field-presence understanding, blank space for width selection, and invisible character guide for the full Unicode invisible character reference.