Transform gaming nicknames into vibrant colored strings with Free Fire [HEX] tags, Discord ```ansi blocks, and rich HTML colors.
Every other style on this site works by swapping one code point for another. Colour cannot work that way, because there is no coloured letter to swap to. Unicode encodes plain text, and the standard is explicit that a character code carries no font, size, weight or colour; presentation belongs to what it calls a higher-level protocol, markup, an escape convention, or the renderer's settings. No code point anywhere means a red A.
The apparent exception proves the rule. Emoji look coloured because a font ships multicolour glyph tables, and because U+FE0F, variation selector-16, requests the emoji presentation of a character that would otherwise draw as monochrome. The colour lives in the font file, never in the character.
Every coloured name you have seen in a game lobby, a Discord announcement or a document came from something wrapped around the letters: a marker a chat parser recognises, an escape sequence a terminal renderer understands, or HTML an editor turns into formatting. The wrapper only works if the destination understands it, and when it does not, the instructions show up beside your name as literal characters. Three conventions cover nearly every destination worth aiming at, and this page writes all three.
The convention game chat parsers use is the plainest of the three: a marker, a six-digit hexadecimal triplet, then the text it applies to. This studio writes it as [FF1E56]ShadowNinja. The parser reads the bracketed value as a colour, removes it from what it draws, and paints what follows in that colour until the next marker or the end of the string.
Minecraft uses the same idea with U+00A7, the section sign, followed by one character: c for red, 6 for gold, l for bold, r to reset. That is sixteen palette slots rather than sixteen million colours, so a section-sign name cannot express an arbitrary brand hex; Java Edition's full colour support lives in JSON text components, not in a string you type into chat.
Two consequences follow. First, a tag is made of characters, so it occupies room: one bracketed triplet is exactly eight characters of overhead before a single letter of your name. Second, acceptance differs field by field inside one game. Free Fire reads colour codes in the bio and the guild description, while whether the nickname field honours or strips them has moved between builds. Try it somewhere you can edit for free before spending a rename card.
The second convention predates the games that borrowed it. ECMA-48, the control-function standard also issued as ISO/IEC 6429 and, in the United States, as ANSI X3.64, defines how a character-cell terminal is told to change its output; the relevant control is Select Graphic Rendition, or SGR.
An SGR sequence opens with the escape character, U+001B, then a bracket, then semicolon-separated parameters, then the letter m. ESC[31;1m sets foreground colour 31 with the bold attribute; ESC[0m resets. The basic palette is eight foreground values, 30 through 37, and eight backgrounds, 40 through 47, with bright variants at 90 through 97 that are a widespread extension rather than part of the original standard. Two later forms give more: ESC[38;5;n picks one of 256 indexed colours, and ESC[38;2;r;g;b sets a direct 24-bit colour in the form ISO 8613-6 describes.
Discord is the one mainstream chat client that renders any of this, and only inside a fenced code block tagged ansi. Its renderer covers the basic set (the 30s and 40s, plus bold and underline) and ignores the indexed and truecolour forms. That is why the Discord copy here paints a whole block one colour instead of the ramp you picked: a gradient there is something the client will not draw.
The third convention is the one document editors speak, and it leaves no code in your text. Choosing the colour format puts two flavours of the same content on the clipboard at once: a text/html flavour in which each character sits in a span carrying its own hex value, and a plain-text flavour with no colour at all. Google Docs, Word, Gmail, Outlook and Canva read the first and give you real, editable coloured text. A field that only understands plain text reads the second and gets clean characters instead.
That path also settles a glyph problem. Web faces such as Georgia, Courier New and Brush Script contain no letters from the Mathematical Alphanumeric Symbols block, so a substituted blackletter name pasted into a document renders as boxes. For those families the clipboard HTML carries your original letters plus a real font-family, which is why a script style arrives in Word looking like script rather than tofu.
One warning about the preview above. The gradient running through the letters is CSS background-clip, a continuous ramp painted through the shape of the text, and none of that CSS travels with a copy. What lands in the clipboard is stepped instead: one flat colour per character.
The commonest failure is not a bad colour choice. It is a destination that does not speak the convention and therefore prints the instructions.
Paste a bracketed hex tag into an Instagram bio and it reads [FF1E56]ShadowNinja, brackets included, because Instagram has no chat parser and the tag is just eight more characters. Paste an ANSI string outside a Discord code block and something stranger happens: U+001B has no visible glyph, so it renders as nothing or as a hairline box, and your reader sees [31;1mShadowNinja. The byte that made the rest a control sequence is the one that vanishes. Many platforms also strip control characters on input, so once the message is sent the escape is gone and the readable remainder is welded into your text.
The HTML format degrades more kindly, because the plain-text flavour travels beside it: a field that cannot read markup takes the clean characters rather than showing tags.
The habit that prevents all of this takes two seconds. Paste somewhere disposable first (a direct message to yourself, a test channel, a bio you can edit again) and look at the result before you paste into anything that costs a rename card or gets read by thousands.
A gradient is not one instruction. No convention here can say fade from crimson to gold across this word; colour applies from a marker until the next one, so a gradient means one instruction per character. This page computes them by interpolating between the preset's stops in RGB: position becomes a ratio, the ratio selects a segment of the ramp, and the two stops either side blend channel by channel.
The cost is arithmetic. At eight characters per tag, a twelve-character name leaves as roughly 108 characters of raw string. In ANSI truecolour, where a single sequence such as ESC[38;2;255;30;86m runs seventeen characters, the same name passes 200.
That collides with name fields, which are short on purpose: a Minecraft Java username is 3 to 16 characters, an Xbox gamertag 12, a Discord nickname 32. None will hold a per-character ramp, so gradients belong in bios, guild descriptions, captions and documents, while a single tag is the realistic choice for a name.
Substituted letters compound it. Characters from U+1D400 to U+1D7FF sit outside the Basic Multilingual Plane and cost two UTF-16 code units each, so a field counting code units takes about half the name you expect before any colour is added.
Colours that look superb against this page's dark panels can be unreadable where you paste them. The WCAG contrast minimum, success criterion 1.4.3, asks for 4.5:1 between text and its background, easing to 3:1 for large text at 18pt or 14pt bold. Game huds and chat panels are less forgiving than a design canvas.
With the sixteen-colour ANSI form you are not choosing a colour at all; you are choosing a palette slot, and the client or terminal decides what pixels that slot produces. Colour 30 is nominally black, which on a dark code-block background is close to invisible. The stealth grey preset here has that problem in Discord, which is better to learn before it goes into a pinned post.
Hex tags give you the actual colour, which moves the difficulty to a background you do not control. A killfeed sits over whatever the map is showing that second: a pure yellow that reads cleanly at night disappears against snow. Mid-tone saturated colours (a strong cyan, a warm orange) survive more backgrounds than either extreme.
Underneath it sits WCAG 1.4.1: colour must never be the only carrier of meaning. If your tag says something, say it in the characters too.
Colour and substituted characters both make text harder for machines to handle, and it is worth naming where that hurts.
Assistive technology gets nothing from it. Screen readers do not announce colour by default, so all three conventions are invisible to a listener at best; at worst the bracketed tags or leftover escape fragments are read aloud or skipped mid-word, and names built from the mathematical letters are commonly announced character-name by character-name, or dropped. Someone using a screen reader cannot read your name back to you.
Search stops matching. A moderator looking up your clan tag, a teammate scrolling for your message and a support agent finding your ticket all type ordinary letters, and ordinary letters match neither a colour tag nor a substituted glyph. Keep one plain copy of your name somewhere you can send.
Identifier fields reject it outright. Usernames, logins and account IDs restrict their character set (Minecraft Java allows only letters, digits and underscores) so anything from this page belongs in a display name, never in the credential. And because some platforms strip the C0 control opening an escape sequence while keeping everything after it, an ANSI name pasted into the wrong box cannot be repaired, only deleted and retyped.
No. ANSI escapes are honoured only inside a code block, and nickname fields render plain. Colour on a Discord name comes from a role a server admin assigns, and the highest-positioned coloured role wins. What a nickname will carry is substituted unicode characters, within its 32-character limit.
Because the blend runs straight through RGB. Two stops on opposite sides of the colour wheel meet at a low-saturation midpoint, so crimson to cyan passes through mud while crimson to gold stays vivid. Pick stops that sit near each other in hue, or a preset with a bright middle stop.
Assume yes. Most fields validate the raw string before any parser strips the tags, so an eight-character tag eats eight of your allowance. Measure the copied string, not the preview: the preview shows letters only, while the clipboard holds every marker too. Silent truncation removes the tail first.
Not as message markup. Twitch colours your username through an account setting rather than anything you type, and YouTube live chat renders plain text. Both show a bracketed hex tag as literal brackets. Styled unicode characters do pass through, so any name effect there comes from characters, not colour.
The character is U+00A7, and many clients block it in chat input, which is why server plugins conventionally accept an ampersand in its place and translate it before display. Command blocks and written books usually take the real sign. Plenty of servers disable colour codes in player names deliberately.
Colour itself is rarely against the rules, but two things get enforced: names impersonating staff by mimicking a reserved colour, and names moderators cannot type when filing a report. Some competitive servers ban colour codes in tags for that second reason. Check the rules before a tournament, not after.
Yes, through the rich format. Gmail and Outlook signature editors accept pasted HTML, so per-character colour survives as it does in a document. Recipients reading in plain-text mode see the letters without colour, which is the right fallback. Keep it short: per-character spans make a heavy signature.
No. There is no sign-up, no paid tier and no upload. Every transformation, gradient and copy format here runs in your browser, on your device, from text you type. Nothing leaves the page, so you can build a name for a private server without anything being recorded.