Create legendary PUBG Mobile and BGMI nicknames with esports wings, Japanese brackets, and godlike symbols.
Nothing on this page changes the typeface the game draws with. Every style here swaps each letter for a different character that only looks like a styled letter. Type A and you may get a heavier form that is not a bold A at all. It is mathematical bold capital A, its own code point at U+1D400, added in Unicode 3.1 in March 2001 so equations could be typeset in plain text. The gaming set here pulls from a few blocks. Most alphabets come from Mathematical Alphanumeric Symbols (U+1D400 to U+1D7FF). Decoration comes from elsewhere: Geometric Shapes at U+25A0 to U+25FF for arrows and triangles, CJK Symbols and Punctuation for the lenticular brackets at U+3010 and U+3011, and Unified Canadian Aboriginal Syllabics at U+1400 to U+167F, which supplies the angular shapes in clan wings, a syllabary written for Inuktitut and Cree, borrowed for its silhouette. Why that matters more in a game than in a chat app: the client stores no formatting flag beside your name. It stores substituted characters, and every system downstream reads them as what they are. The name filter, the friend search, the killfeed renderer and the spreadsheet a tournament organiser pastes your roster into do not see a styled S. They see mathematical bold capital S, and they behave accordingly.
The in-game name field is short. 14 characters is the figure players quote most often, and it is the right number to plan around, but confirm it on the rename screen in your own build, because caps move between versions and regions. Now the arithmetic, which decides everything else. Characters above U+FFFF live outside the Basic Multilingual Plane, and UTF-16 stores each of them as a surrogate pair: one unit from the range U+D800 to U+DBFF followed by one from U+DC00 to U+DFFF. Two units per visible letter. If the field counts UTF-16 code units, which is common behaviour for tightly capped fields, then fourteen units buy you seven mathematical letters rather than fourteen. A seven-glyph styled name is already fourteen units, full before you add a bracket. Not every style pays that tax. Circled letters from Enclosed Alphanumerics (U+2460 to U+24FF), fullwidth letters from Halfwidth and Fullwidth Forms (U+FF00 to U+FFEF), and the brackets and shapes above sit inside the BMP at one unit each, so a fullwidth name fits where a bold one will not, even though it looks wider on screen. Paste your candidate into the field and watch where the counter stops. That one test tells you which rule your build uses, and it is free.
On a social profile a bad name costs nothing. You edit it and move on. Here it costs an item. Changing your character name consumes a rename card: an inventory item you earn from an event or buy with premium currency, with accounts commonly given one free change shortly after they are created. Check what your account holds in the inventory screen first, and assume a cooldown between changes. That single fact reorders the whole job. A bio lets you paste a style, look at it and undo it in seconds; the loop is instant and free. Here the result is only visible after the card is spent, because the lobby, friend list and results screen render through the game client, not your keyboard. If the name lands as empty boxes, the fix is not an edit. It is another card. So treat spending it as the last step rather than the first. Pick the style here, count the code units against the cap, check your characters against the atlas problem described below, and get a teammate to look at the result on a different device before you commit. Testing costs minutes. Not testing costs an item you may have to grind or pay for, and a name you are stuck with.
The tag beside your name is a separate field with its own rules, and it is tighter than the name in every way. It holds a handful of characters rather than a dozen, it belongs to the clan rather than to you, and it is commonly restricted to a narrower character set, plain Latin letters and digits, sometimes uppercase only. Read the clan creation screen: it states the exact limit for your build and rejects disallowed characters as you type, not after you pay. That restriction is worth respecting rather than fighting. The tag is shown most often and at the smallest size (lobby lists, the label above your head, the killfeed, a tournament bracket) so it has the least room to survive a rendering fault. Styled letters that just squeeze into a fourteen-unit name will not fit a four or five character tag, and if the tag field counts UTF-16 code units the way the name field may, one mathematical letter consumes two of the very few slots you have. The answer most clans reach is the honest one: keep the tag in plain uppercase ASCII, where it renders on every client, and spend the decoration budget on the name, where you have more units to work with.
A browser can walk down a font stack until something covers a character. A game engine usually cannot. It draws text from a font atlas, a texture baked at build time from a fixed character set, and a character outside that texture has no picture to draw. What you get instead is the missing-glyph box, a blank, or a stray rectangle where a letter should be. This is why a name can be accepted at entry and still look broken afterwards. The name filter and the text renderer are different systems answering different questions. The filter asks whether the string is permitted; the atlas asks whether it holds a glyph for each character. A string can pass the first and fail the second, with no warning in between. Two consequences follow. First, the preview here is drawn with your browser's fonts, not the game's: it proves the characters exist, not that the client can draw them. Second, coverage varies by client, since Android, iOS and PC builds do not necessarily ship the same atlas, and atlases change between updates. A teammate can screenshot your name looking perfect while yours shows boxes. Test on the device you actually play on, then have someone check on a different one before calling a style safe.
The styles that hold up in game are the plain ones, and there is a mechanical reason. A one-for-one substitution replaces a character with a character: the atlas either has that glyph or it does not, and the answer holds for every letter. Bracket and separator decoration is safer still, since the punctuation and shape characters involved have been in fonts for decades, lenticular brackets, the diamonds and triangles in Geometric Shapes, the syllabics forms. The family that fails is anything built from combining marks. A strikethrough style is not a line drawn through text; it is U+0336, combining long stroke overlay, inserted after every letter, and underline is U+0332 doing the same job. Glitch styles stack marks from Combining Diacritical Marks (U+0300 to U+036F) several deep. Each mark is a code point of its own, so an eight-letter struck name is sixteen code points before anything else, and correct display depends on the renderer positioning each mark over its base glyph. Game renderers frequently do not, so marks land beside the letters, on the wrong ones, or nowhere. There is a coverage trap inside the clean families too. Mathematical italic has no small h: that letter is borrowed from Letterlike Symbols at U+210E, and script and fraktur have the same holes, so a name can fall back mid-word.
There is no way to preview the game's own rendering from a browser, so the test has to happen in the app, in the order that costs least. Start in the field itself. Paste the candidate into the rename box without confirming and watch the counter: if seven styled letters fill the cap, the field is counting code units and your budget is halved; if fourteen fit, it is counting something else. Note whether the filter rejects a character outright, because rejection at entry is the cheap failure and it names the symbol to drop. Then check the letters your name actually contains, not the alphabet in general. The gaps above are per letter, so a name containing an h, an e or a g in a script or italic style can fall back where a name without them looks perfect. After the change, look at your name on more than one surface. The lobby, friend list, team screen, killfeed and results screen use different widgets at different sizes, and a glyph that reads well large can smear at killfeed size. Screenshot it small. Finally, ask someone on another phone or platform to screenshot what they see. Their client decides whether your name reads as a name to everybody else.
A styled name has real costs, and they are worth naming before you spend a card on one. Nobody can type it. Friend search matches characters rather than appearances, so a teammate typing your name on a keyboard searches for plain letters and finds nothing, because your name contains none. Give people your numeric player ID instead, and expect to paste your own name rather than type it when you sign in on a new device. Tournaments and scrims are the sharper version of the same problem. Organisers match roster entries against in-game names exactly, registration forms often reject non-Latin input, and spreadsheets or overlay software drop characters they cannot render, which becomes an argument about whether the player is the person on the sheet. Accessibility is the cost people forget. Screen readers commonly announce mathematical letters one at a time by their formal character names, or skip them altogether, so a styled name read aloud through a stream overlay becomes noise rather than a word. Discovery cuts the same way: a styled name matches no plain-text search anywhere, so viewers hunting for you must copy the exact characters. If none of that matters to you, style it. If several do, decorate the clan banner and keep the name readable.
Styling itself is not the issue. Published naming policies target impersonation, offensive content and misleading names, not which Unicode block your letters come from. The realistic risk is a forced reset if a name breaks those rules, costing you the name and the item you spent on it. Read the policy for your region before building something borderline.
Emoji are a poor fit twice over. Most sit outside the Basic Multilingual Plane, the Emoticons block begins at U+1F600, so each costs two UTF-16 code units, like a mathematical letter. Name filters also reject them commonly, and game atlases rarely carry colour emoji, so an accepted one can still draw as a box.
They do. The mathematical block carries digits as well as letters, running through to monospace nine at U+1D7FF, so a styled numeral costs two code units just as a letter does. Fullwidth digits at U+FF10 to U+FF19 are the cheaper alternative at one unit each, with broader coverage in game fonts.
The field truncates, and truncation measured in code units can cut a surrogate pair in half. A lone surrogate is not a valid character, so it is dropped or swapped for U+FFFD, the replacement character. That is how a paste that looked right in your clipboard arrives with a question-mark diamond on the end.
They are separate fields with separate rules. The tag belongs to the clan, so editing it normally requires leader or officer permission and it changes for every member at once, making it a group decision rather than a personal one. Some builds also charge for a clan rename; check the clan management screen.
They are cheap in code units and widely supported, which is the good news. The catch is physical width: fullwidth forms occupy a full CJK em, so eight of them take roughly the space of sixteen ordinary letters. In a fixed-width lobby slot that means clipping or an ellipsis, even at a legal character count.
Often, and with more room, since chat fields are usually far longer than a name field, so the code-unit tax matters less. The atlas problem does not go away: the same client draws chat, so a character that boxes in your name boxes in your messages. Room names carry their own caps and filters.
It can. Some decorative styles carry joiners or variation selectors, U+200D and U+FE0F are the common ones, which occupy space in the field without drawing anything. An apparently short name can therefore hit the cap, or a filter can reject a string over a character you cannot see.