Every other crafting method in Minecraft asks you to stand at a table and click. The Crafter is different: it is a block that crafts, wired into redstone like a dispenser or a hopper. That single change, turning crafting into a component instead of a menu, is what made real auto-crafting possible in vanilla for the first time.
This guide covers how the Crafter actually works, the one trick that controls everything it does, and a complete working build you can place block for block.
The one trick: disabling slots
A Crafter has a 3x3 grid, same layout as a crafting table. Right-click, sneak-click, or click an empty slot and it toggles between enabled and disabled. A disabled slot is marked and simply refuses items: hoppers, droppers, and hand placement all fail to put anything into it.
That is the entire mechanism the Crafter gives you for controlling shaped recipes, and it is worth sitting with because it is not obvious at first. You are not telling the Crafter "craft a pickaxe." You are shaping the grid so that only pickaxe-shaped input can ever land in it, then feeding it materials and letting the recipe resolve itself.
You do not program a Crafter. You sculpt its grid until only one recipe fits, then let items find their own way into the shape you left open.
Disabled slots stay disabled even when the Crafter is empty and idle. They are a property of the block, not a temporary state that resets.
How items fill the grid
When a hopper or dropper feeds items into a Crafter, they do not go to a chosen slot. They go into the first available enabled, empty slot, checked in standard reading order: left to right, then top to bottom, row by row. Disabled slots are skipped entirely during that check, whether they are empty or not.
This is why slot layout, not item routing, is the whole design problem. If you want an item to land in the center slot only, you disable every other slot and there is nowhere else for it to go. If a recipe needs two different items in specific relative positions, like a bucket in the bottom-center and something above it, you feed one item type through one hopper aimed at the grid with all other slots disabled, then re-enable the remaining slot and feed the second item through a second hopper.
Plan the grid before you place a single hopper. Sketch which of the nine slots the recipe actually uses, disable the rest first, and only then start piping items in. Doing it in the other order means fighting misplaced items you have to dig back out.
Triggering and timing
A Crafter does nothing on its own. It needs a redstone signal, same as a dispenser or dropper. Once triggered, it waits 4 game ticks (0.2 seconds) and then crafts and ejects one item, matching dispenser and dropper timing exactly. That delay is fixed and is not something you can shorten with repeaters or comparators.
Each trigger consumes the ingredients currently sitting in the grid according to the recipe and produces one output. If the grid is not currently a valid recipe, or ingredients are missing, triggering the Crafter does nothing, no items are wasted, and it simply waits for the grid to become valid again.
Where the output goes
Crafted items eject out of the Crafter's front face (the face you can see is oriented by placement, same convention as a dispenser). If a container sits directly against that face, the item goes straight into it. If nothing is there, the item drops into the world as an entity.
One detail matters if you are filtering or sorting output: when a recipe produces a byproduct, an empty bottle from a potion recipe is the standard example, the crafted item is ejected first and the byproduct follows after it. If your output sorting depends on item order arriving at a hopper or an item sorter, account for the byproduct arriving second, not simultaneously.
Reading the grid with a comparator
Place a comparator against any face of a Crafter and it reads a signal strength equal to the number of slots that are either disabled or occupied. Nine total, whether by being switched off or by holding an item, and the comparator outputs strength 9.
This is the part that trips people up the first time they see it, because it is not simply "how full is the grid." A comparator reading a chest measures how much of its capacity holds items. A comparator reading a Crafter counts disabled slots as if they were already full. That is deliberate, and it is exactly what makes "fire when the recipe is ready" work reliably: a recipe that only uses three of nine slots would never reach a full-chest-style reading of 9 if disabled slots did not count, because six slots would sit permanently empty. Counting them as occupied means strength 9 always means "this specific recipe's inputs are satisfied," regardless of how many slots the recipe actually uses.
That single comparator reading, wired into a redstone signal back into the Crafter, is the standard way to detect a full crafter and fire it automatically.
A worked build: the simplest useful auto-crafter
This build turns a stream of one item type into a stream of the crafted result, fully automatically, using a recipe that fills one slot (a 1-to-1 recipe like a block from nine of the same item works as the model to extend from a multi-slot recipe).
- Input hopper feeding the Crafter. Place a hopper aimed into the Crafter's grid. Before you do, disable every grid slot except the ones the recipe actually needs, so the hopper cannot misplace items. For a shaped recipe, this is the step that does the real work.
- The Crafter itself, oriented so its front face points at your output container.
- A comparator reading the Crafter, placed against a side or back face, wired to output a redstone signal when it reads strength 9, meaning every needed slot is filled (and every unneeded slot is disabled, which is already contributing to that 9 before you place a single item).
- That comparator signal feeds back into the Crafter to trigger it. The moment the grid is satisfied, the Crafter fires, waits 4 ticks, and ejects.
- Output chest placed directly against the Crafter's front face, so crafted items land in it instead of dropping on the ground.
The reason each piece sits where it does: the hopper cannot overfill a correctly disabled grid, so you never need to babysit it. The comparator is the only clean way to know "the recipe is ready" without a timer, because timers fire whether or not the grid is actually full and waste ingredients or fire on nothing. And the output chest on the front face means you never have to walk over and pick items off the ground.
If your output chest fills up, items still eject from the Crafter's front face and just drop into the world once the chest can't accept them, since the Crafter doesn't check downstream capacity before firing. Keep an eye on the output chest or feed it into further storage if you expect high volume.
What to automate, and what not to bother with
Pros
- Bundling raw materials into storage blocks (iron, gold, copper, coal, redstone, diamond, and similar) is the clearest win: single-ingredient recipes, no slot-disabling complexity, and it collapses a shulker box worth of items into a fraction of the space
- Any recipe you craft often enough to notice the manual clicking, ladders, sticks, torches, glass, is worth setting up once and forgetting
- Recipes that feed directly into another automated system (blocks into an automatic smelter, or sorted output through an item sorter) pay for themselves because the whole chain runs unattended
Cons
- One-off recipes you craft twice a session are not worth building a grid layout and wiring for; the crafting table is still faster for anything you are not doing in bulk
- Recipes with several distinct ingredients in exact shaped positions take real setup time, multiple hoppers, multiple disable passes, and are only worth it if you need genuine volume
- Recipes with random or NBT-sensitive outputs are not good Crafter candidates since the block still follows fixed recipes; it does not add variety or randomness to what it produces
Feeding the build
A Crafter auto-crafter is only as good as its ingredient supply. A few farms on this site pair naturally with one:
- A bamboo farm supplies bamboo you can crush into blocks for compact fuel storage, which also feeds an automatic smelter running in parallel.
- A sugar cane farm is a straightforward source for a Crafter turning cane into sugar or paper in bulk.
- A minecraft item sorter downstream of a Crafter's output chest is how you keep crafted goods from piling up in one box once you are running more than one recipe through the same storage room.
Can a Crafter craft recipes that need a crafting table nearby, like the old 3x3 shapeless recipes?
No extra table is needed. The Crafter's grid functions as a complete crafting interface on its own, the same way a crafting table's grid does. If a recipe is craftable at a table, the same shape works in a Crafter's grid once the right slots are enabled.
Frequently asked questions
How do I disable a slot in the Crafter?
Click an empty slot in the Crafter's 3x3 grid to toggle it off. A disabled slot is marked and will no longer accept items from hoppers, droppers, or manual placement. Click it again while it is still empty to re-enable it.
How long does it take a Crafter to eject an item after being triggered?
4 game ticks, 0.2 seconds, after it receives a redstone signal. This matches the timing of a dispenser or dropper exactly.
Why does my comparator read 9 on a Crafter that only uses three grid slots?
Because a comparator reading a Crafter counts every slot that is either disabled or occupied, not just occupied slots. If you disabled the six slots your recipe does not need, those six already count toward the total before you place any items, so filling the remaining three brings the reading to 9. That is the intended behavior and the basis for "fire when full" detection.
Can I use a Crafter without any redstone signal at all?
No. Unlike a crafting table, a Crafter will not produce anything on its own. It requires a redstone signal to trigger each craft, the same way a dispenser needs a signal to fire.
Does the Crafter tell me how many items per hour it can produce?
Minecraft Wiki does not publish a throughput figure for the Crafter, and this guide is not going to invent one. What is documented is the per-activation delay: 4 game ticks (0.2 seconds) between a trigger and the item ejecting. Actual throughput in your build depends on how fast your redstone can retrigger it and how fast your hoppers can refill the grid, both of which vary by design.
What happens to the byproduct of a recipe, like an empty bottle, when the Crafter crafts?
It is ejected from the front face after the crafted item, not at the same time. If you are sorting output by arrival order into a hopper line, expect the main product first and any byproduct a moment later.
