MTG The Stack Explained: How Spells and Abilities Resolve (2026)

What the Stack Is (CR 405)

The stack is covered in section 405 of the Comprehensive Rules. The key rules:

CR 405.1: When a spell is cast, the physical card is put on the stack. When an ability is activated or triggers, it goes on top of the stack without any card associated with it.

CR 405.2: Each time an object is put on the stack, it's put on top of all objects already there.

CR 405.5: When all players pass in succession, the top (last-added) spell or ability on the stack resolves. If the stack is empty when all players pass, the current step or phase ends.

The stack is one of seven zones (CR 400.1), alongside the library, hand, battlefield, graveyard, exile and command zone. Spells exist on the stack between being cast and resolving. Abilities exist there between being activated or triggered and resolving. Permanents are on the battlefield, never on the stack.

How a Spell Moves Through the Stack

Here's the life of a single spell.

Step 1: Casting (CR 601.2). You move the card to the stack, choose modes and targets, work out the total cost and pay it. Casting is finished before anyone gets priority, so no one can respond halfway through.

Step 2: You get priority back. If you had priority when you cast the spell, you get priority again afterward (CR 117.3c and 601.2i). You can add something else to the stack or pass.

Step 3: Priority passing. When you pass, the next player in turn order gets priority (CR 117.3d). Each player can respond or pass. When all players pass in succession with the spell on top, it resolves (CR 117.4).

Step 4: Resolution. The spell's instructions are followed. An instant or sorcery goes to its owner's graveyard as the last part of resolving (CR 608.2n). A permanent spell enters the battlefield (CR 608.3).

Step 5: Priority again. After a spell or ability resolves, the active player gets priority (CR 117.3b). The loop repeats until the stack is empty and all players pass in succession. Then the step or phase ends.

Every interaction in Magic is a version of this loop. For when each priority window opens during a turn, see our Magic: The Gathering phases guide.

Priority: The Right to Act (CR 117)

Priority is what makes flash useful. It's the window in which you can actually cast an instant-speed spell.

The rules that govern it:

CR 117.1: Unless a spell or ability is instructing a player to act, which player can act is decided by priority. The player with priority may cast spells, activate abilities and take special actions.

CR 117.3a: The active player receives priority at the beginning of most steps and phases, after turn-based actions and "at the beginning of" triggers are dealt with. No player gets priority in the untap step, and usually not in the cleanup step.

CR 117.3b: The active player receives priority after a spell or ability (other than a mana ability) resolves.

CR 117.3c: If a player has priority when they cast a spell, activate an ability or take a special action, that player receives priority afterward.

CR 117.4: If all players pass in succession, the spell or ability on top of the stack resolves or, if the stack is empty, the phase or step ends.

So the active player gets the first chance to act at the start of each step and after each resolution, and whoever just put something on the stack gets the first chance to add more. Other players only get priority after the player before them passes.

Passing priority is not the same as ending your turn. You can pass priority many times in one turn. A step only ends when the stack is empty and all players pass in a row.

Last-In, First-Out: The Resolution Order

The stack resolves last-in, first-out. The spell or ability that went on most recently resolves first (CR 117.7 and 405.5).

An example:

1. You cast Lightning Bolt targeting your opponent's Tarmogoyf. Bolt goes on the stack.
2. Your opponent responds with Counterspell targeting Bolt. Counterspell goes on top.
3. You respond with Dispel ("Counter target instant spell") targeting Counterspell. Dispel goes on top.
4. All players pass. Dispel resolves and counters Counterspell, which goes to its owner's graveyard.
5. You get priority again, because you're the active player (CR 117.3b). Players can respond to Bolt again here. If everyone passes, Bolt resolves and deals 3 damage to Tarmogoyf.

Items resolve in the opposite order to how they went on. Between each resolution, players get priority again, so a stack of three spells gives everyone three separate chances to respond.

What Goes on the Stack, and What Doesn't

Not every game action uses the stack.

Goes on the stack:

• All spells: instants, sorceries, creatures, artifacts, enchantments, planeswalkers and battles. A modal double-faced card with a land back face uses the stack when you cast its spell face, but not when you play its land face.
• Activated abilities, except mana abilities
• Triggered abilities, except triggered mana abilities

Doesn't go on the stack (CR 405.6):

• Playing a land (a special action, CR 305.1 and 116.2a)
• Mana abilities (CR 605.3b: they resolve immediately)
• Static abilities (CR 405.6b)
• Effects themselves, including replacement effects (CR 405.6a)
• State-based actions (CR 704)
• Turn-based actions, like untapping in the untap step (CR 703)

This explains a lot of "why didn't my counterspell work?" moments. You can't counter a land drop, a mana ability or a replacement effect. If it isn't on the stack, Counterspell has nothing to target.

For how state-based actions fit in around the stack, see our MTG state-based actions guide.

Triggered Abilities and the Stack (CR 603)

Triggered abilities use the stack a little differently from spells and activated abilities.

CR 603.3: Once an ability has triggered, its controller puts it on the stack the next time a player would receive priority. It doesn't go on the stack the instant its trigger condition happens.

CR 603.3b: If several abilities have triggered since the last time a player received priority, each player, in APNAP order (active player first, then the others in turn order), puts the triggers they control on the stack in any order they choose.

What this means in play:

Triggers wait for the spell to finish resolving. Abilities can trigger in the middle of a resolving spell, but they wait until a player would get priority (CR 117.2a). If you control Soul Warden ("Whenever another creature enters, you gain 1 life") and a spell creates two creature tokens, Soul Warden triggers twice, and both triggers go on the stack after the spell has finished resolving.

You choose the order of your own triggers. If three of your "when this creature enters, draw a card" creatures enter at the same time, you put the three triggers on the stack in any order. Because the stack is last-in, first-out, that order decides which resolves first.

Triggers can be countered, but only by the right cards. Stifle counters target activated or triggered ability. Disallow, first printed in Aether Revolt, counters target spell, activated ability or triggered ability. Counterspell only counters spells.

Removing the source doesn't stop a trigger. Once an ability is on the stack, it exists independently of its source (CR 113.7a). Destroying the creature won't stop its trigger from resolving.

For a keyword that changes what happens when creatures attack, see our MTG vigilance guide.

Mana Abilities: The Big Exception (CR 605)

Mana abilities are the main exception to the stack.

CR 605.1a: An activated ability is a mana ability if it meets all of these criteria: it doesn't require a target, it could add mana to a player's mana pool when it resolves, it's not a loyalty ability, and its cost and effect don't move any card to or from a library.

CR 605.3b: An activated mana ability doesn't go on the stack, so it can't be targeted, countered or otherwise responded to. It resolves immediately after it's activated.

So there's no window between tapping a land and getting the mana. Stifle can't counter a mana ability.

Examples:

• Birds of Paradise ("{T}: Add one mana of any color."): a mana ability, no stack.
• Cabal Coffers ("{2}, {T}: Add {B} for each Swamp you control."): a mana ability, no stack.
• Misty Rainforest: not a mana ability. It searches your library and doesn't add mana, so it uses the stack and can be responded to, for example with Stifle.
• Mana Drain: a spell, not a mana ability. It counters target spell, and at the beginning of your next main phase it adds colorless mana equal to that spell's mana value. A spell is never a mana ability (CR 605.5b).

If mana abilities used the stack, every land tap could be answered, and paying for spells would take far longer.

Holding Priority

"Holding priority" means casting a spell or activating an ability and then taking another action before anyone else can respond.

The rule. After you cast a spell or activate an ability, you get priority again (CR 117.3c). If you use it to add something else, the new object goes on top, and your opponent never gets a window between your two actions.

Common uses:

• Responding to your own spell. You can respond to your own spells like anyone else's. You could even counter your own spell if you wanted to.
• Stacking two spells at once. Cast a burn spell, hold priority and cast a second one, so both are on the stack before your opponent can respond to the first.
• Getting value before a sacrifice. Activate an ability of a creature, hold priority, then sacrifice that creature to a sacrifice outlet. The first ability is already on the stack and still resolves (CR 113.7a).

At tournaments, say it out loud. Under the Magic Tournament Rules (section 4.2), whenever a player adds an object to the stack, they're assumed to be passing priority unless they explicitly announce they're keeping it. Say "holding priority" before your second action.

Common Stack Misconceptions

Misconception 1: "I can respond to my opponent playing a land." You can't. Playing a land is a special action. It doesn't use the stack, so there's nothing to respond to (CR 305.1). You can respond to abilities that trigger when the land enters.

Misconception 2: "Counterspell can counter triggered abilities." False. Counterspell says "Counter target spell." To counter a triggered ability you need a card like Stifle, Trickbind or Disallow.

Misconception 3: "I can't respond to my own spell." You can. You get priority first after you cast it (CR 117.3c), and you can cast instants, activate abilities, or even counter your own spell. What you can't do is change its targets after it's cast, unless an effect lets you.

Misconception 4: "If my opponent passes, my spell resolves." Only if every player has passed in succession (CR 117.4). If you cast something and pass, and your opponent passes, it resolves. If your opponent responds instead, all players have to pass in a row again before the top item resolves.

Strategic Implications

Knowing the stack well changes how you play in three ways.

Using your opponent's turn. When your opponent casts a removal spell on your creature, you get priority before it resolves. That's your chance to use the creature's activated abilities, or cast instants, while it's still on the battlefield.

Combo timing. Combo decks depend on what goes on the stack and when. Storm decks cast many cheap spells first so the storm trigger makes more copies (CR 702.40a). Cascade decks cast a spell from the cascade trigger while that trigger resolves (CR 702.85a).

Knowing what your answers hit. Stifle and Trickbind only hit activated and triggered abilities. Counterspell only hits spells. Knowing what uses the stack tells you what each answer can and can't stop.

For how stack-related keywords appear in card text, see our ultimate MTG keywords glossary.

Format-Specific Stack Considerations

Standard. As of October 2026, counterspells like Three Steps Ahead are legal in Standard. Stacks are usually short, but combat tricks and triggers still create plenty of "in response" moments.

Pioneer. Make Disappear and Disallow are both Pioneer-legal, so counter wars over key spells come up.

Modern. Cascade decks play Living End and Crashing Footfalls, which they cast from cascade triggers. Players need to track several objects on the stack at once.

Commander. With four players, priority passes around the whole table in turn order, and triggers from several players go on the stack in APNAP order. Keeping track of the stack is one of the hardest parts of a busy Commander game.

Legacy and Vintage. Cheap spells, free counterspells and fast combo decks make long stacks more common here than anywhere else.

The Bottom Line

The stack is how Magic handles interaction. Spells, activated abilities and triggered abilities all pass through it. Three rules cover most situations: items resolve last-in, first-out; all players must pass in succession before anything resolves; and land drops, mana abilities, state-based actions and turn-based actions skip the stack entirely.

Read the stack from the top down. Track who has priority. Know what uses the stack and what doesn't.