If you’ve ever felt personally betrayed by combat math, timing windows, or that one friend who always “has it,” this MTG combat step breakdown is for you. MTG combat is not complicated because it’s deep. It’s complicated because it’s Magic, and Magic likes paperwork.
Combat is a phase with five steps. Each step has a “do the turn-based stuff” moment, then players get priority to cast instants and activate abilities. Most combat blowouts happen because someone acted in the right idea, wrong step.
The combat phase, in plain English
Here’s the order every single time:
- Beginning of combat
- Declare attackers
- Declare blockers
- Combat damage (sometimes twice)
- End of combat
If no one attacks, the declare blockers and combat damage steps get skipped. Which is honestly the healthiest possible combat.
1) Beginning of combat step: your last chance to stop attackers cleanly
This is the “before attackers are declared” window.
What happens:
- “At the beginning of combat” triggers happen.
- Then the active player (the one whose turn it is) gets priority.
What you do here (common plays):
- Tap a creature so it can’t attack (if it doesn’t have vigilance and it needs to tap to attack).
- Remove a creature you suspect is about to attack (bounce, kill spell).
- Set up combat with an instant-speed trick that needs to happen before attackers exist.
Common mistake:
- Waiting until after attackers are declared to “prevent the attack.” You can’t undo the declaration. You can only respond after it’s already attacking, which is… less preventative and more “damage control,” sometimes literally.
2) Declare attackers step: attackers become attackers, not “potential” attackers
This step has a turn-based action: the active player declares which creatures attack, and who or what they’re attacking (a player, a planeswalker, or a battle). This declaration does not use the stack.
Then:
- Attack triggers go on the stack.
- The active player gets priority.
What you can do after attackers are declared:
- Cast removal on an attacker.
- Pump an attacker (sometimes you want to, but see the “don’t give free info” rule below).
- Create surprise blockers later (tokens, flash creatures) if your deck enjoys being annoying.
What you cannot do:
- “Respond to the choice of attackers” as if it’s a spell. The choice happens first. Then you respond to the results.
Dry, practical advice:
- If your plan is “kill it so it can’t attack,” do it in beginning of combat.
- If your plan is “let it attack, then punish them,” do it here or later.
3) Declare blockers step: blocks happen, then the real game begins
The defending player declares blockers. This is also a turn-based action that does not use the stack.
Then:
- “When this blocks” and “when this becomes blocked” triggers go on the stack.
- The active player gets priority first, then the defending player.
This is the classic combat trick window because you finally know the blocks.
What you do here:
- Cast pump spells on a blocked creature to win the fight.
- Remove a blocker so damage pushes through (or so your attacker survives).
- Use “gotcha” abilities that require an unblocked attacker (hello, ninjutsu fans).
Common mistake:
- Thinking that tapping a creature after it blocks makes it stop blocking. Once a creature is a legal blocker, tapping it later does not magically un-block. (Magic is cruel, but it is consistent.)
Important trigger timing note:
- “Attacks and isn’t blocked” abilities don’t trigger when attackers are declared. They trigger here, after blockers are declared and the creature ends up unblocked.
4) Combat damage step: damage is assigned, then dealt, and yes it matters when
At the start of combat damage, creatures assign damage. This assignment does not use the stack.
Then combat damage is dealt simultaneously.
Then players get priority again.
First strike and double strike: why there are sometimes two damage steps
If any attacking or blocking creature has first strike or double strike as combat damage begins, you get:
- First combat damage step (first strike + double strike creatures deal damage)
- Then a second combat damage step (everyone else, plus double strike again)
This creates a nasty little timing window:
- After first strike damage is dealt, you can cast spells before normal damage happens.
So yes, you can do things like:
- Let your first striker hit, then remove their creature before it hits back in regular damage.
- Or save something from dying to regular damage after it already survived first strike.
New-ish headache: multiple blockers and damage “order”
If one attacker is blocked by multiple creatures, you might remember older rules where you had to set a damage assignment order and “deal lethal to the first blocker before the next.”
Now, in most cases, the attacker’s controller can divide combat damage among all blockers however they want when damage is assigned. No pre-declared “order” paperwork. (Magic sometimes deletes paperwork. It’s unsettling.)
Trample still plays by the “you must respect the blockers” rule
Trample is the big exception that still cares about “lethal first”:
- You must assign lethal damage to each blocker before assigning any excess to the player (or planeswalker/battle being attacked).
Extra spice:
- Deathtouch makes “1 damage” count as lethal for trample purposes. Because if you’re going to be gross, at least be efficient.
5) End of combat step: cleanup, delayed triggers, and the last exit ramp
This is where “at end of combat” triggers happen, and some effects that last “until end of combat” expire.
Practical uses:
- Some creatures get sacrificed at end of combat (like decayed).
- Some delayed triggers wait here to fire.
- Sometimes you just want combat to end so you can stop calculating.
Combat tricks: when to cast them so they do what you think they do
Here’s the part everyone thinks they know, right up until they lose a creature and swear the rules changed overnight.
The “don’t give free info” rule
If your trick is a pump spell, casting it before blockers is often just announcing, “Hello, I have a trick, please block differently.”
Most of the time:
- Pump spells want to be cast after blockers are declared.
- Removal depends on what you’re trying to accomplish.
Removal timing, simplified
- Beginning of combat: stop attacks before they happen.
- After attackers: remove an attacker (it won’t deal damage if it’s gone).
- After blockers: remove a blocker to push damage through, or remove an attacker so it doesn’t trade up.
- Between first strike and regular damage: the advanced class. Bring snacks.
The “too late” moments (where your spell does basically nothing)
- After combat damage is dealt, pumping a creature does not save it from the damage already marked.
- After a creature is blocked, “tapping the blocker” doesn’t undo the block.
- After your opponent passes priority and you say “damage?” without thinking, you may discover what regret feels like.
A quick MTG combat step breakdown cheat sheet
- Want to prevent a creature from attacking? Do it in beginning of combat.
- Want to react to attack triggers or surprise blocks later? Act after attackers.
- Want maximum value from pump spells? Act after blockers.
- Want to get fancy with first strike timing? Act between damage steps (only if first strike or double strike is involved).
- Want to stop thinking? Go to end of combat and pretend you meant it.
Closing thoughts
MTG combat is basically a legal contract that occasionally punches you. Once you internalize the priority windows, this MTG combat step breakdown stops feeling like a trap and starts feeling like a tool. You’ll still lose creatures sometimes. That’s normal. But at least you’ll lose them on purpose, which is the closest thing Magic offers to control.
If you’re also tuning the rest of your deck’s fundamentals, you might like The Best Esper Lands in MTG or, if you need a palate cleanser from all this responsible timing, D&D’s Lack of 2026 Announcements is Actually Typical.
