Somebody’s name looks like ꧁༒☬ᴅᴀʀᴋ☬༒꧂ and yours does not. Retyping it never works, because almost nothing in that string is on your keyboard — and some of the characters have nothing to draw at all. Decoding a nickname means splitting it back into the individual Unicode characters it is built from: paste it into the box above and every character comes back separately, with the real codepoint behind it. That is what lets you rebuild the name with your own letters, and it is also how you find out why a Free Fire or PUBG Mobile name field rejected a name that looked short enough to fit.
Why retyping a copied name never works
A decorated nickname is not a font and not an effect. It is a sequence of ordinary Unicode characters that happen to look ornamental — the same kind of thing as a letter or a comma, just from parts of the standard your keyboard never offers. When you look at ᴅᴀʀᴋ you are not looking at “dark in a style”. You are looking at five separate characters that were designed as phonetic symbols and happen to resemble small capitals.
That is why typing dark and hoping gets you nowhere, and why a screenshot is useless: you cannot copy a picture of a character. The only reliable move is to take the original string apart and find out which characters are actually in it. That is the whole job of the tool at the top of this page.
What the breakdown tells you
Each card in the result is one character. It shows three things:
- The glyph itself, exactly as it appears in the original — tap the card to copy that single character.
- The codepoint, written
U+followed by hex. This is the character’s permanent address in Unicode. ꧁ is always U+A9C1, on every device, forever. Two characters that look almost identical will have different addresses, and that difference is usually what decides whether a game accepts your name. - The name, where we have one on file. These come from the same hand-checked table that powers the symbol lists on this site, so a card either shows a real Unicode name or says plainly that the character is not in our table. We would rather tell you we do not know than invent a name for a glyph.
Above the cards is a count, and the count is the part most people came for: how many characters the string really contains, how many of those are actually visible, and how many we could name.
The four things hiding in a decorated name
Once you have run a few names through, the same four categories keep turning up.
1. Letters that are not letters
ᴅᴀʀᴋ, 𝔡𝔞𝔯𝔨 and 𝕕𝕒𝕣𝕜 all read as “dark”, and none of them contain the letter D. They are drawn from blocks Unicode built for other purposes — phonetics, mathematical notation — that happen to have letter-shaped members. A game that filters names to “letters and digits only” is checking the character’s category, not its shape, so these frequently fail a filter that plain dark would pass.
2. Standalone decorative symbols
The brackets and marks that frame the name are ordinary standalone characters. ꧁ and ꧂ are Javanese Left and Right Rerenggan; ༒ is the Tibetan Mark Rgya Gram Shad; ☬ is Adi Shakti. Each is one character and costs one slot. We wrote about where these marks actually come from and what they mean in their own scripts, because the answer is more interesting than “gamer symbols” — and if you just want to grab a matching pair, the full set of bracket and frame characters is laid out with codepoints.
3. Combining marks that ride on the character before them
This is the category that surprises people. Some characters are not meant to stand alone — they attach to whichever character precedes them. The familiar ×͜× face is exactly this: two multiplication signs with a combining mark tucked between them that draws the curve joining them. On its own the mark is invisible; only in company does it appear.
The consequence matters. A combining mark is a full character as far as a length counter is concerned, even though it adds no width of its own. A name that looks six characters wide can easily be nine characters long, which is how a nickname gets rejected by a field it visibly fits inside.
4. Characters with nothing to draw
The last group is invisible. Zero-width joiners, variation selectors and blank fillers occupy a slot and render nothing. They are in decorated names for real reasons — a variation selector forces a symbol to render in its flat text form rather than as a colour emoji, and a filler is how people fake a blank space in fields that strip ordinary spaces. In the breakdown these appear as a card marked □ with its codepoint, so you can see there is something there even though your eye says the string is empty at that spot.
A worked example
Take ꧁༒☬ᴅᴀʀᴋ☬༒꧂. Your eye reports something like “brackets, some marks, the word dark, the same marks mirrored”. The breakdown reports ten characters:
| Position | Glyph | Codepoint | What it is |
|---|---|---|---|
| 1 | ꧁ | U+A9C1 | Javanese Left Rerenggan |
| 2 | ༒ | U+0F12 | Tibetan Mark Rgya Gram Shad |
| 3 | ☬ | U+262C | Adi Shakti |
| 4–7 | ᴅᴀʀᴋ | U+1D05, U+1D00, U+0280, U+1D0B | Four phonetic small capitals |
| 8 | ☬ | U+262C | Adi Shakti |
| 9 | ༒ | U+0F12 | Tibetan Mark Rgya Gram Shad |
| 10 | ꧂ | U+A9C2 | Javanese Right Rerenggan |
Ten characters, all visible, none combining. That is a well-behaved decorated name: it will survive a copy-paste into any field that accepts these blocks, and it costs exactly ten of whatever limit you are working against. Names that misbehave are the ones carrying invisible passengers in category three and four — and now you can see them before you paste.
Why the character count never matches what you see
The single most common complaint about decorated names is a field rejecting a name that “obviously fits”. The breakdown explains it every time. A twelve-character limit counts characters, not width. A frame of ꧁ ༒ ☬ on each side is six characters before a single letter of your actual name, which leaves six for the name itself. Add a combining mark or a joiner you cannot see and you are over the line while the preview still looks short.
We keep the actual limits for each game and platform field in one place, because the numbers differ more than people expect and the counting rule differs too. If your name is being rejected outright rather than truncated, the cause is usually a filter rather than a length problem — the guide to boxes, blanks and rejected characters covers what to check.
What to do once you know what is inside
The breakdown is a starting point, not an end. Three things people usually do next:
- Rebuild it with your own name. Copy the frame characters individually from the cards, then put your letters between them. You now have the exact ornament without needing the original string.
- Strip what is breaking it. If the count shows invisible characters and a field keeps rejecting the name, remove those and try again. Often the visible part was never the problem.
- Swap one piece. Keep the structure, change the marks. If you like the shape but want stars instead of Tibetan marks, take the frame apart and substitute — the symbol collection and combiner on our home page has each family grouped so you can find an equivalent that occupies the same visual slot.
For a name headed into a specific game, it is worth checking what that game accepts before you commit: our notes on symbols that survive a Free Fire nickname field and on what PUBG and BGMI allow both list the characters that reliably work.
The replacement parts, ready to copy
Once the breakdown has told you which characters a name is built from, the next step is usually to swap one out. These are the families the decoded characters almost always come from — the same hand-checked tables used across this site, with the codepoint printed under every glyph. Tap any card to copy that single character.
Frames and brackets — the outer shell
These are what ꧁ and ꧂ belong to. Swap the pair and the whole name changes character while the length stays identical.
Tibetan and Javanese marks — the inner ornament
༒ and ☬ sit in this group. They are the marks most often stacked just inside the brackets.
Stars, hearts and crowns — the accent slot
One accent on each side is the most common decoration after the frame, and the cheapest in characters.
Wings, arrows and sparkle — the wider set
Questions people ask
Does the tool send my name anywhere?
No. The breakdown happens entirely in your browser. Nothing you paste is transmitted, logged or stored — close the tab and it is gone.
Why does one card show a box instead of a character?
Two different reasons, and it is worth knowing which. A card showing □ with its codepoint is deliberate: that character is genuinely invisible and we draw a placeholder so you can see it exists. A box appearing in the original name, elsewhere on the page, means your device has no font covering that character — a display gap on your end, not a broken character.
Some characters have no name. Why?
Our name table covers the characters that actually turn up in decorated nicknames — currently a few hundred, each checked by hand. Unicode contains well over a hundred thousand characters, so anything outside that set is reported by codepoint and category instead. The codepoint is the authoritative part; you can look it up anywhere and always get the same character.
Can I decode an emoji sequence?
Yes, and it is instructive. A single family emoji is commonly several people-emoji joined by zero-width joiners — paste one in and you will see the joiners appear as their own cards between the visible parts. This is also why one emoji can cost five or six slots against a character limit.
Will a decoded name work everywhere?
No, and no name will. Every platform makes its own decision about which Unicode ranges it accepts in a display name, and those decisions change. Knowing exactly which characters are in your name is what lets you work out why a particular field refused it, instead of guessing.
