Tools Gaming & Minecraft

Minecraft Armor Dye

Convert RGB or hex into dyed leather armor /give commands using dyed_color components or legacy display.color integers.

Minecraft Armor Dye

Legacy color int is (r<<16)|(g<<8)|b. Modern uses minecraft:dyed_color.

Minecraft Armor Dye converts hex or RGB values into leather armor /give commands. Pick a helmet, chestplate, leggings, or boots piece, preview the swatch, then export modern dyed_color components or legacy display.color integers for Java Edition kits and cosmetics.

What Minecraft Armor Dye does

Builds dyed leather armor give commands.

  • Hex and synchronized RGB inputs
  • Armor piece selector
  • Modern dyed_color and legacy display.color
  • Color int readout (r<<16)|(g<<8)|b
  • Copy command

Who Minecraft Armor Dye is for

  • Cosmetics creators matching brand colors
  • Server kits with team leather sets
  • Map makers tinting NPC gear
  • Players recreating skins in item form

How to use Minecraft Armor Dye

1. Open Minecraft Armor Dye on beeforge.dev.
2. Choose modern or legacy syntax and an armor piece.
3. Enter hex or adjust RGB sliders/fields.
4. Confirm the swatch and integer value.
5. Copy the /give command.

Features

  • Bidirectional hex and RGB sync
  • Live swatch preview
  • Related banner and firework dye tools
  • Client-side only

Examples

  • Team blue chestplate from #3C44AA.
  • Full set matching a guild hex.
  • Legacy export for older permission plugins.

Tips and limits

  • Only leather armor accepts dye color this way.
  • Some servers strip display NBT; test first.
  • Color int is unsigned 24-bit RGB packed.
  • No upload of color choices.

Related tools

FAQ

How is the color integer calculated?

It packs channels as (r<<16)|(g<<8)|b, the standard Minecraft leather color int.

Modern vs legacy?

Modern uses the dyed_color item component. Legacy uses display.color inside NBT.

Is my color uploaded?

No. Conversion runs locally in the browser.

Extra notes

This BeeForge tool runs entirely in your browser so drafts, commands, and preview text never need to leave your device for processing. Keep a backup of long outputs in your own notes if you rely on them for production servers or live events. Syntax can change between game or client versions, so verify commands and JSON in a creative world or staging pack before shipping to players. If a paste fails in chat, use a command block, function file, or datapack entry instead of relying on the 256 character chat limit. Accessibility friendly labels come from the module UI strings, and the layout follows the shared BeeForge .bf-tool shell for consistent spacing and buttons.

Support for educators, content creators, and server staff is the same client-side model: open the page, configure options, copy or download, then paste into your workflow. BeeForge related links at the bottom of the tool page point to companion generators so you can move between related gaming utilities without hunting the hub.