Redstone Decoder

A redstone decoder is a vital computing circuit that reads a binary input combination and activates a single corresponding output line. You would use this in redstone computers, memory address selectors (such as dual-read RAM), or complex control panels where binary data needs to trigger specific actions. This guide covers three solid-state, pistonless designs by n00b_asaurus that solve common delay and spacing trade-offs.

Redstone ComputingAdvancedJava Edition
Redstone Decoder video tutorial

Video: Redstone Decoders - 3 Designs + Tutorials by n00b_asaurus

How to build it

  1. Design 1: Lay the Output Wire

    Start the low-profile stackable decoder by placing a straight line of solid blocks for your output wire and run redstone dust across the top. On every other block, place an extra block sticking out the back with a piece of redstone dust on it.

  2. Design 1: Build the Input Bridges

    Above the output line, construct the perpendicular input lines by going one block up, placing blocks in front and in back, and stepping one block down. Ensure the input line is not directly above the extra redstone dust you set back earlier, then run redstone dust along the top.

  3. Design 1: Program and Invert

    To program an input bit to respond to 0, place a repeater underneath the input line so it powers the output line. To program a bit for 1, place a redstone torch on the side of the input block so it powers the recessed redstone dust; add a torch inverter at the end of the output line to make the signal active-high.

  4. Design 2: Build the Staggered Output Line

    For the easier-to-program variant, place two blocks forward, step down one block, step up one block, step down one block again, and finish with two blocks across. Run redstone dust across this entire staggered output path.

  5. Design 2: Add Slab Input Lines

    Build the perpendicular input lines above by stepping up one block on the ends and placing a single block in the middle. Bridge the gaps between these raised blocks using upside-down half-slabs placed one block lower, then run redstone dust across the top.

  6. Design 2: Program with Torches or Repeaters

    Program each intersection directly underneath the input line: place a repeater if the bit should be active when the input is 0, or place a redstone torch in that exact spot if the bit should be active when the input is 1. Tile the slices up to 15 blocks long before inserting repeaters to refresh the signal.

  7. Design 3: Build the Upper Decoder Section

    To build the 'Lost Decoder' (which packs both inputs and outputs tightly), start by building the exact staggered output line and upside-down slab input bridges from Design 2.

  8. Design 3: Add the Lower Input Lines

    Directly beneath the middle block and end blocks of the upper section, go three blocks down, remove the temporary spacer blocks, and run two lower input lines with redstone dust across them.

  9. Design 3: Connect Lower Repeaters and Staggered Blocks

    Attach a block with a repeater to the lower lines, then stagger solid blocks one up and one over on both sides so their outputs feed up toward the middle output line.

  10. Design 3: Program Both Halves and Merge Inputs

    Program the top section using a repeater for 0 or a torch for 1; program the bottom section using two torches for 0 or one torch (plus an extra tick on its repeater to match delays) for 1. Finally, place repeaters at the start of all input lines and staircase the lower and upper input wires so they meet at the same level.

How it works

All three decoders use active-low NOR logic along a shared output line, followed by an inverter at the very end to make the final output active-high:

  • Active-Low Line: An output line is only allowed to turn off (triggering the final inverter to turn on) when every single input line crossing it matches its programmed state. If even one input does not match, it powers the output wire and keeps the final inverted output off.
  • Programming a 0 (Repeater): When a repeater is placed under an input line, an ON signal (1) from the input passes through the block and repeater into the output line, holding it ON (disabled). Only when the input is 0 does the repeater stay off.
  • Programming a 1 (Torch): When a redstone torch is attached to the input block, an OFF input (0) leaves the torch lit, which powers the output line and keeps it disabled. When the input turns ON (1), it turns the torch off, releasing the output line.
  • Dual-Layer Interleaving (Design 3): Because a single solid-state slice normally forces inputs to be spaced 3 blocks apart, the third design slips a second, bottom-fed decoder underneath a top-fed decoder. Both halves meet at the middle output layer, cutting horizontal input spacing down to compact 2-block centers while maintaining uniform delay.

Tips & variations

  • Equalizing Delays in Design 3: In the bottom section of the third design, a 0 bit uses two torches while a 1 bit uses one torch. Always add 1 extra tick of delay to the repeater on any 1-bit line so both states arrive at the output at the exact same time.
  • Signal Strength Limits: In Design 2, stacking two decoder modules end-to-end spans 15 blocks—the exact limit of redstone dust. Place repeaters between every two modules on the lower line and between decode lines on the top line to extend the decoder.
  • Solid-State Reliability: Unlike older piston-based decoders that can misfire in Java Edition due to quasi-connectivity updates, these torch-and-repeater designs are completely solid-state and silent.

Frequently asked questions

Why are all the outputs on except the selected one?
These decoders are naturally active-low, meaning the selected line turns off while all other lines stay powered. Place a redstone torch inverter at the end of each output line to make the selected output turn on (active-high).
Which of the three decoder designs should I build?
Build Design 1 if you need a low-profile decoder to stack vertically (such as for 4-wide memory cells). Build Design 2 for an easier programming layout with the same footprint. Build Design 3 if you have vertical room and need both your inputs and outputs packed as tightly together as possible with minimal delay.
Why not use a piston-based decoder instead?
Piston decoders used to be popular for speed and compactness, but quasi-connectivity in Java Edition makes tightly packed piston lines unreliable. Solid-state decoders using repeaters and torches are silent and completely reliable.

Components used

More decoder / encoder