An invisible character for BGMI is a real Unicode code point — most commonly U+3164 (Hangul Filler), U+200B (Zero-Width Space), U+200C (Zero-Width Non-Joiner), or U+200D (Zero-Width Joiner) — that has no visible glyph in the fonts BGMI bundles, so the resulting name field looks blank even though the engine is not seeing an empty string. Battlegrounds Mobile India's name input accepts ordinary text, including these non-printing code points, until its own filters strip them at save time. The practical way to set one up is to pick the exact character you want by name and code point, copy that one character with a single click, paste it into BGMI's rename field, and preview before confirming. If a saved name later behaves oddly in chat, the friends list, or the lobby — for example showing a tofu box, a question mark, or a strange gap — paste it back into a local inspector to read which invisible code points are still there, where each sits, and whether the game kept them or replaced them with something else.
What BGMI's Name Field Actually Accepts
BGMI's rename dialog is a normal Unicode text field with a visible length limit and a small list of obviously abusive characters blocked at save. Outside that block list, the field accepts whatever code points your keyboard or paste buffer can deliver, including the family of blank-looking Unicode characters that render as nothing in the fonts bundled with the game. That is why a name like a single zero-width space is technically a one-character string to the engine, even though the on-screen result looks empty.
Two practical facts follow from this. First, a "blank" BGMI name is never actually empty — it is a string of one or more non-printing code points the engine is being asked to store. Second, BGMI's save pipeline may normalise, strip, or replace those characters depending on the build, the platform, and how the rename was sent. A character that looks blank in the rename box can appear as a placeholder glyph, a narrow gap, or nothing at all once the name is shown in lobbies, kill feeds, or chat.
Players who want a clean invisible name usually pick a single Hangul Filler (U+3164), because its long history of being used in this exact role means it is well tested against current and older BGMI builds. Players who want a partly blank name — for example, a clan tag followed by a gap and a nickname — tend to use U+200B, U+200C, or U+200D, which behave as true zero-width joiners between the visible characters on either side.
The Six Characters That Make BGMI Names Look Blank
Six specific Unicode code points cover almost every blank-character use case in BGMI names. Each one is a named, fixed code point with a documented purpose; none of them are a hack or a private engine symbol. Knowing the code point in advance is what lets you verify what your clipboard actually holds before you paste it into the rename dialog.
| Label | Code point | Common role in BGMI names |
|---|---|---|
| No-break space | U+00A0 | Renders as a narrow gap; the engine often treats it as ordinary whitespace. |
| Zero-width space | U+200B | Standard zero-width marker; used as a clean separator between visible characters. |
| Zero-width non-joiner | U+200C | Used to break ligatures or shaping; popular as a true invisible joiner. |
| Zero-width joiner | U+200D | Mirrors U+200C; useful for partially blank names that include emoji. |
| Word joiner | U+2060 | Behaves like U+200B in most game engines; sometimes kept where ZWSP is stripped. |
| Hangul filler | U+3164 | The most widely used "looks empty" code point in BGMI and PUBG-style names. |
Hangul Filler is the choice most guides recommend for a fully invisible name, because it has no shaping behaviour, no line-break effect, and no ligature logic. Zero-width characters are the choice for names that need a gap inside visible text, because they sit between real letters without changing how those letters are drawn. The other two — no-break space and word joiner — are useful when one of the zero-width options has been filtered by a specific build, since they exercise different parts of BGMI's text pipeline.
How to Copy an Invisible Character for BGMI
The reliable workflow is to pick a single named character, copy that exact code point, paste it once into the BGMI rename field, and read the in-game preview before saving. Use the Invisible Character tool to keep that step deliberate:
- Open the Invisible Character page in your browser. Pick the character card that matches the look you want — Hangul Filler for a fully blank name, or a zero-width option for a name with an internal space.
- Read the label and the hex code point printed on the card so you know exactly which Unicode character is about to land on your clipboard.
- Click Copy on that card. The page places exactly one of that code point on your system clipboard — no surrounding whitespace, no extra zero-width joiners, no normal spaces.
- Open BGMI, go to your profile, and tap the rename option. Long-press the name field to bring up the paste option, or use the platform's paste shortcut.
- Paste the single copied character into the name field. Read BGMI's preview carefully — the preview is the game's own statement about what will be saved and shown to other players.
- If the preview shows nothing, save the name. If the preview shows a square, a question mark, or a real visible character, undo and try a different code point from the table above.
For a partly blank name, paste your visible prefix, copy a zero-width character from the same tool, paste it once as the gap, then paste your visible suffix. The result is one continuous Unicode string that BGMI renders with a visible gap and no obvious separator.
Inspecting a Name Before You Confirm It
Whenever a saved BGMI name misbehaves — showing a tofu box, refusing to match in search, or appearing wider than you typed — paste it back into the text inspector on the same Invisible Character page. The inspector walks through the string one Unicode code point at a time, so emoji and combining marks are counted as single code points instead of being split into two UTF-16 units, and it flags only the six characters the tool advertises. Each detection is shown with its readable marker — [NBSP], [ZWSP], [ZWNJ], [ZWJ], [WJ], or [HF] — its one-based position in the string, and its hex code point.
That output answers three practical questions. It tells you whether BGMI kept the character you pasted or replaced it with something else. It tells you exactly where the invisible character sits when a friend list search behaves as if the name is shorter than expected. And it tells you the real length of the name, which matters because BGMI's on-screen count and its stored count can drift apart when non-printing code points are involved.
Cleaning a Name the Game Won't Save
If BGMI's preview or save flow rejects a name, the fastest recovery is to remove the invisible characters and start from a clean visible string. The Remove listed characters button on the same page deletes only the six code points in the table above — it does not touch ordinary spaces, tabs, line breaks, punctuation, letters, digits, emoji, or any other Unicode character. That preservation matters because BGMI name rules allow real spaces in some regions and contexts, and stripping those by accident would change how the name is meant to read.
Review the revealed version before copying it back. A zero-width non-joiner or joiner can be intentional in a language with shaping behaviour, a no-break space can be intentional in typographic rules, and a word joiner can be the only thing holding a two-word nickname together. Use removal only when the destination text — in this case BGMI's rename pipeline — is known to treat those code points as noise rather than meaning. For related game contexts, the Invisible Character for BG3: Copy, Reveal, and Remove guide walks through the same workflow against a different engine.
Why Rendering Is Not Behaviour
A character that looks blank in the rename box can still affect how BGMI handles the name behind the scenes. Search, copy and paste, friend matching, moderation filters, and screen-reader output all see the underlying code point, not the empty rectangle in the preview. Two strings that look identical to a player can differ in length, search behaviour, or accessibility output if one of them contains an invisible code point and the other does not.
Rendering is also not fixed across platforms. The same code point may appear blank in BGMI's font, show a replacement glyph in another game's font, be normalised away by a desktop editor, or be stripped by a website form. Treating the in-game preview as the only source of truth — and inspecting the saved string with the tool whenever something looks wrong — is the safest way to keep the name you intended without guessing what the engine is actually storing.