Copy The Invisible Character And Check Where It Works
Use this page to copy the U+3164 Hangul Filler character, understand what it is, and check how hidden Unicode characters behave across apps, forms, and websites.
Click the button above to copy the invisible character to your clipboard.
What is this character?
This tool copies the Unicode Hangul Filler character. It looks blank, but many apps still treat it as a valid character.
Where people use the invisible character
Hidden Unicode reference
Understand what U+3164 is, how it differs from a normal space, and why some systems still count it as a visible character.
Compatibility checks
See where apps allow, strip, or normalize hidden characters before you rely on them in forms or profile fields.
Developer and QA testing
Use the copied character to test sanitization, rendering, exports, and hidden-character handling in text systems.
Ready-made invisible character examples
Tap any template to copy a version with the invisible character already inserted.
Related tools
Character Counter
Count visible graphemes before testing invisible characters inside a limited field.
Free Fire Invisible Space
Use the gaming-focused page for Free Fire names and nickname spacing.
Nickname Fonts
Create stylish names for games, profiles, and social platforms.
Font Generator
Open the full font generator for fancy letters and copy-ready Unicode text styles.
Frequently asked questions
Is U+3164 the same as a normal space?
No. It looks blank, but it is a different Unicode code point, so systems can treat it differently from a standard keyboard space.
Will every app preserve this invisible character?
No. Some apps keep it, some remove it, and others normalize it during validation, storage, or rendering.
Why do some tools call it Hangul Filler?
Because the code point U+3164 is officially named Hangul Filler in Unicode, even though people often use it as an invisible character.
Is it safe to copy and test?
Yes. It is a standard Unicode character, not a script or exploit, but you should still test platform compatibility before using it at scale.