How to Calculate Minecraft Anvil Costs: The Complete Enchantment Combining Order Guide

I still remember the exact moment it happened. I had spent three evenings trading with librarian villagers, carefully collecting Sharpness V, Looting III, Mending, Unbreaking III, Fire Aspect II, and Sweeping Edge III. Six perfect books, laid out on my crafting table like little trophies. Then I walked up to the anvil, started adding them one by one to my netherite sword — and on the fifth book, the screen flashed: "Too Expensive!"

That was the day I learned that in Minecraft, how you combine enchantments matters just as much as which enchantments you choose. The anvil has a hidden cost system that punishes you for working on the same item too many times — and if you don't understand it, you'll waste dozens of XP levels and potentially lock yourself out of adding more enchantments forever.

This guide breaks down the exact formula behind Minecraft anvil costs, explains the prior work penalty in plain language, and shows you the optimal enchantment combining order for swords, pickaxes, and armor — with real numbers, step-by-step examples, and a comparison between Java Edition and Bedrock Edition.

1. What Is the Prior Work Penalty?

Every item and enchanted book in Minecraft carries a hidden counter called the prior work penalty (stored internally as repair_cost in Java Edition). It starts at zero for any fresh item or book you pick up. Each time that item is used in the left slot of an anvil — whether you're adding an enchantment, repairing it, or combining it with another item — its penalty counter increases by one.

The penalty itself doesn't cost you anything directly. What it does is inflate the XP cost of every future anvil operation involving that item. And the inflation is exponential, not linear. The formula is:

Here's what that looks like in practice:

There's one more important rule: when you combine two items, the resulting item inherits the higher of the two penalties, plus one. So if you combine a sword with penalty 2 and a book with penalty 1, the resulting sword has penalty 3. This is why combining books together first — before touching your main item — is so powerful.

2. The Complete Anvil Cost Formula

Every anvil operation has a total cost made up of several components. Understanding each one helps you predict costs and plan your combining order.

Let's walk through each component:

Enchantment Cost

Each enchantment has a base cost that depends on its rarity and the final level being applied. When using a book as the sacrifice (right slot), the multiplier is lower than when combining two items directly — this is one reason why enchanted books from villager trading are so efficient. The full multiplier table is in the next section.

In Java Edition, you pay for the final level of the enchantment on the resulting item, multiplied by the enchantment's multiplier. In Bedrock Edition, you only pay for the increase in level — which makes Bedrock significantly cheaper for many operations.

Penalty Costs

Both the left item (target) and the right item (sacrifice) contribute their penalty costs to the total. This is why a book with penalty 0 from a villager is so much cheaper to use than a book you've already combined once (penalty 1 = +1 level extra, penalty 2 = +3 levels extra, and so on).

A Worked Example

Let's say you're adding a Sharpness V book (penalty 0) to a netherite sword that you've already enchanted once (penalty 1):

3. Enchantment Cost Multipliers Table

Each enchantment has two multipliers: one for when you combine two items directly, and a lower one for when you use an enchanted book. This is why getting max-level books from villagers and applying them directly is almost always more efficient than combining two enchanted items.

4. Why Combining Order Matters So Much

Here's the core problem: every time you put your main item in the left slot of an anvil, its penalty goes up by one. If you add six enchantment books one at a time directly to your sword, the sword's penalty climbs from 0 to 6. By the time you're adding the sixth book, you're paying 2⁵ − 1 = 31 extra levels just in penalty overhead — before even counting the enchantment's own cost.

Compare that to a strategy where you combine books together first, then apply the combined books to your sword. The sword only goes into the anvil three or four times instead of six, keeping its penalty low throughout.

The difference is dramatic. The wrong method accumulates 26 levels of penalty overhead on the sword alone. The pyramid method keeps it to just 4 levels on the sword. That's 22 levels saved — enough to push you from "Too Expensive!" to a successful operation.

5. The Pyramid Method: Optimal Combining Strategy

The pyramid method (also called the "balanced tree" approach) is the standard strategy for minimizing anvil costs when applying multiple enchantments. The idea is simple: instead of a linear chain where one item accumulates all the penalty, you build a branching structure where penalties stay balanced across all items.

The General Rules

1. Combine books in pairs first. Two fresh books (penalty 0) combined produce a book with penalty 1. That's much cheaper to apply to your item than two separate operations.
2. Balance the tree. Try to combine items that have similar penalty values. Combining two penalty-1 books gives a penalty-2 book. Combining two penalty-2 books gives a penalty-3 book. Keep the levels even.
3. Put expensive enchantments in the sacrifice slot fewer times. Enchantments with high multipliers (Thorns, Soul Speed, Silk Touch) cost more every time they appear in the right slot. Arrange your combining order so these appear as the sacrifice as rarely as possible.
4. Apply combined books to your item last. Your main item should only enter the anvil during the final stages, when it's receiving large combined books rather than individual ones.

How Many Books Can You Realistically Combine?

6. Step-by-Step Examples

Example 1: Netherite Sword (6 Enchantments)

Target enchantments: Sharpness V, Looting III, Unbreaking III, Mending, Fire Aspect II, Sweeping Edge III

All books are fresh from villager trading (penalty 0). Here's the optimal combining order, optimized for least total XP:

Total cost: 11 + 5 + 10 + 12 + 7 + 14 = 59 levels. Adding books one by one would cost approximately 80+ levels and likely fail on the last step.

Example 2: Diamond Pickaxe (5 Enchantments)

Target enchantments: Efficiency V, Fortune III, Unbreaking III, Mending, Silk Touch

Wait — Fortune and Silk Touch are mutually exclusive. You can't have both on the same pickaxe. This is one of the most common mistakes new players make. Choose one: Fortune III for resource farming, or Silk Touch for collecting blocks intact. See our enchantment compatibility guide for a full list of conflicts.

Let's go with Efficiency V, Fortune III, Unbreaking III, Mending (4 enchantments):

Total: 35 levels. Clean, efficient, and well under the 39-level cap at every step.

Example 3: Diamond Boots (7 Enchantments)

This is where it gets interesting. Target: Soul Speed III, Thorns III, Mending, Depth Strider III, Feather Falling IV, Protection IV, Unbreaking III

With 7 enchantments, the order becomes critical. The key insight from the Minecraft Wiki's best enchantments guide is that high-cost enchantments like Soul Speed III (cost 12) and Thorns III (cost 12) should be applied to the boots early, before the penalty builds up. Here's the optimal sequence:

Total: 88 levels across all operations. Every single step stays under the 39-level cap. Without planning, this combination would almost certainly hit "Too Expensive!" before all 7 enchantments are applied.

Want to see the optimal order for your specific combination? Check out our best builds page for pre-calculated setups, or use the calculator to generate a custom order.

7. Java Edition vs. Bedrock Edition: Key Differences

The anvil cost system works similarly in both editions, but there are meaningful differences that affect how you plan your enchanting — especially if you're switching between platforms or playing on a server that mixes editions.

What This Means in Practice

If you're playing Bedrock Edition, you'll find that many operations that would be borderline "Too Expensive!" in Java Edition are comfortably under the cap. The Bedrock cost model only charges you for the improvement — so if you're upgrading Looting II to Looting III, you only pay for one level of Looting, not three.

In Java Edition, you pay for the full final level every time, which is why the combining order matters even more. A Looting III book applied to a sword always costs 6 levels (3 × multiplier 2) in Java, regardless of whether the sword already has Looting I or Looting II.

The pyramid method works for both editions — it's just that Bedrock players have a bit more margin for error. Our enchantment calculator supports both editions and accounts for these differences automatically.

8. Frequently Asked Questions

Why does my anvil say "Too Expensive!" even though I have enough levels?

The 39-level cap is a hard limit on the cost of the operation, not on your current XP. Even if you have 100 levels, an operation that costs 40 levels will be blocked. This usually happens because your item has been used in the anvil too many times, accumulating a high prior work penalty. The only fix is to start over with a fresh item and plan your combining order from the beginning.

Can I reset the prior work penalty?

Not without losing your enchantments. Repairing an item on a crafting table removes all enchantments, custom names, and prior work penalties — but that defeats the purpose. A grindstone removes enchantments and penalties but keeps the custom name. There's no way to reset the penalty while keeping your enchantments in vanilla Minecraft.

Should I combine books before applying them to my item?

Almost always yes. Combining books first keeps your main item's penalty low, which is the single most effective way to reduce total costs and avoid "Too Expensive!" errors. The only exception is when you only have 1–2 enchantments to apply — in that case, applying directly is fine.

Does the order of books in the anvil slots matter?

Yes, significantly. The item in the left slot (target) keeps its penalty and gains one. The item in the right slot (sacrifice) is consumed. In Java Edition, you also pay the full enchantment cost based on the sacrifice's enchantments. Putting a high-cost book in the right slot repeatedly is expensive — try to arrange your order so costly enchantments appear in the sacrifice slot as few times as possible.

What's the maximum number of enchantments I can put on one item?

It depends on the item. Swords can hold up to 7 enchantments (Java) or 6 (Bedrock, no Sweeping Edge). Boots can hold 7–8. Helmets can hold up to 6. The limiting factor isn't usually the number of enchantments — it's the total cost of applying them all. With the pyramid method and fresh books, most items can reach their maximum enchantment count. See our best builds page for the full breakdown by item type.

Is there a difference between enchanting a diamond item vs. a netherite item?

No — the anvil cost calculation is identical regardless of the item's material. Netherite items have higher durability and are blast-resistant, but the enchanting process and costs are the same as diamond. The enchantments available also don't change between diamond and netherite versions of the same item type.

How does the anvil cost formula work for Bedrock Edition specifically?

In Bedrock, the enchantment cost is calculated as: (final level − current level on target) × book multiplier. So if your sword already has Sharpness III and you're adding a Sharpness V book, you only pay for 2 levels (V − III = 2) × 1 = 2 levels, not 5. This makes upgrading existing enchantments much cheaper in Bedrock than in Java. The prior work penalty formula is the same in both editions.

Playing a modpack instead of vanilla? ATM10 and Apotheosis-style enchanting can make anvil costs feel different because pack configuration and XP charging may change the final number. See our ATM10 Apotheosis anvil prior work penalty guide for the modded version of this problem.