Hangul Filler (U+3164)
The Hangul Filler is a Korean letter that draws nothing, so it passes checks that reject empty or space-only text.
U+3164Lo · letterhas width
Need the code?HTML, CSS, JS escapesFind it in text
An app result is shown only after a hand test on a named app version, with the date. Results older than 120 days are hidden until re-tested.
Read the method →What is the Hangul Filler used for?
The Hangul Filler (U+3164) is used as a blank that apps still read as text. It is a Korean letter that draws nothing, so it fills blank names, empty messages and spacing where a normal space gets trimmed. It sits in the Hangul Compatibility Jamo block and has been in Unicode since version 1.1.
Its name in the Unicode names list is chaeum, Korean for filler. It sits in the Hangul Compatibility Jamo block and has been part of Unicode since version 1.1.
Unicode classes it as a letter (Lo) and as Alphabetic, not as whitespace. That is why JavaScript's trim() and the \s pattern in regular expressions leave it alone while they remove ordinary spaces.
It is also a Default Ignorable Code Point. Software with no special handling for it should draw nothing at all, which is why it looks empty wherever you paste it.
NFKC normalization, used to compare look-alike text, turns U+3164 into U+1160, the Hangul Jungseong Filler. The result is still a blank letter, so a normalized name keeps its blank.
Watch out for
- An app can still refuse a name made only of Hangul Fillers, because each app sets its own name rules.
- In UTF-8 it takes 3 bytes (E3 85 A4), so a field with a byte limit fills three times faster than with plain letters.
- It looks like a plain space on screen. Paste text into the detector to see exactly where it is.
Sources: Unicode character data (UnicodeData.txt) · Unicode properties (PropList.txt) · Unicode blocks (Blocks.txt) · Unicode version each character arrived (DerivedAge.txt) · ECMAScript: white space · Unicode names list (NamesList.txt) · Unicode derived properties (DerivedCoreProperties.txt) · Default Ignorable Code Points (UAX #44) · Unicode normalization (UAX #15) · Computed from the character itself (see Codes and escapes)
Codes and escapes
| Format | Value | Copy |
|---|---|---|
| HTML entity | ㅤ · ㅤ | |
| CSS | \3164 | |
| JavaScript / Java | \u3164 | |
| Python | \u3164 | |
| URL-encoded | %E3%85%A4 | |
| UTF-8 bytes | E3 85 A4 |
Properties
- Unicode category
- Lo (Letter, other)
- Treated as whitespace
- No
- Width
- Takes up space
- Unicode name
- HANGUL FILLER
Where it works
Not tested yet. Results appear here with the app version and date once each app is tested by hand.
Similar characters
FAQ
How do I type the Hangul Filler?
You can't type the Hangul Filler on most keyboards, so copy it with the button at the top of this page and paste it where you need it. In code, write it as \u3164 in JavaScript or ㅤ in HTML. It takes 3 bytes in UTF-8, which matters for fields with a byte limit.
How do I remove Hangul Fillers from text?
To remove Hangul Fillers from text, paste it into the detector, which lists every U+3164 and deletes them in one tap. In JavaScript, text.replace(/\u3164/g, '') does the same. trim() won't help here, because the Hangul Filler is a letter, not whitespace.
What is the difference between the Hangul Filler and a normal space?
The main difference between the Hangul Filler and a normal space is that Unicode classes the filler as a letter. Code that trims or collapses spaces leaves it in place, while a normal space at the start or end of a field is removed. Both look blank, but only one survives a blank-name check.