How long is one tick in Minecraft?

One tick lasts 0.05 seconds (50 milliseconds). There are 20 ticks in a second, so 100 ticks equal 5 seconds.

What is the difference between TPS and FPS?

FPS is how many frames your screen renders per second. TPS is how many game-logic loops the world completes per second. Minecraft targets 20 TPS regardless of your frame rate.

How do I check my TPS in Minecraft?

On Java Edition, press Alt + F3 to open the debug screen with graphs, which shows your current TPS. There is no equivalent display on Bedrock.

Does a higher random tick speed cause lag?

It can. More blocks update every tick, so crops grow faster but your world does more work. Raise it gradually and watch for drops below 20 TPS.

Minecraft Ticks Explained: Game Ticks, Redstone Ticks and Random Ticks

Home › Minecraft › Minecraft Ticks Explained: Game Ticks, Redstone Ticks and Random Ticks

Almost everything in Minecraft, from a wheat crop inching upwards to a creeper deciding to explode, is timed in ticks. Understand ticks and a lot of the game's stranger behaviour, including farm rates and lag, suddenly makes sense.

What Is a Tick?

Video games run in loops: check the world, move the mobs, update the blocks, repeat. One full loop is a tick, and the number per second is the tick rate, or TPS. It sounds like FPS, but they are different jobs. FPS counts the frames your screen draws; TPS counts the logic loops the game completes. Shooters chase 128 TPS, but sandbox games are happy lower, and Minecraft runs at a fixed 20 ticks per second in both single-player and multiplayer. That makes one tick 0.05 seconds, and a full in-game day 24,000 ticks, which is 20 real minutes.

Game Ticks

The game tick is the master clock. Mob spawning, mob movement, health and hunger, plant growth and fire spread all advance on it. Useful landmarks in the daily cycle:

Ticks	Time of Day
0	Sunrise (start of the day counter)
1000	Morning
6000	Noon
12000	Sunset
13000	Night, when monsters can spawn
18000	Midnight
24000	Next sunrise

When a world gets overloaded, the tick itself stretches: the game cannot finish a loop in 50 milliseconds, TPS drops below 20, and everything feels like slow motion. The usual culprits are huge redstone contraptions firing constant updates, hundreds of mobs crammed together, and hoppers or allays endlessly scanning for items. Culling mobs and switching off idle machines is the fastest cure. On Java you can watch your TPS live by pressing Alt + F3 to open the debug graph.

Redstone Ticks

A redstone tick equals two game ticks, or 0.1 seconds. Strictly it is a community term rather than an official mechanic, but most redstone components in Java delay their signals in steps of 0.1 seconds, so builders think in redstone ticks constantly. You cannot make them faster, only longer, which is exactly what a repeater's settings do.

Chunk Ticks and Random Ticks

Only chunks near players, or holding ticking entities, update each tick; on Java that is roughly a 128-block radius around you. Within those chunks the game also fires random ticks: each tick picks three random block positions per chunk section on Java (just one on Bedrock) and gives them a chance to change. That randomness is why crops grow at uneven speeds, grass and mycelium spread, fire burns out, leaves decay, copper oxidises, mud dries into clay and turtle eggs crack.

The number picked per tick is the random tick speed. You can change it with a gamerule command:

/gamerule randomTickSpeed 30

Raising it makes farms grow far faster, but push it too high and the extra block updates will drag your TPS down. A related idea is the scheduled tick: some blocks, like flowing water and repeaters, book their own future updates so their behaviour stays consistent instead of random.

So the next time a farm underperforms, do not rebuild it. Check whether you are standing close enough for its chunks to tick, and whether your world is actually holding its 20 TPS.