How the MTG Stack Works: A Beginner’s Guide to Magic’s Most Important Rule
You are three turns into your first game at Friday Night Magic. You tap out, slam your best creature on the table, and lean back — satisfied. Your opponent raises a finger. “In response…” they say, and suddenly your creature is dead before it ever got to attack. You stare at the board, trying to figure out what just happened.
What happened was the stack — and it is the single most important rule in Magic: The Gathering that nobody explains clearly enough to new players.
The stack governs how spells and abilities resolve in Magic. It determines who gets to respond to what, in which order things happen, and why “in response” are the two most powerful words in the game. Once you understand the stack, you stop being the player whose creatures keep dying and start being the player who says “in response” with a grin.
This guide will walk you through everything: what the stack is, how it works, and how to use it to win games. We will use real card examples, visual diagrams, and plain language. No law degree required.
Table of Contents
What Is the Stack?
Imagine a cafeteria tray dispenser — the kind where trays are stacked on top of each other, and you always take from the top. When someone adds a tray, it goes on top. When someone takes a tray, it comes off the top. The last tray placed on the stack is always the first one removed.
That is exactly how Magic’s stack works. When you cast a spell, it goes on the stack. When your opponent responds with their own spell, theirs goes on top of yours. When it is time for things to resolve, the game starts from the top and works down. Your opponent’s spell resolves first because it was added last.
Quick Definition: The stack is a game zone in Magic: The Gathering where spells and abilities wait to resolve. It is not a physical pile of cards on the table — it is a conceptual space that determines the order in which things happen. Think of it as a queue where the most recent addition gets processed first.
The stack exists because Magic is fundamentally a game of interaction. Without it, you would cast a spell and it would just happen — no counterplay, no bluffing, no drama. The stack is what makes Magic feel like a conversation between two players rather than two people playing solitaire side by side. It creates the moments where you hold up mana, bluff having an answer, and punish opponents for tapping out at the wrong time.
Every spell you cast (creatures, instants, sorceries, enchantments, artifacts, planeswalkers, battles) goes on the stack. Most activated abilities go on the stack. Triggered abilities go on the stack. The stack is where the game’s most meaningful decisions happen.
Why the Stack Matters
Understanding the stack is not some niche rules trivia that only judges care about. It directly determines whether you win or lose games. Here is why:
Combat tricks work because of the stack. When your opponent declares blockers, you can cast Surge of Salvation to give your creatures protection from the colors of their blockers — and because your spell goes on the stack after blockers are declared, the block is already locked in. Your creatures survive. Theirs don’t.
Counterspells exist because of the stack. A counterspell like Make Disappear does not prevent your opponent from casting a spell — it removes that spell from the stack before it resolves. The timing matters: you can only counter something while it is sitting on the stack, waiting to resolve.
Removal timing wins games because of the stack. Your opponent casts All That Glitters targeting their creature. If you wait for it to resolve, that creature could become enormous. But if you cast Go for the Throat on the creature while the Aura is still on the stack, the creature dies, the Aura has no legal target, and it goes to the graveyard without ever doing anything. You just two-for-one’d them using stack knowledge.
Triggered abilities can be responded to. Your opponent’s Scute Swarm triggers when a land enters the battlefield. That trigger goes on the stack — and before it resolves, you can remove the Scute Swarm with instant-speed removal. The trigger still resolves (it is already on the stack, independent of its source), but understanding when and how to interact with triggers is the difference between losing to an army of insects and keeping the board under control.
How Spells and Abilities Go On the Stack
Casting a Spell
When you cast a spell, it follows a specific sequence. Understanding this sequence helps you see exactly when opponents can (and cannot) interact:
- Announce the spell. Move the card from your hand to the stack. Choose targets, modes, and any other decisions the card asks for (like how much mana to pay for X spells).
- Pay costs. Tap your lands, pay life, sacrifice creatures — whatever the card requires. Once costs are paid, the spell is officially on the stack. You cannot be “interrupted” during this step.
- The spell sits on the stack. It does not resolve yet. It just waits there.
- Priority passes. Both players get a chance to respond. If neither player does anything, the spell resolves. If someone does respond, their response goes on top of the stack, and the cycle repeats.
The key takeaway: there is a gap between when you cast a spell and when it actually does its thing. That gap is where all the interesting decisions in Magic happen.
Triggered Abilities
Triggered abilities are identified by the words “when,” “whenever,” or “at.” They go on the stack automatically when their trigger condition is met.
When Mondrak, Glory Dominus is on the battlefield and you create a token, Mondrak’s replacement effect doubles it — but that is actually a replacement effect, not a triggered ability. Let’s use a cleaner example: Storm-Kiln Artist says “Whenever you cast or copy an instant or sorcery spell, create a Treasure token.” Every time you cast an eligible spell, that trigger goes on the stack on top of whatever you just cast.
Important rule: triggered abilities exist independently of their source once they are on the stack. If your opponent kills Storm-Kiln Artist in response to the trigger, you still get your Treasure token. The ability is already on the stack — removing the creature that created it does not undo it.
Activated Abilities
Activated abilities are written in the format “[Cost]: [Effect]” — there is always a colon separating what you pay from what you get. Most activated abilities use the stack, just like spells.
Quick Tip: The easiest way to identify an activated ability on any card is to look for the colon (:). If a card’s text has a colon separating a cost from an effect, it is an activated ability. “{T}: Add one mana of any color” and “{2}, Sacrifice this creature: Draw a card” are both activated abilities. Tap the permanent or pay the cost, and the ability goes on the stack.
Just like triggered abilities, activated abilities are independent of their source once on the stack. If you activate an ability and your opponent destroys the source in response, the ability still resolves.
Last In, First Out (LIFO)
The LIFO Principle
LIFO stands for Last In, First Out. It is the core rule that governs how the stack resolves. The last thing added to the stack is always the first thing to resolve.
This might feel backwards at first, but it makes perfect sense once you think about it. If your opponent casts a creature and you respond with a counterspell, your counterspell needs to resolve before their creature does — otherwise, how would countering work? LIFO ensures that responses always resolve before the things they are responding to.
Think of it like a conversation. Someone makes a statement (casts a spell). You interrupt them (cast in response). Your interruption is addressed first. Then the original statement resolves — or doesn’t, if your interruption changed things.
Walk-Through 1: Lightning Bolt vs. Counterspell
You cast Lightning Bolt targeting your opponent’s face for 3 damage. Your opponent casts Spell Pierce, paying one mana to counter your spell unless you pay two. You don’t have two mana open.
Here is what the stack looks like before anything resolves:
🔽 THE STACK (resolves top → bottom)
TOP (resolves first) → Spell Pierce (targeting Lightning Bolt)
BOTTOM → Lightning Bolt (targeting opponent)
Resolution: Spell Pierce resolves first. You can’t pay the two mana, so Lightning Bolt is countered and goes to the graveyard. The stack is now empty. Your 3 damage never happens.
Walk-Through 2: Combat Trick vs. Removal
Your 3/3 creature attacks. Your opponent blocks with their 3/3. Before damage, you cast Unleash Fury to double your creature’s power to 6. In response, your opponent casts Go for the Throat targeting your creature.
🔽 THE STACK (resolves top → bottom)
TOP (resolves first) → Go for the Throat (targeting your 3/3)
BOTTOM → Unleash Fury (targeting your 3/3)
Resolution: Go for the Throat resolves first, destroying your creature. Then Unleash Fury tries to resolve, but its target is gone. It fizzles — the game removes it from the stack because it has no legal target. Your opponent traded their removal spell for your combat trick and your creature. You got blown out because of the stack.
The lesson: casting a combat trick before your opponent has a chance to respond with removal can put you in a worse spot than just letting combat happen normally. Stack awareness is not just about knowing the rules — it is about making smarter decisions.
Priority — Who Gets to Respond
What Is Priority?
Priority is the game’s way of determining who gets to act at any given moment. Think of it as a “permission slip” to cast spells or activate abilities. Only the player who holds priority can add something to the stack.
The active player (the player whose turn it is) always receives priority first at the beginning of each step and phase. After they cast a spell or activate an ability, priority passes to the opponent. After the opponent acts or passes, priority goes back to the active player.
How Priority Works
Here is the priority cycle, step by step:
- The active player gets priority.
- They can cast a spell, activate an ability, or pass priority.
- If they act, their spell/ability goes on the stack, and they get priority again (they can respond to their own spell if they want).
- When they pass priority, the opponent gets priority.
- The opponent can act or pass.
- Only when both players pass priority in succession does the top item on the stack resolve.
- After an item resolves, the active player gets priority again.
- Steps 1-7 repeat until the stack is empty and both players pass on an empty stack, which moves the game to the next step or phase.
This means nothing ever resolves “automatically.” Even if your opponent says “I cast this” and reaches for their graveyard, you always have the right to say “hold on, I want to respond.” In tournament play, this is a formal process. In casual games, players often shortcut by assuming no response — but the option is always there.
Common Priority Mistakes
Important: Spells and abilities do not resolve the instant they are cast. There is always a window for responses. New players often treat spells as if they resolve immediately — “I cast Sunfall, your creatures are dead.” But your opponent has priority after you cast Sunfall. They can respond with an instant like Surge of Salvation to give their creatures indestructible. Then Sunfall resolves — and their creatures survive.
Another common mistake: trying to respond to something that has already resolved. If your opponent casts a creature and you say “okay” (passing priority), that creature resolves. You cannot then say “wait, I want to counter it.” Once both players pass, the top item resolves immediately. If you wanted to counter it, you needed to do it before you passed.
In multiplayer formats like Commander, priority passes around the table in turn order starting from the active player. This means every player gets a chance to respond to every spell, which is part of why multiplayer games can have such dramatic stack interactions.
Real Game Walk-Throughs
Let’s look at some real scenarios that come up in actual games. These are the situations where stack knowledge separates experienced players from beginners.
Counterspell Response Chain
You cast Sunfall, a powerful five-mana board wipe. Your opponent casts Make Disappear, paying one mana to counter your Sunfall unless you pay two. You don’t want to pay, so instead you cast An Offer You Can’t Refuse — a one-mana counterspell that counters their Make Disappear (giving them two Treasure tokens, but saving your board wipe).
🔽 THE STACK (resolves top → bottom)
TOP (resolves 1st) → An Offer You Can’t Refuse (targeting Make Disappear)
MIDDLE → Make Disappear (targeting Sunfall)
BOTTOM (resolves last) → Sunfall
Resolution:
- An Offer You Can’t Refuse resolves. Make Disappear is countered and goes to the graveyard. Your opponent gets two Treasure tokens.
- Make Disappear is gone — it was removed from the stack by the counterspell.
- Sunfall resolves. All creatures are exiled. You get an Incubator token with counters equal to the total power of exiled creatures.
You spent one extra mana and gave your opponent two Treasures, but you resolved a game-changing board wipe. That’s a winning trade.
Removal in Response to an Aura (Fizzling)
Your opponent casts All That Glitters targeting their creature. All That Glitters is an Aura that gives a creature +1/+1 for each artifact and enchantment you control — it can make something enormous. But it is still on the stack. In response, you cast Go for the Throat targeting that creature.
🔽 THE STACK (resolves top → bottom)
TOP (resolves first) → Go for the Throat (targeting their creature)
BOTTOM → All That Glitters (targeting their creature)
Resolution: Go for the Throat resolves, destroying the creature. All That Glitters tries to resolve, but its target no longer exists. The Aura fizzles — it goes to the graveyard without ever entering the battlefield. Your opponent just lost two cards (a creature and an Aura) to your single removal spell. That is a brutal two-for-one, and it only happened because you understood when to fire your removal.
The wrong play would have been waiting until All That Glitters resolved and then trying to kill the creature. By then, the creature would already have the Aura’s power boost — and if they had other artifacts and enchantments, it might be too big to deal with efficiently.
Multiple Triggered Abilities (APNAP Order)
In multiplayer games, multiple players might have abilities that trigger at the same time. Magic handles this with the APNAP rule: Active Player, Non-Active Player.
The active player (whose turn it is) puts their triggered abilities on the stack first, in any order they choose. Then, going around the table in turn order, each non-active player adds their triggered abilities. Since the last abilities added resolve first (LIFO), the non-active players’ triggers resolve before the active player’s.
APNAP Made Simple: If it is your turn and both you and an opponent have abilities that trigger at the same time, your opponent’s triggers resolve first. This matters in situations like simultaneous death triggers, beginning-of-upkeep effects, and “at the beginning of combat” abilities. When in doubt, remember: the active player’s stuff is always at the bottom of the stack.
Things That DON’T Use the Stack
Not everything in Magic uses the stack. Knowing what doesn’t use the stack is just as important as knowing what does, because you cannot respond to these actions.
Mana Abilities
Tapping a land for mana does not use the stack. Neither do mana abilities on permanents like Llanowar Elves (“{T}: Add {G}”). These resolve instantly and cannot be responded to. Your opponent cannot destroy your Llanowar Elves “in response” to you tapping it for mana — by the time they could respond, you already have the mana.
Static Abilities
Abilities that are always “on” — like “Creatures you control get +1/+1” — never go on the stack. They just exist as long as the permanent is on the battlefield. There is no point where a static ability is “resolving” that you could respond to.
Special Actions
Playing a land is a special action that does not use the stack. You cannot counter someone playing a land. Turning a face-down creature face-up (morph/manifest) is also a special action that does not use the stack — the creature flips instantly.
Replacement Effects
Effects that say “instead” or “as” — like Mondrak, Glory Dominus doubling tokens or a card entering the battlefield tapped — modify events as they happen rather than going on the stack separately. You cannot respond to a replacement effect because it modifies the original event rather than creating a new one.
Quick Test: If you are unsure whether something uses the stack, ask yourself: “Can my opponent say ‘in response’ to this?” If the answer is no — it is a mana ability, a static ability, a special action, or a replacement effect — then it does not use the stack. If the answer is yes, it does.
Common Stack Mistakes Beginners Make
Even after you understand how the stack works in theory, these are the mistakes that trip up newer players in actual games:
- Treating spells as instant-effect. You cast a creature and immediately start using its abilities. But your opponent had priority and could have countered it. Always give opponents a chance to respond — and if you are the opponent, speak up before things resolve.
- Destroying a source to stop an ability. “I’ll kill your creature in response to its triggered ability!” Great — the creature dies. But the ability is already on the stack and still resolves. Removing the source of a triggered or activated ability does not remove that ability from the stack.
- Casting combat tricks too early. Casting Unleash Fury before your opponent has declared blockers gives them information and a chance to respond. Wait until blockers are declared, then pump. Better yet, wait until after they have used their own combat tricks.
- Not holding up mana for responses. Tapping out on your turn means you cannot respond to anything during your opponent’s turn. Even if you don’t have an instant in hand, representing open mana forces your opponent to play around the possibility.
- Scooping too early on the stack. Your opponent aims a lethal Lightning Bolt at your face. You concede before it resolves. In most casual games, this is fine. But in some situations (like when your opponent’s spell has other effects that require it to resolve, or when death triggers matter), scooping with spells on the stack can matter.
- Forgetting that the stack resolves one item at a time. After each item resolves, both players get priority again before the next item resolves. You can add new things to the stack between resolutions. This creates opportunities for complex multi-step plays that beginners often miss.
Rules Change Alert: Before 2010, combat damage used the stack. This meant you could assign lethal damage, then sacrifice your creature for value before the damage resolved. That rule was removed with the Magic 2010 rules update. Today, combat damage happens instantly and does not use the stack. If someone tells you to put damage on the stack and then sacrifice your creature, they are remembering a rule that hasn’t existed for over fifteen years.
Frequently Asked Questions
Can I respond to a land being played?
No. Playing a land is a special action that does not use the stack. However, if playing a land triggers an ability (like landfall on Scute Swarm), that triggered ability does go on the stack and can be responded to.
If I kill a creature, do its triggered abilities still resolve?
Yes. Once a triggered ability is on the stack, it exists independently of its source. Destroying, exiling, or bouncing the permanent that created the trigger does not remove the trigger from the stack. The ability will still resolve.
Can I counter an activated ability?
Most counterspells only counter spells, not abilities. A regular Make Disappear cannot counter an activated ability. However, a few specific cards like Stifle and Disallow can counter triggered and activated abilities. These are relatively rare effects.
What happens if a spell’s target becomes illegal?
If a spell or ability has a single target and that target becomes illegal before it resolves (because it left the battlefield, gained protection, etc.), the spell or ability fizzles — it is removed from the stack without resolving. If a spell has multiple targets and only some become illegal, it still resolves against the remaining legal targets.
Can I respond to my own spells?
Yes. After you cast a spell, you retain priority before passing it. You can cast another spell or activate an ability on top of your own. This is how you can cast a creature and then immediately cast a spell to protect it before your opponent gets priority (though you must have an instant or flash card to do this).
Does a creature’s enter-the-battlefield ability go on the stack?
Yes. Enter-the-battlefield (ETB) abilities are triggered abilities. The creature enters the battlefield as the creature spell resolves, and then the ETB trigger goes on the stack. Players can respond to the ETB trigger — for example, by removing the creature before the trigger resolves (though the trigger will still resolve even if the creature is gone).
What is the difference between “in response” and “before that resolves”?
They mean the same thing. “In response to your Lightning Bolt” and “before your Lightning Bolt resolves” both mean “I am adding something to the stack on top of your spell.” In casual play, either phrase works. In tournament play, both are understood to mean you are acting while you have priority.
Can sorceries go on the stack?
Yes — every spell goes on the stack when cast, including sorceries. The restriction on sorceries is when you can cast them (only during your main phase when the stack is empty), not whether they use the stack. Once cast, a sorcery sits on the stack like any other spell and can be responded to.
Do tokens entering the battlefield use the stack?
Creating a token does not use the stack — the token just appears. However, the spell or ability that creates the token was on the stack, and any triggered abilities that fire when the token enters (like ETB triggers or constellation effects) go on the stack and can be responded to.
How does the stack work in multiplayer Commander?
The same LIFO rules apply. The main difference is priority order: after the active player casts a spell, priority passes clockwise around the table. Every player must pass priority before the top item resolves. This means more players equals more chances for interaction — and more dramatic stack wars. Simultaneous triggers use the APNAP rule (Active Player, Non-Active Player) described above.
Wrapping Up
The stack is where Magic goes from a game of “play creatures, turn sideways” to a game of strategy, bluffing, and split-second decisions. Understanding it does not require memorizing hundreds of rules — it requires understanding one principle (LIFO), one concept (priority), and developing the instinct to ask “can I respond to this?” before anything resolves.
Start small. Next time you play, consciously think about the stack during your games. When your opponent casts something, pause and consider your options before saying “okay.” When you have open mana, think about what you could be representing. When a triggered ability fires, remember that there is a window to respond.
Before you know it, you will be the one saying “in response” — and watching your opponent’s face fall.
Want to learn more about using stack interactions to your advantage? Check out our guides on Combo Decks 101, Control Decks 101, and Aggro Decks 101 for archetype-specific strategies.
Keep Reading
Related Guides
Example Decks
Explore More