State-Based Actions in Magic: Rules Explained

When Do State-Based Actions Run?

State-based actions are checked whenever a player would receive priority (rule 704.3), including after a spell or ability resolves and after turn-based actions at the start of many steps and phases. They are not checked in the middle of a spell or ability resolving. The game repeats the check until no state-based action applies, then puts waiting triggers on the stack before a player receives priority.

Because SBAs don't use the stack, you cannot respond to them. You can't say "in response to my creature dying from lethal damage." The creature dies as a state-based action check; by the time either player gets priority to respond to anything, the creature is already in the graveyard. This is the fundamental reason why damage and toughness reduction feel immediate.

The Most Important State-Based Actions

A creature with toughness 0 or less is put into its owner's graveyard (rule 704.5f). This is why reducing a creature's toughness to 0 with -X/-X effects kills it — the game sees a creature with 0 toughness and removes it. No "destroy" is involved, which means indestructible doesn't save it.

A creature with lethal damage marked on it is destroyed (rule 704.5g). Lethal damage is damage equal to or greater than the creature's toughness. Indestructible creatures can have damage marked on them but won't be destroyed by this SBA. Damage is cleared from all permanents at the end of each turn, so damage doesn't carry over between turns (unless a card specifically says otherwise).

A player who has 0 or less life loses the game (rule 704.5a). A player who is required to draw a card when their library is empty loses as a state-based action at that moment — not when the library first becomes empty, but at the point the draw would occur (rule 704.5b). Running out of cards does not by itself end the game; the loss happens only when a draw is attempted from an empty library.

SBAs and Tokens, Copies, and +1/+1 Counters

Tokens that leave the battlefield cease to exist as a state-based action. A token creature that goes to the graveyard is removed from the game — it exists briefly in the graveyard long enough for abilities that trigger on creatures dying to see it, but immediately ceases to exist afterward. This is relevant for Tombstone Stairwell, Reassembling Skeleton's interaction with tokens, and similar niche cases.

+1/+1 counters and -1/-1 counters on the same permanent are removed in pairs as a state-based action (rule 704.5r). A creature with two +1/+1 counters and two -1/-1 counters will have both sets removed, ending up with no counters at all. This can change whether an effect "sees" those counters.

A legendary permanent being controlled by the same player as another legendary permanent with the same name causes the player to choose one to keep and put the rest in the graveyard (rule 704.5j). This is the "legend rule" in action — it's an SBA, not a triggered ability, so it happens automatically and simultaneously with other SBAs.

SBAs and the Stack

Triggered abilities that trigger from SBAs — like "when a creature dies" triggering from a creature dying to lethal damage — don't trigger until the SBA actually applies. Since SBAs run before priority is received, both the SBA and any triggered abilities that result from it are handled before either player gets to act.

Multiple state-based actions are checked simultaneously. If a spell reduces all creatures to 0 toughness, all those creatures die at the same time — not one after another. This matters because a player might control a creature that triggers from other creatures dying, but that triggering creature is also dying. It can still see the other deaths before it goes to the graveyard.

The takeaway for practical play: when something bad happens (a creature dying, a player losing life), ask yourself whether it happened from a spell or ability on the stack, or from a state-based action. If it's an SBA, you couldn't have responded to it. If it was from a spell or ability, there was a window before it resolved when you could have acted.

Source and verification

This explanation is based on the Magic: The Gathering Comprehensive Rules sections cited in the article. Card-specific Oracle text and rulings should be checked against an official card database. At a sanctioned event, ask the event judge for the ruling that applies to the current game.

Related guides

• The Combat Phase, Step by Step

  A complete walkthrough of Magic's combat phase — every step, every priority window, and the rules that govern what actually happens when creatures fight.

• Legend Rule, Tokens & Copies Explained

  Learn how the legend rule, tokens, and copy effects work in Magic: The Gathering, including what happens when you control two legendary permanents in play.

• Common Magic Rules Mistakes Explained

  Avoid ten common Magic: The Gathering rules mistakes with clear explanations and the actual rule behind each one, from combat to card interactions at the table.