Guides / Enchanting Strategy / Enchanting Strategy: How the Anvil Actually Works
Enchanting Strategy: How the Anvil Actually Works
Published September 12, 2026
Every enchanted item you've ever seen on a good survival world went through the same machine: an enchanting table for the first roll, then an anvil for everything after. AnvilCalc exists because that second step has a hidden cost curve that punishes the wrong order — and once you understand why, you can build anything without ever hitting Too Expensive!
The prior-work penalty is the whole game
Every time an item or book goes through an anvil, its internal "anvil use count" goes up by one. The level cost of its next combine is then multiplied using the formula 2^c − 1, where c is that count: 0, 1, 3, 7, 15, 31 levels of pure penalty, stacking on top of whatever the enchantments themselves cost. This is why combining four separate books one at a time onto your sword gets exponentially more expensive with each step. A small side merge of two books (two fresh books give a result at prior work 1) can keep both sides' penalties lower for longer, but merging every book into one big "master book" first does not: the book itself piles up prior work and the last step pays for all of it (see The Master Book Myth).
Penalty in XP levels added on top of enchantment cost, by how many times that item or book has already been through an anvil.
When two items merge, the result only inherits the higher of the two prior-work counts, plus one — not the sum. That single rule is the reason a smart combine order can be dramatically cheaper than an obvious one, and it's exactly what AnvilCalc's solver searches for automatically.
The 39-level wall
In Java Edition, if a single anvil operation would cost 40 levels or more, the anvil refuses it outright and shows Too Expensive! — even in Creative mode, where the display differs but the same cap applies to what you can commit in Survival. Bedrock enforces the same 39-level ceiling per operation, just without the exact "Too Expensive!" wording. This cap applies per step, not to your total build cost — which is exactly why breaking a big enchantment list into the right sequence of smaller merges is often the only way to finish a build that looks impossible at a glance.
Books vs. items as the sacrifice
Combining an enchanted book into an item is cheaper, level-for-level, than sacrificing a second copy of the same item — anvil-core (and the real game) applies a lower cost multiplier for book sacrifices. If you're farming a villager or an enchanting table for a specific enchantment, book results are worth prioritizing over a second full item purely for how much cheaper they are to apply later.
Netherite is a free pass
Upgrading diamond gear to netherite at a smithing table costs no XP, doesn't touch the prior-work penalty, and keeps every enchantment exactly as it was. There's genuinely no reason to delay: enchant the diamond version fully, then upgrade whenever you get the netherite ingot and smithing template. See the Netherite Conversion guide for the full breakdown.
Let the solver do the ordering
All of this — the exponential penalty, the cap, book-vs-item cost, conflicting enchantments — is exactly what the calculator on the home page solves for automatically. Pick your item, tap the enchantments you want, and it returns the cheapest possible sequence of anvil steps, ready to follow in-game.
Frequently asked questions
How do you combine enchantments in Minecraft?
Put the item and an enchanted book (or a second copy of the item) in an anvil's two slots. If none of the enchantments conflict, the anvil merges them onto the result and shows the XP-level cost to pay. Merging a few books in pairs first can be cheaper than adding every enchantment to the item one at a time, because of the prior-work penalty explained above, but merging all of them into one master book usually is not; AnvilCalc's solver searches for the cheapest mix automatically.
What is the prior-work penalty on a Minecraft anvil?
Every time an item or book goes through an anvil, its internal use count goes up by one, and the level cost of its next combine gets multiplied using 2^c minus 1 for that count — 0, 1, 3, 7, 15, 31 extra levels of pure penalty stacked on top of whatever the enchantments themselves cost.
Why does my anvil say Too Expensive?
Java shows Too Expensive! (Bedrock enforces the same limit without the exact wording) whenever a single anvil operation would cost 40 levels or more. It's a per-step limit, not a total-build limit, so reordering your combines into smaller merges is usually enough to get around it — see the Anvil Too Expensive guide for the specifics.
Is it cheaper to combine books together before enchanting an item?
Sometimes: merging a few books in pairs first can keep prior-work counts lower for longer than applying them to the item one at a time. Merging all of them into one big master book first usually costs more, and the master book can still leave the item at a high prior-work count. AnvilCalc's solver searches for the cheapest ordering automatically, so you don't have to work it out by hand.