U+3164 Hangul Filler: the technical story behind the "invisible name" trick
U+3164 is a single Unicode codepoint with an outsized reputation in Free Fire communities. It looks like blank space but is technically not the space character (U+0020), and that distinction is the entire reason it ever worked as a workaround. Here is what U+3164 actually is, why it stopped working in Free Fire after 2024, and what the realistic alternatives are now.
What U+3164 actually is
In the Hangul Jamo block of Unicode, U+3164 is the "Hangul Filler", a placeholder character used in Korean text input systems when a syllable block is incomplete. It is not a space, it is not punctuation, and it has zero visible width in most fonts. In Korean typography it is functionally a non-character; in non-Korean contexts it became famous for a different reason.
Because U+3164 renders invisibly but is not classified as whitespace by most text validators, it was the perfect bypass for games that disallowed empty or whitespace-only names. Players would paste U+3164 into the Free Fire name field and get an "invisible" in-game name. Visible to nobody, including the kill feed.
Why Free Fire blocked it (and when)
Garena patched U+3164 acceptance in stages through 2024. The motivation was straightforward: blank names made the game harder for teammates and opponents to communicate around. Pro players asked for the change; competitive integrity required it. By the end of 2024, the in-game name filter explicitly pattern-matches U+3164 and rejects names that consist entirely or majority of it. The same patch wave also caught other Unicode "blank" characters, U+200B (zero-width space), U+200C (zero-width non-joiner), U+200D (zero-width joiner), U+FEFF (zero-width no-break space).
A small loophole remained briefly: names containing both U+3164 and a visible character (say, a single dot) were accepted. By mid-2025, the filter caught those too. The "invisible name in Free Fire" workaround is, in 2026, dead in every region. Any tutorial promising otherwise is outdated.
What you can still do with U+3164
The codepoint still works in other places: WhatsApp display names accept it, Instagram accepts it in some bio fields, Discord nicknames in some servers accept it. If your goal is an "invisible" presence on a non-Garena platform, U+3164 is still useful. The page above provides a single-click copy of the character.
A second use: a U+3164 between two Latin characters can sometimes create unusual spacing in Instagram captions that the standard space character will not produce. Designers who want a particular visual rhythm in a profile sometimes lean on it.
Alternatives that work in Free Fire today
If the appeal of the invisible name was anonymity in the kill feed, the closest modern substitute is a one-character name composed of a hard-to-spot Unicode symbol. For example a single tiny dot (⸱, U+2E31) or a single hyphen-minus. These pass the filter and read in the kill feed as nearly nothing. They are not invisible, but they are easy to overlook.
If the appeal was novelty, lean into elaborate decoration instead. ꧁ ꧂ brackets with a single short word inside read as polished and remain compatible across every Free Fire patch we have tracked from 2022 through 2026. Spend the creativity on what is visible rather than on what is hidden.