Color Codes
| Name | Hex Code | Code | MOTD |
|---|---|---|---|
| dark_red | #BE0000 | §4 | \u00A74 |
| red | #FE3F3F | §c | \u00A7c |
| gold | #D9A334 | §6 | \u00A76 |
| yellow | #FEFE3F | §e | \u00A7e |
| dark_green | #00BE00 | §2 | \u00A72 |
| green | #3FFE3F | §a | \u00A7a |
| aqua | #3FFFEF | §b | \u00A7b |
| dark_aqua | #00BEBE | §3 | \u00A73 |
| dark_blue | #0000BE | §1 | \u00A71 |
| blue | #3F3FFE | §9 | \u00A79 |
| light_purple | #FE3FFE | §d | \u00A7d |
| purple | #BE00BE | §5 | \u00A75 |
| white | #FFFFFF | §f | \u00A7f |
| gray | #AAAAAA | §7 | \u00A77 |
| dark_gray | #3F3F3F | §8 | \u00A78 |
| black | #000000 | §0 | \u00A70 |
| Reset | §r | \u00A7r | |
| Bold | §l | \u00A7l | |
| Italic | §o | \u00A7o | |
| Underline | §n | \u00A7n | |
| Strike | §m | \u00A7m | |
| Obfuscate | §k | \u00A7k |
Choose the right Minecraft color code for your text
A clear rank prefix, a readable server description or a highlighted instruction all need the right text format. This table puts Minecraft color names, HEX values, legacy codes and MOTD escapes beside one another. Click a non-empty cell to copy its value rather than retyping an unfamiliar symbol or confusing a display color with a formatting instruction.
Before copying, decide where the text will appear. A plugin configuration, a Java server file and a Bedrock text component may expect different representations. The same visible color does not imply that the same syntax works everywhere. This distinction prevents a common problem: players seeing the literal code instead of the intended colored message.
How to use the color code table
- Identify your destination. Check whether the field expects legacy codes, Unicode escapes, plugin ampersand codes or modern text components.
- Choose a color. Use the name and preview to find the desired entry. HEX describes an RGB value; the code column gives a Minecraft formatting sequence.
- Copy the appropriate cell. Click a non-empty value. The MOTD column contains an escaped representation of the section sign.
- Place the code before the text. Add any supported style codes and reset the formatting when the highlighted section ends.
- Test it in context. Check the result in the actual client. For a complete server description, use the MOTD generator to preview your draft.
Section signs, Unicode escapes and plugin codes
What a legacy code actually does
A legacy code starts with § followed by a code character. For example, §a selects green and §c selects red. In a field that interprets these codes, the sequence controls the text that follows rather than appearing as visible characters. A later formatting instruction can change that state again.
The sequence \u00A7 is a Unicode escape representing the section sign. In a compatible Java properties file, \u00A7a can therefore describe the same green color change. In an ordinary text input, the escape may simply remain visible. The destination must actually decode it.
Many server plugins accept &a as a more convenient alternative and translate it internally. This is a plugin feature, not a universal Vanilla chat rule. Typing an ampersand into Java chat or a sign does not by itself enable colors. Direct section signs are also restricted in some inputs. Check both the plugin’s syntax and the permissions granted to the player.
HEX values describe colors, not universal commands
An RGB value such as #55FF55 contains two hexadecimal digits for each channel: red, green and blue. Each channel ranges from 00 to FF, equivalent to 0 through 255. Together they describe 256³ = 16,777,216 possible colors. Traditional Minecraft color codes use a much smaller fixed palette.
A HEX value is useful for websites and text systems supporting RGB, but pasting it into a chat field does not automatically color the following text. Modern components and plugins require their own syntax. Resource packs, text shadows and display settings can also make an in-game color look different from the table’s browser swatch.
Combine formatting without losing readability
Useful legacy styles include §l for bold, §o for italic and §r for reset. Java also supports legacy underline and strikethrough styles. Some code meanings differ in Bedrock, so do not assume that every Java styling example transfers unchanged.
In Java legacy text, changing color can clear existing styles. For green bold text, place the color before bold: §a§lWelcome§r. Keep obfuscated text away from instructions and server names, since changing characters make those harder to read. A short prefix and one accent color are often enough for a rank. Include words such as “Info” or “Warning” so the message remains understandable even when its color is difficult to distinguish.
Frequently asked questions
Why does &a not work in my chat?
Ampersand codes require a plugin or another system that translates them. Vanilla Java chat does not generally perform that conversion, and plugins may require permissions.
What is the difference between §a and \u00A7a?
They can represent the same color change, but the Unicode escape must be interpreted by the file format or application. An ordinary input field may display it literally.
How do I reset text formatting?
Use §r in a supported legacy text field, or the reset syntax required by your plugin. Following text then uses the default formatting.
Are Java and Bedrock formatting codes identical?
No. They share several color codes, but some codes have different meanings or additional uses in Bedrock. Check the edition before copying styles.