TLDR
The practical answer to when to remove a creature before its controller untaps is usually during the end step immediately before that player’s turn. You cannot act during the untap step itself. If you wait until upkeep, the creature has already untapped, beginning-of-upkeep abilities have triggered, and the active player receives priority before you do. Use the preceding end step when denying that untap or the first activation of the new turn matters.
That does not mean “always cast removal in the end step.” The best timing depends on what you need to deny: an untap, an upkeep trigger, a tap activation, combat, a static ability, or part of a combo. Good removal timing begins by naming the specific action you cannot allow.
There Is No Window Immediately Before or During Untap
Magic’s turn structure creates a common timing trap. The beginning phase contains the untap, upkeep, and draw steps, but players do not receive priority during the untap step. Permanents untap as a turn-based action, and the game proceeds to upkeep without giving either player a chance to cast an instant or activate a normal ability in between. The official Magic Comprehensive Rules define this timing structure.
| Point in the turn | What has happened | Can you cast removal? |
|---|---|---|
| Opponent’s preceding end step | Their next untap has not happened | Yes, when you receive priority |
| Opponent’s untap step | Their applicable permanents untap | No; no player receives priority |
| Opponent’s upkeep | Their permanents have already untapped and upkeep triggers have triggered | Yes, but the active player receives priority first |
| Opponent’s draw step | They have reached their draw for the turn | Yes, after the turn-based draw and applicable triggers |
The last normal priority window before a creature untaps is therefore the preceding turn’s end step. Once both the stack is empty and every player passes in succession, the game advances. You cannot let the turn reach untap and then try to insert removal before the creature becomes usable.
Ask What Resource the Removal Must Deny
“I want that creature dead” is not yet a timing plan. A better question is: “What happens if I give its controller one more priority window with it?” That reframes removal as a resource decision instead of a reflex.
- If you must deny the creature’s next untap, remove it during the preceding end step or earlier.
- If you must prevent a beginning-of-upkeep ability from triggering, remove its source before the upkeep begins.
- If you must stop a non-mana activated ability already being activated, removal is usually too late to stop that ability; deal with the ability on the stack if possible.
- If you only need to stop an attack, waiting may reveal more information and preserve your flexibility, provided the delay does not expose you to protection, sacrifice, or attack triggers.
- If the creature supplies an important static effect, act before the game action that effect would change.
- If the creature is part of an immediate combo, interact at the last point that actually breaks the sequence—not automatically at the end of the turn.
This is the same habit behind stronger overall in-game decision-making: identify your objective, compare the available windows, and choose the line that denies the most important opposing option while preserving as many of your own options as possible.
Why End-Step Removal Is Often Strongest
Suppose an opponent controls a tapped creature that can produce mana or generate value by tapping. They end their turn with it still tapped. Removing it during that end step has two advantages: you retained your mana and information throughout their turn, and the tapped creature normally cannot pay another tap cost in response. If you wait until upkeep, it will have untapped and may be usable before you receive priority.
That is the cleanest version of end-step removal: wait until the threat has been used, then remove it before it refreshes. In multiplayer, the same line also gives other players a chance to spend their interaction first. The tradeoff is that waiting leaves the creature and any static effects it provides on the battlefield for the rest of the current turn.
End-step timing is particularly attractive when all of the following are true:
- The creature is currently tapped or otherwise unable to use its relevant ability.
- Its next untap would generate an immediate advantage.
- It does not need to die sooner to stop a combo, attack, or static effect.
- You can safely leave mana open until the end step.
- You are willing to accept any death trigger or replacement effect associated with removing it.
An Untapped Creature May Still Respond
Casting removal during the end step does not prevent every response. If the creature is untapped and has a legal tap ability, its controller can generally activate that ability in response. Tapping the creature does not counter the removal spell, but the controller still gets the ability’s effect if it resolves.
For example, imagine an untapped value creature with “Tap: draw a card.” You target it with an instant during the end step. Its controller can activate the ability, putting that ability above your removal. The ability resolves first, and then the creature is destroyed. You have prevented future activations, but not the final one.
This is why removing a tap-based engine after its controller uses it can be better than acting while it remains untapped. You let the original activation happen, but you avoid giving the creature an extra activation in response and still prevent it from untapping for the next turn.
Mana abilities are a special case
An activated mana ability normally does not use the stack. If an untapped mana creature can legally activate such an ability, its controller may produce mana before the removal resolves, and players cannot respond to the mana ability itself. You may still be able to respond to a spell or non-mana ability for which that mana is used.
The distinction matters because “I kill it in response to it tapping for mana” does not reverse the mana production. The mana ability has already resolved. Your removal can stop later uses of the creature, but it cannot retroactively remove mana that has already been produced.
Removing the Source Usually Does Not Stop Its Ability
Once an activated or triggered ability is on the stack, it generally exists independently of its source. Destroying the creature afterward usually does not counter that ability. Exceptions depend on the ability’s wording, such as requiring information about the source or having legal targets that can disappear, but “kill the creature to stop the ability” is not a reliable general rule.
Consider a creature with a beginning-of-upkeep triggered ability. As upkeep begins, the ability triggers before anyone receives priority. After applicable triggers are put on the stack, the active player receives priority first. Removing the creature at that point does not erase its trigger. If your objective was to prevent the trigger entirely, the preceding end step was the important window.
This also explains why waiting for upkeep can be especially risky against an untapped engine. The creature has already untapped, its upkeep ability may already be on the stack, and its controller gets the first chance to take an action. Your removal may still prevent later use, but it cannot recreate the opportunities you already allowed.
Four Board States and the Best Default Timing
1. A tapped mana creature
Your opponent has finished their turn, and their mana creature is tapped. You believe that one additional mana on their next turn enables a play you cannot handle. Remove the creature in the end step. Waiting until upkeep allows it to untap, and its controller may activate its mana ability before you receive priority.
2. An untapped value engine
The creature can tap to generate value and has not been used. End-step removal still prevents future turns of value, but it probably cannot prevent one final activation. If that activation is unacceptable, you may need a different form of interaction, a spell that prevents abilities, or an earlier line that pressures the opponent into using the creature under less favorable conditions.
3. A beginning-of-upkeep trigger
The creature’s important ability triggers at the beginning of its controller’s upkeep. Remove the creature before that upkeep begins—normally during the preceding end step. Killing it after the trigger is on the stack usually does not stop the trigger. If the trigger targets, you may instead be able to make its targets illegal, but that is a separate tactical plan.
4. A creature that matters only in combat
If the creature has no relevant static, triggered, or activated ability and your only concern is its attack, you may gain information by waiting. The opponent might cast another, more dangerous threat or choose not to attack. However, remove it before attackers are declared if you also need to prevent an attack trigger; after declaration, the creature is already attacking and relevant attack triggers have triggered.
Waiting also has costs. The opponent may find protection, sacrifice the creature for value, or force you to spend mana at an awkward time. Targeting restrictions such as ward, hexproof, and protection can further change whether your intended interaction works; those distinctions are covered in how ward, hexproof, and protection change interaction.
Do Not Confuse “Latest Possible” With “Best”
Players often preserve optionality by waiting, but the latest legal window is not automatically the strongest one. Act earlier when the creature is already enabling something dangerous, when the opponent could sacrifice or protect it, when your mana will be constrained later, or when leaving it in play changes combat or a combo sequence.
Conversely, delay when nothing important can happen yet and waiting gives you useful information. In Commander, another player may remove the threat, the controller may spend resources elsewhere, or a new threat may become the higher priority. Saving removal is valuable only while the delay remains safe.
A useful test is to compare two costs: the value your opponent gains if you wait and the information or flexibility you lose if you act now. End-step removal is best when the first cost sharply increases at untap while the second cost remains small.
Handling “Go” or “Your Turn” Clearly
In sanctioned play, saying “go” or “your turn” normally proposes a shortcut through the end of the turn. An opponent who wants to act can indicate that they are doing so in the end step.
The practical habit is simple: be explicit. Say, “In your end step, I cast this targeting that creature.” This avoids the ambiguous exchange where one player begins untapping while the other says they intended to act. Clear communication protects both the tactical line and the game state.
The Removal-Timing Checklist
Before casting instant-speed removal, run through this short sequence:
- Name the action you must prevent: untapping, triggering, activating, attacking, protecting, or enabling another permanent.
- Identify the last priority window before that action happens.
- Check what the creature can do in response, especially tap abilities, sacrifice abilities, and protection effects.
- Ask whether its important ability is already on the stack. If so, removing the source usually will not stop it.
- Compare the value of waiting for more information with the risk of giving the opponent another useful priority window.
- Communicate the chosen step clearly, particularly when acting after an opponent says “go.”
The Practical Takeaway
When the goal is specifically to stop a creature from untapping and being used on the next turn, remove it during the preceding end step. There is no interaction window during untap, and upkeep is already too late to deny the untap itself.
Then apply the exception that matters: act before upkeep to prevent an upkeep trigger, earlier to break an immediate combo, or later when only combat matters and waiting is safe. Do not memorize “end step” as a ritual. Identify the resource you need to deny, find the last safe window, and use removal there.