How to use the calculator in three steps
The tool answers one question: in what order do I combine these books so the total XP bill is as low as possible?
1. Pick the item
The item type filters the enchantment list and drives conflict detection (Sharpness can't coexist with Smite, Protection can't coexist with Fire Protection, and so on). Elytra and mending, mace and breach, boots and Frost Walker — the conflicts are encoded, so you won't be handed an impossible plan.
2. Enter your books
One row per book, one enchantment per book — the librarian-trading case. Set the level with the second dropdown. Duplicate enchantments are handled: two Sharpness III books merge into Sharpness IV, and the calculator knows that.
Looted books with several enchantments can't be entered as a single row; enter each enchantment as its own book. When no enchantment repeats, the final result and total cost are identical.
3. Read the answer
- Total cost — experience levels the whole plan costs, summed over every operation.
- Step list — each row is one anvil trip:
target + sacrifice → cost. The number on the right is that single operation's price. - Green / red per-step cost — anything above 39 levels is refused in Survival, so a red step means that plan can't be performed as written.
- Sequential comparison — what the naive "keep adding books to one item" approach would have cost, so you can see what the optimization bought you.
Reading a worked example
Six books on a sword — Sharpness V, Looting III, Unbreaking III, Mending, Sweeping Edge III, Fire Aspect II. Sequential merging (always adding the next book to the growing item) compounds the penalty until the later steps get expensive. The optimizer instead pairs cheap books early and keeps the tree balanced, which typically lands well under the sequential total. Press Max sword in the tool to see the live numbers rather than a claim here.
What the tool deliberately does not do
- It doesn't model repairing or renaming — those add fixed costs (+2 damaged, +1 rename) that don't change the optimal order.
- It doesn't include Bedrock-only differences (Impaling's cost multiplier, among others). The numbers are Java Edition, per the Wiki.
- It won't invent an order that skips the cap: if every order is too expensive, it tells you so.
Back to the calculator, or read the mechanics behind it.