Which character Free Fire accepts
Free Fire accepts U+3164. Free Fire charges the rename on submit. Paste the character into in-game chat first to confirm the client renders it blank.
The fallback is U+2800, which clears validators the first character does not. Both survive trim(), which is the operation that destroys an ordinary space.
The field caps at 12 characters, and every invisible character counts as one. A name of 12 invisible characters is the maximum Free Fire will store.
How to set it on Free Fire
To set blank text on Free Fire, copy the character above and paste it into a cleared field. The whole method is one paste — the cost is 390 diamonds or one name-change card, consumed when you submit rather than when it succeeds.
- Copy U+3164 from the tool above.
- Open Free Fire and tap your character banner, top-left.
- Tap the yellow pencil icon beside your nickname.
- Clear the field, paste, and confirm the rename.
On Android
Copy the character, open Free Fire, clear the field and long-press to paste. If the paste produces nothing, the keyboard's clipboard manager stripped it — copy from the browser directly rather than from a clipboard history panel.
On iPhone and iPad
iOS sanitises some pasted content between apps. Paste the character into Notes first, select it there, copy again, then paste into Free Fire. The second copy comes from a plain-text source and survives.
On desktop and emulators
Desktop clients paste the character unmodified, so the browser-to-app route works directly. Android emulators such as BlueStacks and LDPlayer share the host clipboard, and pasting into the emulator's own notes app first avoids the same stripping that affects physical devices.
Why an invisible character works where a space does not
One Unicode property decides it, and it is not the one most guides name. Every character carries a White_Space value of Yes or No, and that value determines whether trim() removes it.
The spacebar produces U+0020, whose White_Space value is Yes. Free Firetrims the field before saving, the trimmed value is empty, and the field falls back to its previous contents. That is why a name built from spaces looks correct in the editor and reverts the moment you save.
U+3164 has White_Space=No. No trimming function removes it and the regex class \s does not match it, so the value that reaches the server is the value you pasted.
One caveat applies to U+3164 specifically. Normalization Form NFKC folds it to U+1160 Hangul Jungseong Filler, so a platform that normalizes before storing keeps a different codepoint than the one you pasted. The name still displays blank. Use U+1160 directly if you want the stored value to match exactly.
What it costs on Free Fire
390 diamonds or one name-change card, consumed when you submit rather than when it succeeds. Test the character in a free-text field first — a rejected rename is charged the same as a successful one.
If it does not work on Free Fire
If the game rejects it, pair the character with one visible symbol, or switch to U+2800 Braille Pattern Blank.
The field clears itself after saving
Free Fire trimmed the value and found an empty string, so it restored the previous one. The character you used has White_Space=Yes. Switch to U+3164 or U+2800, which do not, and the value survives the trim.
A box or question mark appears
The rendering font has no glyph at that codepoint, so the renderer draws.notdef — an empty rectangle in most fonts. The stored value is correct and only the display is wrong. U+2800 carries wider font coverage than most alternatives.
The paste produces nothing on mobile
The keyboard or clipboard manager sanitised the content in transit. Paste into a plain-text notes app first, copy from there, then paste into Free Fire. This is the single most common practical failure and it has nothing to do with the character itself.
It works on desktop and fails in the app
The two clients validate separately. A value the desktop site accepts can still be rejected by the mobile client's own check, and the reverse also happens. Set it on whichever client accepts it — the stored value is shared.
Full property data for both characters is on the Unicode invisible characters table.
Is a blank name allowed on Free Fire?
Yes. A blank name breaks no Free Fire rule. Platform policies restrict impersonation, harassment and filter evasion, not which codepoints a name contains.
Two uses do violate policy on Free Fire and on every comparable platform, and neither depends on the name being blank. Copying another user's name to pass as them is impersonation. Splitting a blocked word with a zero-width character to defeat moderation is evasion.
One consideration applies regardless of the rules. Screen readers announce nothing for an invisible character, so NVDA, JAWS and VoiceOver read a fully blank name as unnamed. Keeping one visible character alongside the invisible ones preserves the announcement and still looks almost blank.