MTG Commander Damage Explained: The 21 Rule, Every Edge Case, and the Commanders That Get There (2026)

Every page you have ever read about commander damage tells you the same sentence: deal 21 combat damage with the same commander and that player loses. That sentence is correct, and it is where every one of those pages stops. It is also almost never the thing you needed to know, because the arguments that actually break out at a table are never about the number 21. They are about whether the token copy counts, whether the infect swing counts, whether gaining forty life bought you anything, and whether the counter went back to zero when you finally killed the thing.

This guide answers those. Every rule below is quoted from the official Magic: The Gathering Comprehensive Rules text file effective 7 August 2026 — the version Wizards published alongside The Hobbit — and every card is verified against the live Scryfall database at the time of writing, including its current Commander legality and price. Where a widely repeated piece of advice is wrong, it is named.

The rule, in the exact words that matter

Commander damage is written into the Comprehensive Rules in three separate places, and all three say the same thing. That redundancy is worth knowing about, because it means there is no obscure fourth clause hiding somewhere that changes the answer.

Being a state-based action is not trivia. It means nobody has to notice, nobody has to do anything, and it cannot be responded to. The game checks the condition every time a player would receive priority, and the moment the 21st point has been dealt, that player has lost. You cannot hold up an instant to save yourself after the damage resolves, for the same reason you cannot respond to dying at 0 life — and that is the same timing rule that governs everything in flash, priority and the stack.

Four words decide every argument: “combat damage by the same commander”

Nearly every real dispute over commander damage comes down to one of those four words. Here is what each one excludes.

The second row is the one that costs games. A commander with high power that keeps getting chump-blocked is making no progress at all on the 21 clock, no matter how much damage it “deals” each turn — which is why evasion, not power, is the real currency of this strategy.

Nothing resets the counter. Nothing.

“Over the course of the game” is doing enormous work in 903.10a. The count is a permanent property of a pairing — this commander, that player — and there is no card, effect, or sequence of events in Magic that sets it back to zero. Players get this wrong constantly, usually in a way that gets them killed.

The practical consequence: partial commander damage is an unremovable liability. If you have taken 14 from one commander, that number will still be 14 in an hour, and every removal spell you hold for that commander is worth more than it looks. This is exactly the situation where a cheap exile effect earns its slot over a cheap destroy effect — not because exile removes the damage, but because it removes the recursion.

Partners, Backgrounds and the Doctor’s companion: two counters, not one

If a player has two commanders, this is the rule that decides the game, and it is quoted almost nowhere. Rule 702.124d is unambiguous:

“When determining whether a player has been dealt 21 or more combat damage by the same commander, consider damage from each of your two commanders separately (see rule 903.10a).”

Rule 702.124a lists the abilities that let you do this: partner, partner—[text], partner with [name], choose a Background, and Doctor’s companion. So a partner pair that has hit you for 12 and 11 has dealt you 23 total combat damage and has killed nobody. You are on two separate clocks, both of them unreset, and neither has fired.

This cuts both ways for the attacker. Two commanders means two ways to be blocked, two removal targets, and two counters that each have to reach 21 independently — which is why partner pairs are usually built as value engines rather than as commander-damage kills, and why a single-commander build like a dedicated voltron deck closes faster on this axis despite having half the cards in the command zone.

The trap that ends more games than any other: copies are not your commander

This is the single most expensive misunderstanding in the format, and the rule that settles it is one sentence in 903.3:

“This designation is not a characteristic of the object represented by the card; rather, it is an attribute of the card itself.”

A token is not a card. It has no card underneath it. It therefore cannot carry the commander designation, no matter how perfect a copy it is — and a token copy of your commander deals zero commander damage. Three very popular cards run straight into this.

Sakashima is the exception that proves the rule and the reason the rule is worth learning properly. It is not a copy of your commander; it is your commander, wearing something else’s face. Meanwhile Blade of Selves — a card that appears in a great many “voltron” primers — turns your commander into a value engine and quietly stalls the kill you were building toward. Note the further wrinkle: myriad tokens are legendary copies, so on a legendary creature they also collide with the legend rule the instant they arrive.

Your commander can now be a Vehicle or a Spacecraft — and it changes the math

Almost every article on this subject was written when 903.3 read differently. As of the current rules, the card you designate as your commander must be:

“either (a) a creature card, (b) a Vehicle card, or (c) a Spacecraft card with one or more power/toughness boxes.” — 903.3

A live Scryfall query confirms the scale of this: 40 Vehicles and 5 Spacecraft can legally be designated as a commander right now. Both deal combat damage to players when they are creatures, so both accumulate commander damage normally.

There is also a genuine internal wrinkle worth flagging, because it will confuse anyone who reads the rules top to bottom: 903.1 still describes Commander as a format where “each deck is led by a legendary creature.” That summary sentence is narrower than the actual requirement two rules later. 903.3 is the operative text.

Dawnsire deserves the emphasis. A 20/20 commander that connects with an untouched opponent has dealt twenty commander damage, and 903.10a requires twenty-one. Every single-point pump effect in your deck is, in that specific board state, a lethal spell. It is the cleanest demonstration in the game that the threshold is 21 and not 20.

Infect and toxic: two clocks running at once, and one of them is faster

The most common rules question about commander damage that page one of Google does not answer: does infect damage count? Yes. The derivation is short and comes straight from the rules on how damage is processed.

Rule 120.4b deals the damage. Rule 120.4c then processes “damage that’s been dealt” into its results. Rule 120.3b defines that result: “Damage dealt to a player by a source with infect causes that source’s controller to give the player that many poison counters.” Infect changes the result of the damage. The damage was still dealt, by your commander, in combat, to a player — which is the entire test in 903.10a.

So a commander with infect is running two independent loss conditions against the same opponent simultaneously: the 21-damage clock, and the ten-poison-counter clock in 104.3d. The poison clock is less than half as long.

Note the distinction in that last row. Toxic is not infect. Rule 120.3g: combat damage from a creature with toxic deals its damage normally and gives poison counters “in addition to the damage’s other results.” A toxic commander therefore drains life, builds commander damage, and stacks poison from the same connection — three clocks, not two. An infect commander trades the life-total clock away for the poison one.

One warning on Grafted Exoskeleton: “Whenever this Equipment becomes unattached from a permanent, sacrifice that permanent.” Any effect that moves it — including a well-meaning one of your own — kills your commander. It goes back to the command zone under 903.9a, but the damage clock does not care and neither does your board.

Damage doublers count. Life-loss doublers do not.

This is the most valuable single distinction in this article and it is almost never stated. Both categories of card kill an opponent faster. Only one of them moves the commander damage counter.

A damage replacement effect changes how much damage is dealt, so 903.10a sees the larger number. A life-loss replacement effect leaves the damage alone and doubles the life the player loses afterwards — so the opponent’s life total falls twice as fast while the commander damage counter creeps up at its original rate. Compare the two oracle texts directly:

Bloodletter of Aclazotz is a $37 card that appears in a great many aggressive black lists, and against an opponent you are trying to kill with commander damage specifically, it does nothing for that plan. It is an excellent card doing a different job. Fireshrieker, at 22 cents, does more for the 21 clock than Bloodletter does — because double strike deals combat damage twice, and both instances are combat damage from your commander.

The arithmetic: how many connections you actually need

Twenty-one is an awkward number by design. It is one more than a starting life total in most other formats and one more than the largest common power value, and it repeatedly lands a swing short of where players expect.

Two rows repay study. At power 10, two connections deal twenty and you need a third whole combat to finish a job that looks done — which is why “+1/+1” effects are disproportionately valuable in these decks and why power 11 is the real breakpoint for a two-swing kill. And double strike is mathematically identical to a damage doubler on this clock while costing far less, because both instances of combat damage are dealt by the commander.

The cards that get you there

Commander damage is not a power problem. It is a connection problem: your commander has to survive removal, get past blockers, and land damage on a player rather than a creature, repeatedly. These are the pieces that solve those three problems, all Commander-legal and all verified today.

Trample deserves a specific note here because it is routinely overrated for this plan. Trample damage assigned to a player is combat damage from your commander and does count — but you only get the excess, so a 12/12 trampler into a 5/5 blocker moves your counter by seven, not twelve. Deep-dive on how trample, double strike and the rest interact in the combat damage keywords guide, and see the full equipment rankings for the pieces that pull double duty in other archetypes.

Commanders that realistically close on 21

A commander that gets there needs some combination of high power, built-in evasion, a damage multiplier stapled to its own text, or protection from removal. These are verified Commander-legal, with current prices, and none of them are Game Changers under the bracket system — which means every one of them is legal in a Bracket 2 deck.

Zurgo is the honest budget pick on this list. A 7/2 for four mana that must attack every turn, is indestructible on your own turn, and needs precisely three connections — with a 56-cent price tag. The fragility is real: 2 toughness dies to almost anything on an opponent’s turn, which is exactly what Darksteel Plate and Whispersilk Cloak are for.

Defending against it

Because the counter never resets, the defensive game is entirely about preventing connections — and about answering the commander before the count gets uncomfortable rather than after.

Note why Fog is categorically different from life gain. Rule 120.4b deals damage “as modified by replacement and prevention effects.” Prevented damage is never dealt, so it never enters the commander damage count in the first place. Life gain happens strictly after the damage was dealt and counted. The two are not remotely equivalent, and against a commander-damage deck only one of them is doing anything.

Teferi’s Protection is the only Game Changer on this list, which matters if you are building to a specific bracket — the same framework covered in detail in the Commander brackets and Game Changers guide.

You can lose the game to your own commander

Read 903.10a once more with this in mind: “A player who’s been dealt 21 or more combat damage by the same commander.” There is no clause about whose commander it is, and no clause about who controls it.

If an opponent takes control of your commander — Mind Control ($0.25), Agent of Treachery ($4.63), or any of the format’s many theft effects — and swings it back at you, that damage is dealt by “the same commander” and accumulates against you exactly as it would against anyone else. Combine that with the fact that the count never resets, and a commander you have already used to hit an opponent for 14 becomes a two-turn clock on you the moment it changes hands.

This is a real and underrated argument for keeping a way to sacrifice or bounce your own commander in decks built around a very large one. It is also the reason a stolen commander is worth answering immediately rather than racing.

A starting package

The following is a functional commander-damage core rather than a complete list — the protection, evasion and multiplier pieces that any build of this archetype wants, priced today. Slot it around whichever commander you have chosen from the table above, then fill out lands and ramp to taste.

Every card in that package is Commander-legal as of today and none of them are Game Changers, so the package itself does not push a deck out of Bracket 2. If you would rather start from a finished list, there are thousands of public builds on the community deck browser, and you can check any of these prices yourself with the card price tool.

The mistakes that decide games

Frequently asked questions

How much commander damage kills a player?

Twenty-one or more combat damage from the same commander over the whole game, per rule 903.10a. Twenty does not do it.

Does commander damage from two commanders add together?

No. Rule 702.124d requires you to “consider damage from each of your two commanders separately.” Twelve from one and eleven from the other is 23 total damage and zero progress toward the rule.

Does noncombat damage from my commander count?

No. Activated abilities, triggered abilities, fight damage and spell damage never count, even when your commander is unambiguously the source. The rule says combat damage.

Does gaining life reset commander damage?

No. The two loss conditions are completely independent. A player at 200 life who has taken 21 from one commander loses.

Does killing the commander reset the count?

No, and neither does exiling it, recasting it, or its returning to the command zone. Rule 903.3 states that the commander designation is an attribute of the card, which it retains across every zone change.

Do token copies of my commander deal commander damage?

No. A token is not a card, so it cannot be a commander. This applies to Blade of Selves myriad tokens, Helm of the Host copies, and every other token copy effect.

Does infect damage from my commander count toward 21?

Yes. The combat damage is still dealt (rule 120.4b); infect only changes the result into poison counters (120.3b). You are running the 21-damage clock and the ten-poison clock at once.

Do damage doublers increase commander damage?

Yes, if they replace the damage — Fiery Emancipation, Gratuitous Violence, Dictate of the Twin Gods. No, if they replace the life loss, like Bloodletter of Aclazotz.

Does commander damage apply in a two-player Commander game?

Yes. Rule 903.2 explicitly allows a Commander game to be a two-player game, and nothing in 903.10a is restricted to multiplayer.

Can I lose the game to my own commander?

Yes. Rule 903.10a says “the same commander,” not “an opponent’s commander.” If somebody steals yours and attacks you with it, that damage counts against you.

The short version

Twenty-one, combat only, to a player only, per commander, never reset. Tokens do not count, infect does, damage doublers do, life-loss doublers do not, and your own commander can kill you if somebody borrows it. Everything else is arithmetic — and the arithmetic is unforgiving in a way that is easy to miss, because 21 keeps landing exactly one point past where a clean number would put you.

If you want to see how a commander-damage plan looks in a finished ninety-nine, the fastest route is to describe the commander you want to build around and let the deck builder do the first draft — then test your commander recognition against the format in Guess That Commander.