Observer
An observer watches the block directly in front of its face and emits a short pulse from its back whenever that block changes state. It detects updates that ordinary redstone cannot see.
What is an observer?
An observer is a block-update detector. It stares at the single block directly in front of its face (marked by the small dot) and, whenever that block changes — a lever flips, a plant grows, a piston extends, water flows in — it fires a brief redstone pulse out of its back (the arrow side).
This makes the observer the go-to component for reacting to events that don't produce a normal redstone signal, like crop growth or a block being placed.
How long is the observer pulse?
In Bedrock Edition an observer emits a pulse that lasts 1 redstone tick — 2 game ticks, or about 0.1 seconds — the same length as Java's observer pulse. (A common myth holds that the Bedrock pulse is shorter; it is not.) Where the editions really differ is the delay before the pulse fires: it is meant to be 2 game ticks, but on Bedrock a long-standing bug can stretch that to 4 or even 6 game ticks, so observer timing on Bedrock is a touch less predictable than on Java.
Observers as clocks
Point an observer at its own output (or at a second observer pointed back at it) and the two will trigger each other forever, producing a very fast, compact clock. Observer clocks are tiny and reliable but run quickly, so they're best for fast machines rather than slow timers.
Key facts
- Watches the block in front of its face; outputs a pulse from the back arrow on any change.
- Pulse lasts 1 redstone tick (2 game ticks, ~0.1s) — the same length as Java's; the “shorter Bedrock pulse” is a myth.
- Detects events redstone normally ignores: plant growth, block placement, fluid changes, piston motion.
- Two observers facing each other make a compact, fast clock.
- Reacts to changes only — a constant state produces no further output.
Bedrock vs. Java: timing quirks
The observer pulse is the same length (1 redstone tick) on both editions, so a Java build that fails on Bedrock usually isn't about pulse length — it's about Bedrock's less predictable observer delay (a known bug can stretch it from 2 to 4 or 6 game ticks) and the absence of quasi-connectivity in piston builds. If an observer-driven circuit misbehaves, feed the output through a repeater to clean up and re-time the signal, and wire each piston with real, direct power. This simulator models the standard 1-tick Bedrock pulse.