Minecraft Anvil Cost Explained

The anvil’s experience cost looks random until you know the formula. It is actually deterministic: three components add up to the level cost of every single combine. Once you can compute it by hand, the “Too Expensive!” message stops being a mystery. The enchantment calculator does this math for every possible order and returns the cheapest.

The three cost components

Prior-work penalty (kept item) — a surcharge based on how many times the left item has been on an anvil.
Prior-work penalty (sacrificed item) — the same surcharge for the right item.
Enchantment transfer — each enchantment on the sacrificed item, priced as level × rarity multiplier.

Renaming an item adds a flat 1 level; repairing with raw material costs 1 level per unit consumed; and repairing by sacrificing a second copy of the item costs a flat 2 levels. All three are separate from enchantment combining and stack on top of the prior-work penalties.

How to use the operation simulator

Start by choosing the operation that matches the two anvil slots. Transfer enchants means the right slot supplies enchanted books or another enchanted item.Repair with material covers a repair ingredient such as an ingot or diamond. Combine two items is the durability repair from sacrificing a second item of the same type. Rename onlyisolates Java’s special rename rule. These operations have different base costs, so choosing the nearest mode is more reliable than trying to force every case through enchantment transfer.

“Prior anvil uses” is the hidden work count, not the number of visible enchantments and not the item’s repair cost shown in the UI. A newly obtained item normally starts at zero. Each non-rename anvil result takes the larger work count of its two inputs and adds one. If commands or old anvil work changed an input, enter that existing count before comparing the simulator with the game.

For an enchantment transfer, enter the level that will exist on the result and the effective multiplier for the sacrificed source. A book uses the lower book multiplier; transferring directly from another item uses the item multiplier. The standalone simulator accepts the multiplier rather than an enchantment name so it can also explain a single step outside a complete loadout. For a named, conflict-checked build, use the optimizer instead.

The prior-work penalty doubles every time

This is the single most important number to understand. The penalty follows 2ⁿ − 1 where n is the number of previous anvil uses:

0 prior uses → 0-level penalty
1 prior use → 1-level penalty
2 prior uses → 3-level penalty
3 prior uses → 7-level penalty
4 prior uses → 15-level penalty
5 prior uses → 31-level penalty
6 prior uses → 63-level penalty

Because this penalty is charged for both items in every future combine, an item that has passed through the anvil six times already carries a 63-level surcharge — well past the survival cap — before any enchantment is even transferred. That is the entire reason combine order matters.

The rarity multipliers

From a book, enchantments cost their level times 1, 2, or 4 depending on rarity (applying directly from another tool doubles each). The 8 very-rare enchantments at multiplier 4 are the dangerous ones — moving a single very-rare enchantment a second time costs as much as moving four common ones.

Combining equal and unequal enchantment levels

Two equal levels normally combine into the next level, up to that enchantment’s maximum: two Sharpness IV inputs can produce Sharpness V. If the levels differ, the higher compatible level is retained rather than added together. The transfer charge is based on the level placed on the result, which is why entering the final transferred level matters. Enchantments that cannot apply to the target, or that conflict with an enchantment already present, require separate handling; the loadout calculator prevents those combinations instead of pretending they are a normal usable build.

Repair and rename edge cases

Material repair charges one level for each repair unit actually consumed, up to the operation’s repair-unit limit. Combining two matching items charges the item-repair base cost and merges durability according to the game’s repair rules; this simulator explains the XP charge rather than predicting the exact durability bar. The interactive modes isolate one primary operation at a time for inspection; if one in-game operation both repairs durability and transfers enchantments, add the applicable repair component when checking the formula or reproduce the exact inputs in-game.

A Java rename-only operation is exceptional: when prior work would otherwise push it over the normal survival threshold, the charged cost is capped at 39. Renaming alone does not increase the prior-work count. If the same operation also repairs or transfers an enchantment, it is no longer rename-only and the normal 40-level rejection rule applies.

Worked example: an Infinity bow

A Bow with Power V, Punch II, Flame, Infinity and Unbreaking III. The cheapest survival-legal order the optimizer finds costs 29 levels, peaking at 11 levels on its priciest step:

Bow + Book: Power V — 5 levels
Book: Punch II + Book: Flame I — 2 levels
Bow (Power V) + Book (Punch II, Flame I) — 8 levels
Book: Infinity I + Book: Unbreaking III — 3 levels
Bow (Power V, Punch II, Flame I) + Book (Infinity I, Unbreaking III) — 11 levels

The 39-level “Too Expensive” cap

In Survival and Adventure mode the anvil refuses any single operation worth 40 levels or more. The cap is per-step, not per-project: you may spend far more than 39 levels across a sequence of combines, but no individual step may reach 40. Creative mode removes the cap. When a plan crosses the line, the calculator marks it red and points at the step that broke it.

Java vs Bedrock

The formula above is shared by both editions. Within this site’s compatible-book planning model, Impaling costs half as much in Bedrock. Bedrock also omits the +1 surcharge Java applies per incompatible enchantment, a case the optimizer prevents by blocking conflicting selections. For a non-conflicting loadout without Impaling, the calculated order and cost are the same in both — read more on the calculator page, where you can toggle editions directly.

Frequently asked questions

Do experience points and experience levels cost the same amount?

No. Anvils charge levels, and each level requires a different number of raw experience points depending on the player’s current level. A 30-level operation removes 30 displayed levels; it is not a flat 30 experience points. This calculator reports the same level number shown by the anvil.

Does renaming increase prior work?

Renaming by itself does not increase the item’s prior-work count. If the same anvil operation also repairs the item or transfers enchantments, the operation is no longer rename-only and the resulting item receives the normal updated work count. That distinction is why the simulator separates rename-only from the “also rename” checkbox on other modes.

Why is my in-game cost different?

Check which side holds the retained item, whether either input already has prior work, whether the sacrifice is a book or an item, and whether repair or renaming happens in the same operation. Also confirm edition, game version and any server plugins. The simulator isolates documented vanilla cost components; modified anvil rules require the server’s own documentation.

For a reproducible comparison, record both input items, their visible enchantments, which slot each occupies, the proposed result and the displayed level cost before changing anything. Those details usually reveal the missing component.

This operation costs