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

What the Stack Is (CR 405)

The Comprehensive Rules dedicate an entire section, CR 405, to the stack. The opening rule is simple:

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 with no physical representation.

CR 405.4: Each spell or ability resolves separately. When the spell or ability on top of the stack resolves, it's removed from the stack and follows the instructions in its rules text or effect.

CR 405.5: Whenever 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.

The stack is one of seven game zones — alongside the battlefield, library, hand, graveyard, exile, and command zone. Spells exist on the stack between when they're cast and when they resolve. Abilities exist on the stack between when they're activated or triggered and when they resolve. Permanents do not exist on the stack — only spells and abilities do.

How a Spell Moves Through the Stack

Walking through the lifecycle of a single spell illustrates the stack's mechanics.

Step 1: Casting (CR 601.2). You announce the spell, move it from your hand to the stack, choose modes and targets, determine total cost, and pay the cost. The casting is a single, indivisible action — you cannot respond to a spell being cast, only to a spell that has been cast and is now on the stack.

Step 2: On the stack. The spell exists on the stack. The active player receives priority. Both players have the opportunity to respond. Any response goes on top of the original spell.

Step 3: Priority passing. The active player either takes a game action (casting another spell, activating an ability) or passes priority. The non-active player then has the same options. When both players pass priority in succession with the stack non-empty, the topmost spell or ability resolves.

Step 4: Resolution. The spell's effect happens. The card moves from the stack to its appropriate destination — the battlefield (for permanents), the graveyard (for instants and sorceries), or another zone if the spell says so.

Step 5: Priority resets. After resolution, the active player receives priority again. The process repeats until the stack is empty and all players pass in succession, at which point the game moves to the next step or phase.

Mastering this lifecycle is the foundation. Every interaction in Magic is a variant of this core loop. For a deeper look at when each priority window opens within a turn, see our Magic: The Gathering phases guide.

Priority: The Right to Act (CR 117)

The stack only works because priority passes between players in a strictly defined order. CR 117 governs priority:

CR 117.1: Unless a spell or ability is instructing a player to take an action, that player needs priority to take any actions. Priority is given to the active player first at the beginning of most steps and phases.

CR 117.3a: The active player receives priority at the beginning of most steps and phases, after a spell or ability (other than a mana ability) resolves, and at certain other times.

CR 117.3b: A player who has priority may cast a spell, activate an ability, or take a special action.

CR 117.4: If all players pass in succession (each in turn passes without taking an action), the spell or ability on the top of the stack resolves or, if the stack is empty, the phase or step ends.

The crucial rule: the active player always receives priority first at the start of each step and phase, and after each spell or ability resolves. The non-active player only gets priority after the active player passes. This is why decisions about whether to act often happen on the active player's turn — they have first option.

A common newer-player misunderstanding: passing priority is not the same as ending the turn. You can pass priority a hundred times in a single turn, going through hundreds of separate spell-and-response chains, without the turn ending until all priority passes resolve to "stack empty, both players pass in succession."

Last-In, First-Out: The Resolution Order

The single most important property of the stack is its resolution order: last-in, first-out (LIFO). The spell or ability that goes onto the stack most recently resolves first. This produces the "stacking" pattern that gives the mechanic its name.

Consider this canonical example:

1. You cast Lightning Bolt targeting your opponent's Tarmogoyf. Bolt goes on the stack.
2. Your opponent responds with Counterspell targeting your Bolt. Counterspell goes on top of Bolt.
3. You respond with Dispel targeting their Counterspell. Dispel goes on top of Counterspell.
4. Both players pass priority.
5. Dispel resolves first — it counters Counterspell.
6. Counterspell is now on top of the stack but has no legal target (it tried to counter Bolt, which is still on the stack). Wait — that's wrong. Let me re-read the example.

Actually, let me correct that. After Dispel resolves, Counterspell is removed from the stack because it was countered. Then Bolt resolves and deals 3 damage to the Tarmogoyf. The stack is empty.

The key takeaway: each item on the stack resolves in the opposite order it was placed. The last spell cast resolves first.

What Goes on the Stack — and What Doesn't

Not every game action uses the stack. Knowing the difference is essential for advanced play.

Goes on the stack:

• All spells (instants, sorceries, creatures, enchantments, artifacts, planeswalkers, lands with kicker like Modal Double-Faced cards as spells)
• Activated abilities (except mana abilities)
• Triggered abilities

Does NOT go on the stack:

• Playing a land (CR 305.1, special action)
• Mana abilities (CR 605, resolve immediately)
• Static abilities (CR 604, never resolve, just exist)
• Replacement effects (modify events, don't use the stack)
• State-based actions (CR 704, automatic, don't use the stack)
• Turn-based actions like the untap step's untap (CR 703, automatic)

This distinction explains many "but why didn't my counterspell work?" moments. You cannot counter a land being played. You cannot counter a mana ability. You cannot counter a replacement effect. If it doesn't go on the stack, Counterspell does nothing.

For a complete map of when state-based actions trigger relative to the stack, see our MTG state-based actions guide.

Triggered Abilities and the Stack (CR 603)

Triggered abilities deserve their own treatment because they use the stack differently from spells and activated abilities.

CR 603.2: Whenever a triggered ability triggers, its controller puts it on the stack the next time a player would receive priority. It doesn't go on the stack instantly when its trigger condition is met.

CR 603.3b: If multiple abilities have triggered since the last time a player received priority, the active player puts their triggers on the stack in any order they choose, then each non-active player in turn order does the same.

This produces a few non-intuitive behaviors:

Triggered abilities don't interrupt resolution. A spell resolves fully before any triggered abilities created during resolution are placed on the stack. So if your Soul Warden triggers off a creature entering, and you cast a creature that creates two more creatures via a separate effect, all three triggers wait until after the spell fully resolves.

The active player chooses the order of their triggers. If you control three creatures with "When this creature enters, draw a card," you can put them on the stack in any order. Since the stack is LIFO, this lets you control the resolution sequence.

Triggered abilities can be countered by the right effects. Cards like Stifle counter triggered abilities. Disallow (a 2024 reprint, originally from Aether Revolt) counters spells, activated abilities, or triggered abilities. Counterspells specifically targeting "spells" do not work on triggered abilities.

For a deeper look at how triggered abilities interact with combat, see our MTG vigilance guide, which dissects the priority windows during the declare attackers and declare blockers steps.

Mana Abilities: The One Exception (CR 605)

Mana abilities are the single most important exception to the stack. CR 605 lays out the rules:

CR 605.1a: An activated ability is a mana ability if it has the following three properties: it doesn't have a target, it could put mana into a player's mana pool when it resolves, and it's not a loyalty ability.

CR 605.3: Mana abilities don't use the stack. Activating a mana ability puts the mana into the activating player's mana pool immediately.

This is why tapping a basic land for mana cannot be responded to. There is no priority window between the tap and the mana being added — the entire action resolves instantly. Stifle cannot counter a mana ability. Counterspell cannot counter the activation of a mana ability.

Mana ability gotchas:

• Cabal Coffers tapping for mana = mana ability (no stack)
• Dryad Arbor coming into play does not use the stack (it's a land)
• Birds of Paradise tapping for mana = mana ability (no stack)
• Mana Drain itself is a counterspell that adds mana — it goes on the stack like a normal spell because the casting is the spell, not the mana production

The mana ability rule is what makes ramp viable. If mana abilities used the stack, opponents could respond to every mana production by destroying lands.

Holding Priority: Advanced Stack Manipulation

"Holding priority" is the technique of casting a spell or activating an ability and then immediately taking another action without giving your opponent a chance to respond between them.

The rules of priority retention. After you cast a spell or activate an ability, you keep priority. You can choose to either pass it or take another action. If you take another action, that new spell or ability goes on top of the previous one. Your opponent never gets a chance to respond between your two actions.

Common applications:

• Fetchland sequencing. Crack Misty Rainforest in response to your own creature's enters-the-battlefield trigger, ensuring the trigger sees the new land. Useful for Knight of the Reliquary-style cards.
• Sorcery + instant chains. Cast a creature, hold priority, activate the creature's ability before opponents can respond. (This often doesn't work because activated abilities require the creature to be on the battlefield, which means the spell has to resolve first — but it works for triggered abilities.)
• Damage trigger optimization. Cast a damage spell, hold priority, sacrifice the source to a sac outlet so its trigger is on the stack before the damage even resolves.

To hold priority verbally at a competitive event, say "I'm holding priority" or "I have priority" before taking the second action. Judges expect this announcement; without it, opponents can claim you passed priority implicitly.

Common Stack Misconceptions

After thousands of judge calls, these are the four mistakes I see most often.

Misconception 1: "I can respond to my opponent playing a land." You cannot. Land plays are special actions, not spells, and they don't use the stack. There is no response window because there is no stack item.

Misconception 2: "Counterspell can counter triggered abilities." Generally false. Counterspell counters target spells. To counter a triggered ability, you need cards like Stifle, Trickbind, or Disallow.

Misconception 3: "I can respond to my own spell to interact with its effect." You can respond to your own spell to add more spells on top of it, but you cannot, for example, cast Counterspell on your own spell to remove an unwanted target you chose. Once targets are chosen, they're locked in (with rare exceptions for legal target re-selection on resolution).

Misconception 4: "If my opponent passes priority, the spell resolves immediately." False. The spell resolves only when all players pass in succession. You still need to pass priority too. Until both (or all) players pass, the spell sits on the stack.

Strategic Implications

Mastering the stack changes your game in three measurable ways.

Decision quality during opponent's turn. When your opponent casts a removal spell at end of turn, you have a priority window before the spell resolves. Use that window to crack fetchlands, activate creatures, or cast instants of your own — actions that the resolution of their spell would prevent.

Combo execution timing. Combo decks live and die on stack ordering. Storm players intentionally build their stack to maximize Storm count; cascade decks chain off the resolution order. A clean understanding of priority and stack order is the difference between executing a combo and fizzling.

Sideboard interaction. Cards like Stifle, Trickbind, and Pyroblast only work because the stack exists. Knowing what types of effects use the stack and which do not tells you exactly what your sideboard hate accomplishes against each archetype.

For a complete reference on how stack-based interactions appear in card text, see our ultimate MTG keywords glossary.

Format-Specific Stack Considerations

Standard. Most relevant counterspells in Standard are tempo plays (Make Disappear, Three Steps Ahead). Stack interactions are less complex because activated abilities are rare on cheap creatures.

Pioneer / Modern. Stack complexity increases with cards like Cascade triggers (Living End, Crashing Footfalls), Storm mechanics, and tutoring chains. Players need to track multiple objects on the stack at once.

Commander. The 4-player stack is dramatically more complex. Multiple triggered abilities from different players must be ordered, and turn-based priority cycles through three opponents. Stack management is one of the highest-skill aspects of competitive Commander.

Legacy / Vintage. The fastest stacks in Magic. Combo decks pile dozens of spells deep, and counterspell wars can hit 6+ items high. Mastery of stack order is non-negotiable in these formats.

The Bottom Line

The stack is Magic's central interaction mechanism. Every spell, every activated ability, every triggered ability passes through it. Mastering its three core rules — items resolve in last-in-first-out order, all players must pass priority for resolution to occur, and mana abilities skip the stack entirely — unlocks the entire interactive layer of Magic: The Gathering.

Read the stack from the top down. Track priority carefully. Know what uses the stack and what doesn't. The difference between a casual player and a competitive one isn't deck choice or card knowledge — it's stack literacy.