Commander Tax Explained: What Gets More Expensive and What Does Not

TLDR: Commander tax is an additional {2} generic mana for each previous time you cast that commander from the command zone during the same game. The first command-zone cast has no tax, the second adds {2}, the third adds {4}, and so on. It applies only when you cast that commander from the command zone. It does not increase the card’s mana value, and moving the commander through other zones does not reset the count.

With commander tax explained in one sentence, the practical question is whether your commander is being cast from the command zone. Removal does not automatically create a tax. It usually leads to one because players commonly return their commanders to the command zone and cast them again, but the zone and the number of earlier command-zone casts are what matter.

Commander tax explained with a simple calculation

Start with the cost you are using to cast the commander. Add {2} for every earlier time you cast that same commander from the command zone during this game. Commander tax is an additional cost under the official Commander rules and Comprehensive Rules. The official Commander rules overview provides the format-level rule, while the Magic Comprehensive Rules controls the detailed cost and zone interactions.

Suppose your commander normally costs {3}. Its command-zone casting costs progress like this:

Command-zone cast	Previous casts from command zone	Commander tax	Total before other modifiers
First	0	{0}	{3}
Second	1	{2}	{5}
Third	2	{4}	{7}
Fourth	3	{6}	{9}

The commander does not need to have died between those casts. The rule only asks how many times you previously cast that commander from the command zone. Returning it to your hand, putting it into your library, exiling it, or otherwise changing its zone does not erase that history.

What causes commander tax—and what does not

Commander tax applies when both of these conditions are true:

You are casting a card designated as your commander.
You are casting it from the command zone.

If either condition is missing, the commander-tax rule does not add a cost to that cast. Casting your commander from your hand, graveyard, or exile does not carry commander tax, assuming another rule or effect legally lets you cast it from that zone. That cast also does not increase the number used for future commander tax because it was not a command-zone cast. The existing command-zone cast count still remains if the commander later returns to the command zone.

Putting a commander onto the battlefield without casting it is also different from casting. Commander tax is part of calculating a spell’s cost, so there is no tax to pay when an effect simply puts the card onto the battlefield. The specific effect must still permit that move, and card-specific wording can change how an interaction works.

Does the commander’s first cast include tax?

No. Before the first command-zone cast, there have been zero previous casts from that zone, so the additional cost is {0}. The informal phrase “commander tax” can make it sound like every commander spell starts with a surcharge, but the first cast normally uses the card’s ordinary cost.

Does removing or killing the commander add tax?

Not by itself. Destroying a commander, exiling it, or returning it to its owner’s hand changes where the card is located. The tax appears only if the owner later casts it from the command zone. That distinction matters when deciding whether to move the card back there.

What happens when a commander changes zones

If a commander goes to a graveyard or exile, its owner may move it to the command zone as a state-based action. If it would go to a hand or library, its owner may move it to the command zone instead through a replacement effect. In each case, moving it is optional rather than mandatory.

That choice creates a strategic fork:

Move it to the command zone for reliable access, accepting that the next command-zone cast may cost more.
Leave it in the destination zone when your deck has a dependable and advantageous way to retrieve or cast it there.
Leave it outside the command zone when an immediate recast would be unrealistic and another line offers better value.

Reliable access is usually the main advantage of choosing the command zone. Leaving a commander in the graveyard may avoid tax if you can legally cast or return it from there, but it also exposes the card to graveyard exile and may strand it if your recursion disappears. Leaving it in hand after a bounce spell can let you cast it for its normal cost, but an opponent may then make you discard it. The correct choice depends on your cards, available mana, and opposing interaction.

Importantly, none of these movements resets prior command-zone casts. If you cast your commander twice from the command zone, cast it once from your hand, and later return it to the command zone, its next command-zone cast still has {4} of commander tax.

Commander tax does not change mana value

Commander tax changes the total cost paid for a particular spell. It does not rewrite the commander’s printed mana cost or increase its mana value. A commander with mana value 3 remains mana value 3 even when you must spend {7} to cast it because of two previous command-zone casts.

This matters for effects that refer to mana value. Paying more for your commander does not suddenly make it a larger mana-value card for removal, reanimation, or other restrictions. Keep these concepts separate: mana value describes the card or spell as defined by the rules, while commander tax is one additional component of what you pay.

Cost reductions and alternative costs still interact with the tax

Commander tax is an additional cost, so cost reductions can help pay for the resulting total. If your commander’s applicable casting cost is {3}, its tax is currently {4}, and an effect reduces the generic portion of the spell’s cost by {1}, you would normally pay {6} after that reduction rather than {7}. Reductions do not erase the tax history; they modify the total cost for that cast. Costs cannot be reduced below zero.

Alternative costs follow the same basic principle. If an effect lets you cast the commander for an alternative cost—or without paying its mana cost—from the command zone, commander tax is still added. “Without paying its mana cost” replaces the mana-cost component; it does not waive additional costs.

For example, casting a commander for its mutate cost from the command zone does not avoid commander tax. Mutate supplies an alternative cost, and the accumulated command-zone tax is added to it. The interaction can become more involved after cards merge, so consult the detailed guide to mutate and commanders when the composition or destination of a merged permanent matters.

Two commanders track their taxes separately

If your deck legally has two commanders, each commander keeps its own command-zone cast history. Casting Commander A twice does not make Commander B cost an additional {4}. Commander B’s first cast from the command zone still has no commander tax.

For example, imagine Commander A normally costs {2} and Commander B costs {4}. After you cast A twice and B once from the command zone, the next cast of A costs its applicable cost plus {4}, while the next cast of B adds only {2}. Track the commanders independently with dice or counters if repeated zone changes make the game state difficult to remember.

How commander tax should affect deckbuilding

Commander tax is not just bookkeeping. It determines how expensive failure becomes when a deck relies heavily on keeping its commander in play. A three-mana commander may be easy to deploy initially but become a seven-mana play after two removals. An expensive commander can become impractical to recast much sooner.

The answer is not to fill every deck with protection. Instead, compare the cost of protecting the commander with the cost of rebuilding after it leaves. A commander that supplies the deck’s card draw, mana production, or only realistic win condition deserves more support than a commander that merely improves an already functional plan.

Useful responses include:

Run protection appropriate to the commander’s importance and the interaction used in your pod. Choosing a protection-spell count should account for mana value, colors, strategy, and table speed rather than follow a universal quota.
Build enough mana production to cast the commander and still make another meaningful play. A technically castable commander is not always a useful turn if it consumes all available mana.
Include cards that advance the deck without the commander. Redundant engines, backup payoffs, and independent interaction prevent one removal spell from switching off the entire list.
Avoid casting the commander automatically. If it provides no immediate value and the table clearly has open removal, developing mana or presenting another threat may be better.
Treat repeated commander removal as information. If the commander is always the only threatening permanent, the deck may need a broader plan rather than another narrow defensive card.

Do not cut lands reflexively to fit those support cards. Recasting a taxed commander increases the deck’s mana demands as the game progresses, so a commander-centric list may need a sturdier mana plan than its printed curve initially suggests. The broader Commander deckbuilding framework explains how to make role-based cuts without weakening the mana base first.

Common commander-tax mistakes

Adding {2} after the commander dies even though it has not yet been cast again from the command zone.
Charging tax on the first command-zone cast.
Counting every zone change rather than previous command-zone casts.
Resetting the count when the commander goes to a hand, graveyard, library, or exile.
Increasing the commander’s mana value along with the amount paid.
Treating an alternative cost or “without paying its mana cost” as permission to ignore the tax.
Combining the tax histories of two commanders.

A simple tracking rule prevents most errors: place a die beside the command zone showing the number of previous command-zone casts for that commander. Multiply that number by two when calculating the next cast.

Quick answers

Does commander tax apply after my commander dies?

Only if you move it to the command zone and cast it from there again. Dying itself does not add {2}.

Can cost reducers reduce commander tax?

Yes. Commander tax becomes part of the spell’s total cost, and applicable reductions can reduce that total. The prior-cast count does not disappear.

Does bouncing a commander avoid the tax?

It can avoid tax on the next cast if you leave the commander in your hand and cast it from there. If you choose the command zone instead, the next command-zone cast includes the accumulated tax.

Does mutate avoid commander tax?

No. Mutate is an alternative cost, and casting the commander for that cost from the command zone still requires you to add commander tax.

Is commander tax part of Commander Brackets?

No. Commander tax is a gameplay rule. Commander Brackets are separate pregame guidance for discussing deck expectations.

The rule to remember

Count how many times that specific commander has already been cast from the command zone by that player, then add {2} for each one. Do not count deaths, removal spells, or general zone changes. Track two commanders separately, apply tax on top of alternative costs, and leave mana value unchanged.

For deckbuilding, assume an important commander may need to be cast more than once. Give the deck enough mana, protection, or redundancy to survive that possibility—but choose the mix according to the commander and the table rather than treating commander tax as a reason every deck needs the same package.