Skip to content
ShapeCraft

Minecraft Sign Text Generator

Java & Bedrock

Write all four lines on the front and back of any Minecraft sign, colour each line (hex too), add bold, italic, underline, strikethrough or obfuscated text, switch on glow ink and wax, then copy a ready-made command for your exact version. The preview draws the sign in its wood colour with pixel text and cuts lines that are too wide, just like the game.

Sign

Text

10/90
Sign dye
263/90
Sign dye
358/90
#00AA00
40/90
Sign dye

The default text colour. Without glow ink the game shows it at 40 % brightness.

Preview · front

Command

Command (180 chars)
give @p minecraft:oak_sign[block_entity_data={id:"minecraft:sign",front_text:{messages:["",{text:"Welcome to",bold:true},{text:"Spawn Town",color:"dark_green"},""],color:"black"}}]
Only operators (cheats on) get the text when placing the item; for other players the sign is placed blank.

How it works

Type each line and use the toolbar to insert & colour and format codes, or set a colour and style for the whole line. Lines are parsed into styled text parts and measured with a pixel font: a sign line holds 90 px (about 15 letters), a hanging sign 60 px. Wider lines turn red in the editor because the game simply cuts them off.

The sign's dye colour is the default text colour. Without glow ink the game darkens it to 40 %, so dyed text looks muted; with glow ink the text shows at full brightness with an outline — the preview copies both looks.

Since 1.20 signs have two sides, each with its own 4 lines, dye and glow. The command writes front_text and back_text, plus is_waxed so players can't edit the sign.

Pick your version: 1.21.5+ writes the lines as SNBT text components, 1.20.5–1.21.4 puts JSON strings into the block_entity_data component, and 1.20–1.20.4 uses the old BlockEntityTag. Bedrock commands can't carry sign text, so you get the blank-sign command plus the exact § codes to type on each line.

Under the hood

1.21.5+ give
give @p oak_sign[block_entity_data={id:"minecraft:sign",front_text:{messages:["",{text:"Hi",bold:true},"",""],color:"black",has_glowing_text:1b},is_waxed:1b}]
1.20.5–1.21.4
messages:['""','{"text":"Hi","bold":true}','""','""']
1.20–1.20.4
give @p oak_sign{BlockEntityTag:{front_text:{messages:[…]}}}
Line width
sign 90 px · hanging sign 60 px · letter ≈ 5 px + 1 px gap, bold +1 px
Plain text colour
no glow: dye colour × 0.4 · glow ink: full colour + outline

FAQ

How do I write coloured text on a Minecraft sign?

In Java Edition you can't type colour codes on a sign by hand, so use a command: design the sign here and copy the /give command (or /setblock to place it). You can also dye a whole sign by right-clicking it with a dye. On Bedrock, type § followed by a code (for example §c for red) directly on the sign.

Why does my sign text get cut off?

Each sign line is 90 pixels wide (hanging signs 60). Most letters are 6 px including spacing, narrow ones like i or l less, and bold adds 1 px per letter — so about 15 normal letters fit. The editor shows each line's width and the preview cuts long lines exactly where the game would.

Which command format do I need for my version?

1.21.5 and later read sign lines as SNBT text components ({text:"Hi"}). 1.20.5 to 1.21.4 use the block_entity_data item component with JSON strings ('{"text":"Hi"}'). 1.20 to 1.20.4 use the old {BlockEntityTag:{…}} NBT. Choose your version above the command and it is rewritten for you.

What do glow ink and waxing do?

Glow ink makes sign text bright and readable in the dark, with an outline in a darker shade. Waxing (honeycomb) locks the sign so nobody can edit it — perfect for spawn and rules signs. Both are just flags in the command: has_glowing_text and is_waxed.

Why is my sign blank when another player places it?

Block data on items is only applied when a player with operator permissions places the item. For survival players, place the sign yourself with the /setblock command instead, or give it to an operator to place.

All tools →