Hopper Throughput: the 9,000-an-Hour Ceiling

Verified: Java 26.3 / Bedrock 26.50 · 2026-09-16 · rate identical in both editions · Updated 2026-09-16

Every item system in the game — storage halls, furnace arrays, farm collection — eventually runs into one number: a hopper moves an item every 8 game ticks. This guide is what that number actually costs you, when it matters, and the two honest ways around it. The hopper rate calculator runs the arithmetic.

The rate, stated plainly

After a hopper pushes or pulls, it waits 8 game ticks — 0.4 seconds — before acting again. That is 2.5 items per second, 150 per minute, 9,000 per hour, and those figures never change with the hopper's contents, orientation, or age. It is worth saying once, clearly: the 8,000-an-hour number that circulates in older forum posts is wrong. The cooldown is 8 ticks, a second is 20 ticks, and 2.5 × 3,600 is 9,000 — the wiki states the per-hour figure directly, and independent redstone documentation agrees.

What the ceiling means in practice

Run the sizes you actually haul through the number. A shulker box or single chest of 64-stack items is 1,728 items: 691.2 seconds, or 11 minutes 31.2 seconds, through one hopper. A double chest is 3,456 items and takes 1,382.4 seconds — 23 minutes and 2.4 seconds. A double chest of ender pearls (the 16-stack class, 864 items) is a much friendlier 5 minutes 45.6 seconds, and 54 unstackable items pass in 21.6 seconds. The pattern to internalize: hopper time scales with items, not slots — which is why the 64-stack loads dominate every waiting-around story you have heard.

Left alone for a day, one hopper moves 216,000 items. That sounds enormous until you price a serious farm: a million-item project is 111.1 hopper-hours through a single line.

Chains add distance, lines add speed

The most common design mistake is lengthening a hopper chain and expecting throughput. A chain is a pipe: every hopper in it obeys its own 8-tick clock, so items flow through a 30-hopper line no faster than through a 3-hopper line — the extra hoppers add travel distance and iron cost, nothing else. Throughput multiplies only when lines run in parallel, each with its own source and destination. Two independent lines carry 5 items a second; four cut the double-chest drain from 23 minutes to 5 minutes 45.6 seconds. The calculator's parallel-lines field models exactly this, splitting the load with the busiest line deciding the finish.

Whether the iron is worth it is a farm-rate question. A farm producing under 9,000 items an hour cannot saturate one hopper, and parallel collection there buys nothing but tidiness. Past 9,000 an hour, every line is mandatory plumbing: items that cannot leave the collection point float, and floating items despawn in five minutes.

The two documented quirks

The calculator models the flat 8-tick rate and says so, because the two exceptions both work in your favor. First, in Java only, the initial push into an empty hopper runs on a 7-tick cooldown rather than 8 — a one-tick head start that matters to instrumented contraptions and to nobody's storage room. Second, when a stack of items sits in a vertical hopper pipe, the holding hopper pushes down while the hopper below simultaneously pulls down, and the stack can descend at double speed. Real systems therefore run slightly ahead of the calculator's clock, never behind it — the number you get is a floor you can plan on.

Feeding machines instead of chests

Throughput framing flips when the destination does work. A furnace consumes one item per 10 seconds — 360 an hour — so a single hopper at 9,000 an hour can keep 25 furnaces saturated if the plumbing distributes evenly. That is why big smelter arrays are hopper-cheap: the bottleneck is the furnaces, and the smelting calculator prices that side of the system. Storage sorters sit at the other extreme: every item passes single-file through the sorting line, so the line's 2.5 per second is the hall's intake ceiling no matter how elegant the back end.

Limits

All figures assume a loaded, lag-free area — the wiki's own numbers carry the same caveat, since a struggling server stretches every tick. Water streams, droppers on clocks, and minecart-with-hopper systems move items on entirely different budgets and are out of this tool's scope. Sources: the Minecraft Wiki's hopper documentation and independent redstone references confirming the 2.5-a-second rate; re-verified 2026-09-01, and every number in this guide is asserted in our test suite.