If a single commander has dealt you 21 or more combat damage over the whole game, you lose, no matter what your life total is. That is the entire rule. It counts per commander, not per opponent, it counts combat damage only, and the total builds up across turns rather than resetting.
This guide is part of our MTG keywords and mechanics glossary, the index of every mechanic guide on Mana Grove.
You start a Commander game at 40 life (rule 903.7), so commander damage is a second and much faster clock running alongside the first. A 7 power commander needs three unblocked attacks to kill you through the commander damage rule, and six to kill you through your life total.
What the rule actually says
The Comprehensive Rules state it in one sentence, in rule 903.10a:
A player who's been dealt 21 or more combat damage by the same commander over the course of the game loses the game.
The same sentence appears in the list of ways to lose a game (rule 104.3j) and in the list of state based actions (rule 704.6c). A state based action is a game action that happens automatically whenever its condition is met, and it does not use the stack (rule 704.1). It is checked throughout the game and is not controlled by any player (rule 704.2), specifically whenever a player would get priority (rule 704.3). So nobody has to announce it: if the twenty first point of damage lands, you lose at the next check, whether or not anyone at the table noticed.
Three words in that sentence do all the work: combat, same, and game.
The five things players get wrong
1. Only combat damage counts
The rule says combat damage. Damage your opponent's commander deals any other way does not add to the total: not a triggered ability, not an activated ability that pings you, not a spell the commander somehow copies. If it did not happen in a combat damage step, it is ordinary damage and it only reduces your life total. The rules define the term precisely: combat damage is "damage dealt during the combat damage step by attacking creatures and blocking creatures as a consequence of combat" (Comprehensive Rules glossary, "Combat Damage").
This cuts both ways for the attacker. A commander built to throw damage at faces is on the 40 life clock, not the 21 clock.
2. It is per commander, not per opponent
"The same commander" means each commander keeps its own tally against each player. Three opponents attacking you with three different commanders are running three separate counters of 21. Nine damage from one, seven from another and eight from a third is 24 damage to your life total and nothing at all toward the commander damage rule.
The same is true of a deck with two commanders. The partner abilities let a player designate two legendary cards as their commander (rule 702.124a), and both start in the command zone (rule 702.124b), but rule 903.10a still says "the same commander", so each one needs to get to 21 on its own. Rule 702.124d says it outright: when working out whether a player has taken 21 or more combat damage from the same commander, "consider damage from each of your two commanders separately".
3. It does not reset
Rule 903.10a counts damage "over the course of the game". Nothing in the rule resets the total, and the commander designation is an attribute of the card itself rather than of the object on the battlefield, so the card keeps that designation even when it changes zones (rule 903.3).
So killing the commander does not clear the tally. If a commander dealt you 14 damage, died, went back to the command zone (rule 903.9a) and came back, it needs 7 more, not 21 more. Bouncing it, exiling it or having its controller tuck it away changes nothing about the damage already dealt.
4. Your life total is a separate clock
Two different state based actions can kill you, and they do not talk to each other. You lose if your life total is 0 or less (rule 104.3b), and you lose if one commander has dealt you 21 or more combat damage (rule 903.10a). Both are checked at the same moment, whenever a player would get priority (rule 704.3).
Gaining life does not undo commander damage. A player who has taken 14 from one commander and then gained their way back up to 38 life is still exactly seven points of that commander's damage away from losing, and no amount of lifegain changes that number.
5. A token copy of a commander is not a commander
This is the edge case that ends arguments. Rule 903.3 says the commander designation "is not a characteristic of the object represented by the card; rather, it is an attribute of the card itself". A token is a marker used to represent a permanent that is not represented by a card (rule 111.1). A token copy of somebody's commander therefore is not a commander, and the damage it deals you does not go on that commander's tally.
Trample and double strike do the maths for you
Two keywords make commanders reach 21 much faster than their power suggests.
Trample. The controller of an attacking creature with trample assigns lethal damage to the blockers first, and then may assign the excess to the player being attacked (rule 702.19b). That excess is still combat damage dealt by the commander, so it counts. A blocker does not save you from a big trampler, it only reduces the number. Note the other half of rule 702.19b, because this is where people go wrong: the attacker does not have to assign lethal damage to every blocker, but if they do not, they cannot assign any damage to the player at all.
Ghalta, Primal Hunger, {10}{G}{G}, is a 12/12 with trample that costs {X} less to cast where X is the total power of your creatures. Two connections is 24 damage, which is over the line, and chump blocking only buys a turn.
Double strike. If any attacker or blocker has first strike or double strike as the combat damage step begins, the combat phase gets a second combat damage step, and creatures with double strike assign damage in both (rule 702.4b). That is two lots of combat damage from one attack. First strike and double strike, explained has the full timing.
Rafiq of the Many, {1}{G}{W}{U}, is a 3/3 with exalted that also gives a lone attacker double strike until end of turn. Attacking alone, Rafiq is a 4/4 with double strike, so an unblocked swing deals 8 combat damage. Three of those is 24.
The commanders that actually get there
An unblocked creature assigns its combat damage to the player it is attacking (rule 510.1b), so the arithmetic is just power times connections.
| Commander | Cost | Power | Unblocked attacks to reach 21 |
|---|---|---|---|
| Ghalta, Primal Hunger | {10}{G}{G} | 12, trample | 2 |
| Zurgo Helmsmasher | {2}{R}{W}{B} | 7, haste | 3 |
| Rafiq of the Many | {1}{G}{W}{U} | 3, but a 4/4 with double strike attacking alone, so 8 a swing | 3 |
Zurgo is the clean example of why the rule matters: 7 power, haste, and indestructible during its controller's turn, so it attacks the turn it lands and survives most of what happens in combat. Three connections and exactly 21, which ends the game for a player who has taken nothing from anybody else. You are out with 19 of your 40 life still left.
Equipment shortens every one of those counts. Colossus Hammer, {1}, gives +10/+10 and takes away flying, with equip {8}. Blackblade Reforged, {2}, gives +1/+1 for each land you control and costs only {3} to equip to a legendary creature. Sword of Feast and Famine, {3}, adds +2/+2, protection from black and from green, and untaps all your lands on connection.
And a counter example worth naming, because it is the most common misreading of the format: Kaalia of the Vast, {1}{R}{W}{B}, is only a 2/2 with flying. She would need eleven connections to kill anyone with commander damage. She is dangerous because attacking puts an Angel, Demon or Dragon from your hand onto the battlefield tapped and attacking, not because of her own damage. Plenty of strong commanders are on the 40 life clock, not the 21 clock.
How not to die to commander damage
Because the clock is per commander, the answer is usually to stop that one creature rather than to gain life.
- Remove it. Swords to Plowshares, {W}, exiles a creature for one mana. Exiling is better than destroying here because exile gets past indestructible, which Zurgo Helmsmasher has during its controller's turn. Either way, the owner may move the commander to the command zone (rule 903.9a) and cast it again for the rest of its 21, but each cast from there costs {2} more than the last (rule 903.8).
- Tax the attack. Propaganda, {2}{U}, and Ghostly Prison, {2}{W}, each stop creatures attacking you unless their controller pays {2} for each attacker. At a four player table that usually means they attack somebody else.
- Prevent the damage. Maze of Ith untaps a target attacking creature and prevents all combat damage that would be dealt to and by it that turn. Prevented damage is never dealt, so it never reaches the tally.
- Block, but do the sum first. Blocking a trampler reduces the damage rather than stopping it. Blocking a 12/12 trampler with a 2/2 still sends 10 to your face.
The cheapest protection is attention. Track the running total per commander out loud, the way the table tracks life, and you will notice the third attack coming before it arrives.
When it is 21, and when the rule is switched off
The rule applies to Commander games whether the game is two player or multiplayer, since both are Commander games (rule 903.2).
The one place it does not apply is Brawl. Brawl is an option for a different style of Commander game, and rule 903.12h says plainly that Brawl games do not use the state based action in rule 704.6c, the one that causes a player to lose to 21 commander damage. Brawl also uses 60 card decks (rule 903.12d) and starts players at 25 life in a two player game or 30 in a multiplayer one (rule 903.12f). So in Brawl there is no commander damage rule at all.
Frequently asked questions
What is commander damage in MTG?
Commander damage is the combat damage a commander deals to a player, tracked separately for each commander against each player. A player who has been dealt 21 or more combat damage by the same commander over the course of the game loses (rule 903.10a), whatever their life total. Only combat damage counts, and the total never resets (rule 903.3), even when the commander dies and comes back.
How much commander damage do you need to lose?
21 or more combat damage from the same commander over the course of the game (rule 903.10a). It is counted per commander and per player: 21 from one commander ends your game whatever your life total, while damage from two different commanders never adds together. It is also combat damage to a player, so it takes the crown from the monarch like any other combat damage.
Is it 21 damage or 21 damage per opponent?
Twenty one from each individual commander, tracked separately against each player. Damage from different commanders never combines, and damage one commander deals to different players is tracked separately for each of those players.
Does commander damage reset if the commander dies?
No. The rule counts combat damage from the same commander over the course of the game (rule 903.10a), and nothing resets that count. The commander designation follows the card through every zone change (rule 903.3), so the same card picks up where it left off.
Does noncombat damage from a commander count?
No. Rule 903.10a counts combat damage only. Anything a commander deals outside a combat damage step comes off your life total and nothing else.
Does trample damage count as commander damage?
Yes. The excess a trampler assigns to the player it is attacking is combat damage dealt by that creature (rule 702.19b), so it goes on the tally like any other combat damage.
Does a commander with double strike deal double commander damage?
Effectively yes, in the sense that it assigns combat damage in two separate combat damage steps in the same combat phase (rule 702.4b). Both lots are combat damage from the same commander, so both count.
Can you die to commander damage while at high life?
Yes, and that is the point of the rule. The commander damage condition (rule 903.10a) and the zero life condition (rule 104.3b) are two independent state based actions. A commander that connects three times for 7 has dealt 21 and wins, and if you gained life along the way you can be well above 19 when it happens.
Does a copy of a commander deal commander damage?
Not if the copy is a token. The commander designation belongs to the card, not to the object on the battlefield (rule 903.3), and a token is not represented by a card (rule 111.1).
Can your own commander deal commander damage to you?
Yes, if an opponent gains control of it and attacks you with it. Rule 903.10a counts combat damage dealt to you "by the same commander" and says nothing about who controls it, and the commander designation belongs to the card itself (rule 903.3), so your commander is still a commander under another player's control and its hits go on your tally like anyone else's. While you control it, it can't attack you, because the player you attack is always an opponent (rules 506.2 and 506.2a), so in ordinary play it deals you no combat damage; the exception is a redirection effect that sends its damage to you instead (rule 614.9).
What is commander damage in a two player game?
The same 21 from the same commander. Rule 903.2 says a Commander game may be a two player game or a multiplayer game, and the commander damage rule applies to Commander games. Only Brawl switches it off (rule 903.12h).
Does commander damage also come off your life total?
Yes, unless the commander has infect. Commander damage is ordinary combat damage, so you lose that much life as usual (120.3a), or get that many poison counters from an infect commander (120.3b), and the game keeps a separate count of it for the 21-damage rule either way (903.10a).
Does commander damage count as regular damage?
Yes. It is combat damage like any other, so lifelink and abilities that trigger on combat damage work as usual (702.15b); the only extra is the separate tally against 21 (903.10a).
Is it 20 or 21 commander damage?
- Rule 903.10a sets the threshold at 21 or more combat damage from the same commander; 20 is the starting life total of an ordinary game (119.1), while Commander starts you at 40 (903.7).
Build with the clock in mind
If you want to be the player on the fast clock, a commander with high power and evasion is the shortest route, and Blackblade Reforged plus a way through is the classic add. If you want to stop being on the receiving end, start with two cheap exile effects and one attack tax. The build order for the rest of the deck is in how to build a Commander deck, and the creature count that supports an attacking plan is in how many creatures a Commander deck needs. The rest of the format's rules, from the command zone to 40 starting life, are in how to play Commander, and the deck builder lets you try a list with no account.
Create a free Mana Grove account to build with the full deck builder, legality checks and deck statistics on every plan. For more on the format, start at the Commander hub, search every card by what it does, or browse every article.
Sources
- Comprehensive Rules, effective August 7, 2026, rules 104.3b, 104.3j, 111.1, 510.1b, 702.4b, 702.19b, 702.124a, 702.124b, 702.124d, 704.1, 704.2, 704.3, 704.6c, 903.2, 903.3, 903.7, 903.9a, 903.10, 903.10a, 903.12d, 903.12f and 903.12h: https://magic.wizards.com/en/rules. Read on September 16, 2026, from the snapshot our rules engine keeps. The quotation in "What the rule actually says" is rule 903.10a verbatim, and the definition of combat damage is the Comprehensive Rules glossary entry "Combat Damage" verbatim. The FAQ answer on your own commander, added on October 26, 2026, also cites rules 506.2 and 506.2a (attacking and defending players) and rule 614.9 (redirection effects), read that day in the edition effective September 25, 2026.
- Mana Grove card database, MTGJSON build 5.3.0+20260914 of September 14, 2026: the mana costs, power, toughness, rules text and Commander legality of every card named above.
This article is updated when the Comprehensive Rules change something it states. The date at the top is the last revision.
