An invisible name is not a hack or a glitch. It is a real Unicode character that occupies space without drawing anything, and every app that shows a blank name is simply rendering it correctly. Here are the characters that work, why some of them fail, and what to do when the field rejects all of them.
Last updated: 13 September 2026 · NameStylish editorial team
The characters — tap to copy
Each box below holds one invisible character. They look empty because they are meant to. Tap one to copy it, then paste it into the name field.
Nothing appears between the quote marks because that is the entire point: "ㅤ" above contains a character. If the field rejects the first one, work down the list — they behave differently and that is explained below.
Which blank character for which app
The right invisible character depends on the app, and for Free Fire the usual advice is wrong. Free Fire has blocked the Hangul Filler (U+3164) since the OB43 update; the character that still gives a blank Free Fire name is U+00A0, the no-break space, checked against OB54. Everywhere else, the order in the table above still applies.
| Where | Try first | Avoid | Why |
|---|---|---|---|
| Free Fire in-game name | U+00A0 no-break space, six in a row | U+3164 Hangul Filler | U+3164 blocked since OB43; paste U+00A0 twice if the field trims it |
| Fields that demand at least one letter | U+3164, then U+FFA0 | U+200B zero width space | Fillers are classed as letters; zero-width characters are formatting and get stripped |
| Fields that trim spaces | U+2800 Braille blank | U+3000 ideographic space | U+2800 is a symbol, not whitespace, so trimming leaves it alone |
| Fields that refuse a blank name outright | A gap plus one small visible mark | Any fully blank name | A single mark satisfies the rule; see the gap kit below |
Why one works and another does not
All six are invisible to look at. To software they are completely different things, which is why one sails through and the next is rejected by the same field.
| Character | What Unicode calls it | How software treats it |
|---|---|---|
| U+3164 | Hangul Filler | A letter. Passes filters that demand letters and reject whitespace — the reason it is the classic choice |
| U+2800 | Braille Pattern Blank | A symbol with no dots raised. Also not whitespace, and widely supported |
| U+FFA0 | Halfwidth Hangul Filler | Like U+3164 but a different code point — useful when the first is specifically blocked |
| U+1160 | Hangul Jungseong Filler | A combining vowel filler. Can merge with a neighbour rather than standing alone |
| U+200B | Zero Width Space | Formatting, not a character. Stripped by most modern filters |
| U+3000 | Ideographic Space | Genuinely whitespace, and wide. Trimmed by anything that trims spaces |
That third column is the whole explanation. A name field that requires at least one letter and forbids blank names will accept U+3164, because to the software it is a letter. The same field will reject U+200B, because to the software that is not a character at all — it is an instruction about line breaking, and trimming it is the correct behaviour rather than a bug.
So when someone says “the invisible name trick stopped working”, what has usually happened is that they were using a zero-width character and the app added trimming. The filler characters are far more durable because they are not whitespace in the first place.
Why a plain space does not work
The obvious first attempt is to press the spacebar. It never works, and the reason is worth knowing because it explains the whole category.
Essentially every name field trims leading and trailing whitespace before saving — not to stop you, but because it prevents “John” and “John ” from being two different accounts. A name made only of spaces trims down to nothing, and an empty name is rejected as empty.
The filler characters slip past that not by being sneaky but by not being whitespace. Nothing is being defeated; the field is doing exactly what it was written to do.
Space characters, by width
If a filler is rejected but you still need a gap, the next thing to try is a space character of a different width. Unicode defines a whole family of them, and a name field that trims the ordinary space often leaves these alone because they are distinct characters rather than the space key.
Each button below holds one. They differ in width, which is the point — and every one still counts toward the field’s character limit.
Two behave differently from the rest and are worth knowing. No-break space (U+00A0) is the one most likely to survive trimming, because its whole purpose is to resist being treated as an ordinary break — but it is still classified as whitespace, so a strict field will remove it. Figure space (U+2007) is exactly as wide as a digit, which makes it the neat choice when you are aligning something numeric.
The last two are not spaces at all — they are the fillers from the top of this page, repeated here so you can compare widths in one place. Those two are the ones to reach for when everything else gets trimmed.
What this will not do
Worth being straight about, because a blank name attracts some ideas it should not.
It does not hide you. Your account still has an ID, moderators still see it, and a blank display name does not remove you from a report. It does not make you unbannable, and it is not a way around a name restriction you were given for a reason. If an app has explicitly forbidden blank names, using a filler to get one anyway is against its rules, and that is between you and them.
It also cannot be used to impersonate. A blank name that mimics an official or empty-looking system account is impersonation regardless of how it was made, and our editorial policy covers why we will not help with that. Everything on this page is here for the ordinary reason: some people want a clean profile.
And to say the obvious once: nobody should ever ask for your account, player ID or password to give you a blank name. There is nothing to log into. You copy a character and paste it yourself.
12 frames to hold the gap open
The most common use of a filler is not a fully blank name but a controlled gap — a clan tag held apart from a nickname, or an indent that ordinary spaces would collapse. Paste a filler from above where you want the gap, and one of these either side of the visible part.
These are tier 1 frame characters — the safest category, because your letters stay ordinary and only the decoration is unusual. Which of them a given field accepts is covered in which symbols survive a name field.
Pairing it with a styled name
The more common use is not a fully blank name but a gap inside one — separating a clan tag from a nickname, or holding an indent that ordinary spaces would collapse. Filler characters keep that gap because nothing trims them.
Build the visible part on NameStylish, then paste a filler where you want the gap. It works the same way in a Free Fire name, a PUBG or BGMI clan tag, or an imo group name.
Try it with your own name
The generator lives on the front page — type your name once and it comes back in dozens of styles, each with a copy button. There is no account and no sign-up. Being straight about the one thing that does leave your device: the name you type is sent to the service that styles it, and a copy is counted on our own server for up to 35 days, which our privacy policy sets out line by line.
Gap kit — marks, faces and names with the gap built in
A blank character on its own is fragile: a field can trim it from either end, or refuse a name with nothing visible in it. The fix in both cases is a visible edge — one small mark on the outside of the gap — and that is what this kit is for. Everything here is copy-ready and none of it is a letter in disguise.
Tiny marks for a nearly-blank name 38
If a fully blank name is refused, one small mark beside the gap usually satisfies a “must contain a visible character” rule while still reading as almost empty. Clouds, moons, snow and small creatures — one to three characters each.
Faces that sit beside a gap 15
Short enough to leave room for a filler and a name in a 12-character box. A face is punctuation rather than letters, so it never trips a letters-only rule.
Short trails to put after the gap 17
A gap followed by a small trail reads as deliberate spacing rather than a mistake — useful when a blank name on its own looks like an error to other players.
Divider lines for a bio gap 20
For the space between lines of a bio rather than inside a name. Too long for most name fields.
Names with a gap already built in 20
Each one holds a real gap character (U+2800, the Braille blank) between a frame and a styled name, so the spacing survives pasting. For Free Fire, swap that gap for the no-break space in the Free Fire row above.
FAQ
Which one should I try first?
It depends on the app. For Free Fire, use U+00A0, the no-break space — U+3164 has been blocked there since OB43. Names with that space already placed between words, letters and frames are on the Free Fire space page. Almost everywhere else, U+3164 (the Hangul Filler) has the widest record of being accepted because software classifies it as a letter rather than as space; if it is rejected, try U+2800 next.
I pasted it and the field still says the name is empty.
The app trimmed it, which means it is treating that character as whitespace. Move to U+3164 or U+2800 if you were not already using them — those two are the least likely to be trimmed.
Will my name look blank to everyone?
To anyone whose device has a font covering that character, yes. On a device without it you may get a box instead of nothing, which is the opposite of what you wanted — the same rendering issue that affects styled names showing as boxes.
Can I use several to make a wider gap?
Yes, and each one counts toward the field’s character limit, so a wide gap eats the room you needed for the name.
Is this against the rules?
It depends on the app, and it is worth checking. Many are indifferent. Some forbid blank names outright, in which case using a filler to get one is a rules violation even though nothing is technically broken.