Empty character: copy a real codepoint

Bottom line: “empty character” is a useful nickname, not a Unicode category

There is no official Unicode character named Empty Character. People use the phrase for characters that render with no visible mark, occupy blank width, or make an otherwise empty field contain text. U+3164 Hangul Filler is a practical example because many fonts draw it as an empty cell. U+2800 Braille Pattern Blank is another because its braille pattern has no raised dots. U+200B Zero Width Space has no width but serves a line-breaking purpose. These are different characters with different semantics.

That distinction matters whenever software validates, searches, shapes, or stores the text. A field may accept a filler and reject a formatting control. A search engine may treat a zero-width space as a boundary. A script-aware renderer may use joiner or non-joiner to change letter forms. Calling all of them empty is convenient for discovery, but choosing one safely requires looking at the codepoint and its intended role. The table gives you both rather than presenting a mysterious blank box.

How to copy, inspect, and test an empty character

Press the main button to copy one U+3164 Hangul Filler. Paste it into the test textarea. The field may look unchanged, but the counter should display one. Select the textarea contents to expose the highlighted selection width. You can then repeat the test with another row. U+200B may create almost no visible selection, while U+3000 creates a much wider highlight. Those differences help confirm that the browser received distinct characters.

For a technical inspection, record the codepoint before you paste. The label U+2009, for example, identifies Thin Space independently of how a particular font draws it. If an application changes the character, paste the saved output back here and compare the count, then inspect it in a Unicode-aware editor or programming language. A visual comparison alone is not enough because several blank characters can appear identical at ordinary zoom levels.

The generator repeats U+3164 for tasks that require an empty-looking string rather than one character. Use it conservatively. A repeated filler occupies string length and may occupy layout width. It is not equivalent to null, an empty database value, or a missing form control. If you are developing software, represent absence with the data type your system defines and reject or normalize unexpected format controls explicitly. This page is a copy and diagnostic tool, not a substitute for input validation.

Applicability checklist for empty-looking characters

• Nickname fields: U+3164, U+115F, and U+1160 are fillers worth testing when permitted by the game.
• Whitespace-only message checks: U+2800 may be treated as a non-space symbol while rendering blank.
• Preventing a line break: U+00A0 has the relevant behavior; use it between words that should stay together.
• Optional break opportunity: U+200B may allow a line break without displaying a space.
• Script shaping: U+200C and U+200D are meaningful controls, not general empty placeholders.
• Source files: treat U+FEFF carefully because tools may interpret it as a byte-order mark at the beginning.

For social media spacing, an empty-looking character can help preserve a line that the editor would otherwise remove. For chat, it can demonstrate how a validator distinguishes blank rendering from empty data. For games, it may create a gap inside an allowed nickname. For testing, it is useful in cases involving trimming, normalization, line wrapping, cursor movement, and search. The same character should not be assumed appropriate across all of those contexts.

Common misconceptions about empty characters

The first misconception is that an empty character is the same as an empty string. An empty string has length zero. A string containing U+3164 has at least one codepoint, even when its rendered area looks blank. This affects required-field checks, database uniqueness, character limits, equality comparisons, and user-interface counters. If two blank-looking names are considered different, they may contain different codepoints or different counts of the same one.

The second misconception is that zero width means zero impact. Joiners can change glyph formation, zero-width space can change wrapping, and invisible marks can disrupt exact string matching. Screen readers may pause, ignore, or announce unusual content depending on context. Moderation and fraud systems may flag unexpected invisible characters because they are sometimes used to disguise text. Use them transparently and avoid placing them inside words unless you understand the linguistic effect.

The final misconception is that copying from any blank area produces the intended value. Web pages include layout whitespace, CSS spacing, and selectable characters that can look alike. Use a labeled button tied to a documented codepoint. After copying, verify the character count and the destination’s saved state. If the app removes the value, that is valid platform behavior. Trying a different codepoint can test compatibility, but it should not become an attempt to defeat a rule.