Almost every redstone build eventually needs a repeater, and almost every beginner places one without knowing what it actually does. It looks like a fancier piece of redstone dust with two little torches on it, so people treat it that way: something you drop in when a signal "runs out." That works, but it hides how useful the block really is.
The repeater does three separate jobs, and each one is worth learning on its own. It repeats a fading signal back to full strength, it delays a signal by a controllable amount of time, and it can lock to hold an output frozen. Once those three behaviors are clear, long redstone lines, timed contraptions, and memory circuits all stop feeling like magic.
This guide is pinned to Minecraft 26.2 Java Edition. Repeater behavior is stable and has been unchanged for years, so everything below applies directly. The repeater is one chapter of the complete redstone handbook, which links every other component together, and it pairs naturally with the redstone comparator, the block it is most often confused with.
Job one: repeating a fading signal
Every redstone signal carries a strength from 0 to 15. Redstone dust loses 1 strength per block it travels, so a signal from a lever reaches only 15 blocks before it dies. That limit is the first wall every redstone builder hits.
A repeater resets the signal. Whatever strength arrives at its back, the repeater outputs a fresh strength 15 from its front. Drop one in every 15 blocks and a redstone line can run as far as you want.
- The back of the repeater (the end where the two torches point toward you) is the input.
- The front (the end the arrow points to) is the output.
- A repeater is one-directional. A signal can only travel back to front. This is why the repeater is also called a diode.
The arrow printed on top of the repeater always points in the direction the signal flows. If you ever lose track of which way a repeater faces, look down at the top texture: the signal exits toward the arrowhead. This single detail solves most "my redstone line just stops here" problems.
Job two: delaying a signal
The two little redstone torches on top of the repeater are not decoration. The distance between them sets a delay, and you change it by right-clicking the repeater. Each right-click moves the front torch back one notch, cycling through four settings.
- 1 tick (default): the shortest delay, 0.1 seconds.
- 2 ticks: 0.2 seconds.
- 3 ticks: 0.3 seconds.
- 4 ticks: 0.4 seconds, then it wraps back to 1.
A redstone tick is 0.1 seconds (two game ticks). So a repeater on its maximum setting delays a signal by four tenths of a second. That sounds tiny, but chaining repeaters lets you build any delay you want: ten repeaters at 4 ticks give a full four seconds.
A repeater is a booster and a stopwatch in one block. Every other timed contraption in the game, from a piston door that closes on its own to a clock that ticks forever, is built out of repeater delays stacked end to end.
Delay is why redstone lines sometimes "arrive out of order." If two branches of a circuit need to fire at the same instant but one path is longer, add repeater delay to the short path until both sides line up. Timing bugs in doors and flying machines are almost always a delay mismatch, not a wiring mistake.
Job three: locking a repeater
This is the feature almost nobody discovers on their own, and it is what makes the repeater a genuine logic component rather than a wire.
If you power a repeater from the side with another repeater or a comparator, it locks. A locked repeater freezes its current output: if it was on, it stays on; if it was off, it stays off, and it ignores whatever happens at its back until the side signal is removed.
A tiny bar appears across the top of a locked repeater so you can see the state at a glance. This behavior turns two repeaters into a memory cell, the simplest way to store a single bit of information in redstone.
- Point one repeater at the side of another.
- Pulse the second (the locking) repeater, and the first freezes whatever it was outputting.
- Release the lock, and the first repeater resumes following its input.
That is the foundation of a latch. It is how item sorters remember their state, how hidden bases stay open or closed, and how counters hold a value. If you have read the item sorter guide, the comparators and repeaters holding each channel steady are doing exactly this.
Repeater versus comparator: the constant confusion
Both blocks have little torches, both are flat, and both are one-directional. They are also almost opposites in what they do to a signal.
| Behavior | Repeater | Comparator |
|---|---|---|
| Output strength | Always 15 | Passes or calculates a value (0-15) |
| Main purpose | Boost + delay | Measure + compare |
| Delay | 1 to 4 ticks, adjustable | Fixed, effectively instant |
| Reads containers | No | Yes |
| Can be locked | Yes | No |
The rule of thumb: reach for a repeater when you need a signal to travel further, arrive later, or hold steady. Reach for a comparator when you need to read a value, such as how full a chest is or whether one signal is stronger than another. The comparator guide covers that side in full.
Practical circuits every builder should know
A few small patterns show up constantly once you are comfortable with repeaters.
- Signal extender: one repeater every 15 blocks keeps a line alive across any distance.
- Diode / one-way gate: a single repeater stops backflow, so a signal cannot travel into a section you do not want powered. This prevents feedback loops in compact builds.
- Adjustable pulse timing: feed a button press through a chain of repeaters to delay when a piston fires. This is the heart of the timing in piston doors.
- Memory cell: two cross-locking repeaters store one bit, set and reset by short pulses.
A repeater cannot delay below 1 tick, and a 1-tick repeater can drop very short pulses entirely. If you feed a repeater a pulse shorter than its delay, the output may never fire. When you need sub-tick precision or pulse shortening, that is observer territory, covered in the observer and quasi-connectivity guide.
Putting it together
The repeater is the workhorse of redstone precisely because it does three jobs at once. It repeats so your signals reach across the base, it delays so events happen in the right order, and it locks so circuits can remember. Master those three and most intermediate redstone, doors, clocks, sorters, and farms, becomes a matter of arranging delays and latches rather than fighting mysterious behavior.
From here, the natural next step is timing: chaining repeater delays into a signal that fires on its own. That is exactly what a redstone clock does, and it is built entirely from the delay behavior you just learned. For the full map of how every component connects, keep the redstone handbook open in another tab.
Frequently asked questions
What is the difference between a redstone repeater and a comparator?
A repeater always outputs full strength 15 and can add delay or lock, so you use it to extend or delay a signal. A comparator measures and compares signals, reads container fullness, and never amplifies. Reach for a repeater to move a signal further or later, and a comparator to read a value.
How much delay does a redstone repeater add?
Each repeater adds 1 to 4 redstone ticks of delay, changed by right-clicking it. One redstone tick is 0.1 seconds, so a single repeater delays a signal by 0.1 to 0.4 seconds. Chain repeaters end to end for longer delays.
Why is my redstone repeater not working?
The most common cause is direction: a repeater only passes signal from back to front, the way its top arrow points. Make sure the arrow faces away from the input. Also check it is not locked, a bar across the top means a side signal has frozen it.
How do you lock a redstone repeater?
Power a repeater from the side with another repeater or a comparator, and it freezes its current output until the side signal is removed. Two cross-locking repeaters form a one-bit memory cell, the basis of most redstone latches.
