How to Get Glitch Text in Minecraft?

Glitch text is the rapidly changing, scrambled lettering used for a mysterious message. Before trying it, decide where you want the result: a chat message, a sign, a book or a map introduction. Those are different destinations, so a working chat example is not automatically a recipe for a permanent sign. Start with the smallest test and build your design only after the effect appears where you expect.

This guide separates text formatting from game bugs. Missing characters, broken fonts and rendering problems can look strange, but they are not the effect you are trying to create. A message that displays squares needs a different diagnosis from a message that intentionally changes its characters. Keep a plain-text version of your intended message nearby so you can compare the two without guessing.

Choose the method for your Minecraft edition

Do not assume that another player’s screenshot came from the same setup as yours. It might show a server feature, resource pack or older release. When asking for help, include your edition, version and the place where you entered the text. That short description is more useful than saying only that the code does not work. Keep the exact error message too; it can show whether the problem is syntax, permissions or the selected input field.

How to get glitch text in Bedrock

Microsoft’s Bedrock documentation identifies §k as obfuscated text and §r as reset. For a command-based example, enter this on one line in a world where you have permission to use it:

/tellraw @s {"rawtext":[{"text":"§kSecret§r normal text"}]}

The intended effect applies to “Secret”; the reset code ends the formatting before the readable words. You can copy the section symbol § from this page. Input behavior varies by device and field, so use this rawtext example rather than assuming every chat, sign or book editor accepts the same entry.

How to get glitch text in Java

Java command text uses text components. Minecraft Java 1.21.5 changed command text-component input from JSON to SNBT. For that syntax family, a small example is:

/tellraw @s {text:'Secret',obfuscated:true}

For older versions that use JSON text-component input, the equivalent simple form is:

/tellraw @s {"text":"Secret","obfuscated":true}

These are chat-message examples, not commands for placing a sign or writing a book. Check the syntax supported by your exact release. We have checked documentation, but have not run these examples in your world or server.

Use a separate plain message when you want to explain what the effect means. You do not have to put every instruction in the same command. A short effect followed by a normal explanation is easier to maintain than a long message containing many styles. If your first test works, change the displayed word next. Add further styling one change at a time so you can identify which edit introduced a problem.

Why §k or &k may not work

A tutorial can be correct for one environment and unsuitable for another. Do not keep downloading tools because the first copied line failed. Write down what you entered and where you entered it, then compare that context with the tutorial. A server’s custom chat command may be unavailable in a single-player world; a command example may be unsuitable for an ordinary text box.

Some server instructions use an ampersand prefix such as &k. Treat that as a feature to check in the server’s own documentation, not a universal Minecraft command. Ask the server owner which formatting options players may use. Do not attempt to work around a restriction with a hacked client. You can still make an attractive message with readable wording and the formatting features the server permits.

1. Check the destination: ordinary chat, command input, sign and book are separate cases.
2. Check the version: match the example to the release you are running.
3. Check the copied punctuation: keep quotes, braces and brackets intact.
4. Check permissions: use your own test world or ask an administrator.
5. Reduce the example: return to one short word before adding decoration.

Signs, books and map introductions

A chat test proves only that your chat example worked in that environment. If your actual goal is a sign, prepare a separate test sign near your work area and preserve the original wording before editing it. For a book, keep a copy of the normal text outside the game. That makes it easier to correct spelling, restore a readable version and share the wording with someone helping you.

Put the mysterious effect on a clue’s optional decoration. Keep instructions, exits and important labels readable. A map visitor should not have to decode animated symbols to understand how to proceed. If you are designing a puzzle, give the player enough surrounding information to know whether the scrambled text is a deliberate clue or simply visual decoration.

Consider a simple pattern: a readable heading, one short mysterious phrase, and a clear next step. This gives the effect a purpose without making the whole page difficult to read. Show your draft to another player before placing it throughout a map. Ask what they believe they should do next. Their answer is a useful check on the message’s clarity, even if they like the visual effect.

Is glitch text a Minecraft bug?

Intentional obfuscated lettering is a formatting effect. It does not require crashing the game, changing a block’s identity or triggering an unrelated effect. The old idea that typing a special word makes you float or creates invisible walls is not a text-formatting method. If a tutorial connects those actions to scrambled letters without a verifiable explanation, do not use it as your starting point.

If readable text unexpectedly becomes missing glyphs or a broken display, describe that as a display problem when requesting help. Note whether it happens everywhere or only in one message. Record recent changes to packs or settings, but do not remove a collection of files at random. Keep the original configuration available so you can compare the problem before and after one controlled change.

Make the result easier to share

For a screenshot or short clip, keep the surrounding message brief. Show enough context for someone to understand the edition and where the effect appears. Avoid editing a still image so that it looks like proof of a command you never ran. A concept image can illustrate the topic, but it should not be presented as a test result.

Save the working command together with the edition and version you used. When sharing a tutorial, distinguish your tested result from a suggested variation. That makes your guide more useful than a dramatic caption alone. If another player reports failure, compare environments first rather than promising that the same steps work on every device.

Troubleshooting checklist

Before changing anything else, make a plain message work in the same context. Then try your smallest formatted example. If the plain message fails, focus on access or input first. If only the formatted message fails, compare its structure carefully. This approach keeps you from changing several unrelated things and losing track of the original issue.

Watch for copied typographic quotation marks, missing punctuation and accidental line breaks. If you typed the command manually, compare it character by character with the example. Use simple text while debugging; special characters can add another variable. Once the short version works, save it before experimenting with a longer message.

Frequently asked questions

What to do next

Choose the example for your edition, test a short message, and keep essential words readable. You can use a small mysterious phrase as decoration without making your whole build confusing. When you are ready for a new project, explore the related building guides below.

Existing walkthrough: Open the original linked video on YouTube. Its edition and version should be checked before following it.

Sources: Microsoft: Bedrock raw messages and formatting codes; Minecraft: Java 1.21.5 command text-component changes.