Ward does not make a spell more expensive to cast. It creates a triggered ability after an opponent’s spell or ability targets the permanent. That trigger goes on the stack, players may respond, and the opponent decides whether to pay only when the ward trigger resolves. If they do not pay, ward counters the original spell or ability.
That timing distinction explains most ward questions. It is also why ward creates more play than a simple targeting restriction: the target is legal, the original spell has already been cast, and the table gets another priority cycle before payment is due.
How ward works, step by step
Under the current Magic Comprehensive Rules, ward means: whenever the permanent becomes the target of a spell or ability an opponent controls, counter that spell or ability unless its controller pays the stated cost. Ward is therefore a triggered ability, not an additional casting or activation cost.
- An opponent casts a spell or activates an ability that targets your permanent with ward.
- The opponent completes that process normally, including choosing targets and paying the spell’s or ability’s ordinary costs.
- The permanent has become a target, so ward triggers. The ward trigger is placed on the stack above the original spell or ability.
- Players receive priority and may respond to the ward trigger.
- When the ward trigger resolves, the controller of the targeted spell or ability chooses whether to pay the ward cost.
- If the cost is paid, nothing is countered. The original spell or ability remains on the stack and can resolve later.
- If the cost is not paid, ward counters the original spell or ability.
Suppose an opponent casts a removal spell targeting a creature with ward {2}. They pay the removal spell’s normal casting cost first. Ward then triggers. They do not reserve or prepay the extra two mana during casting; they need to produce it when the ward trigger resolves.
Ward uses the stack—and that creates a response window
Because the ward trigger sits above the targeted spell or ability, either player can respond before the payment decision. The defending player might counter the removal spell, remove another important permanent, or force the opponent to spend mana elsewhere. The opponent might generate more mana or otherwise prepare to pay.
When the ward trigger reaches resolution, its controller cannot cast a spell in the middle of that resolution. However, the player being asked to make a mana payment may activate mana abilities at that point. Tapping a land for mana is fine; casting a ritual spell is not.
A player may also decline to pay even when they can afford the cost. The ward trigger then attempts to counter the targeted spell or ability. This can be deliberate if the player only wanted a cast trigger, wanted the card in their graveyard, or no longer considers the target worth the resources.
What if the targeted spell cannot be countered?
Ward still triggers. “Can’t be countered” does not prevent targeting, and it does not remove the ward ability from the stack. It only prevents the ward trigger’s counter instruction from succeeding.
This means the spell’s controller may decline to pay. Ward resolves, attempts to counter the uncounterable spell, fails, and the original spell remains on the stack. Wizards highlighted this interaction with Heated Debate in the Strixhaven release notes: its protection from being countered explicitly included ward abilities.
Keep the two stack objects separate in your head. Ward is one triggered ability; the spell targeting the permanent is another object. Making the spell uncounterable does not stop the trigger—it just makes the trigger’s threatened consequence ineffective.
Common ward interactions
| Situation | Result |
|---|---|
| The permanent has two ward abilities | Both abilities trigger separately. The opponent may need to pay both costs to keep the original spell or ability from being countered. |
| One spell targets several warded permanents | Each applicable ward ability triggers. Failing to pay any one of them can counter the entire spell, not merely the part affecting that permanent. |
| A target is changed to a permanent with ward | The permanent has newly become a target, so ward triggers and goes above the original spell or ability on the stack. |
| The permanent loses ward after the trigger is created | The existing ward trigger remains on the stack and resolves normally. |
| The permanent gains ward after it was already targeted | Ward does not trigger retroactively. The permanent must become a target while it has the ability. |
| A planeswalker loyalty ability targets the permanent | Ward triggers. If ward counters the loyalty ability, any loyalty counters paid to activate it remain paid. |
| A board wipe destroys the permanent | Ward does nothing unless the spell actually targets it. |
| An opponent is instructed to sacrifice a creature | Ward usually does nothing because the creature being sacrificed was not targeted. |
| A creature with deathtouch deals combat damage | Ward does nothing. Combat damage and deathtouch do not target. |
The multiple-trigger cases are especially easy to misplay. Separate instances of ward do not merge into one giant invoice. Each produces its own trigger. Wizards’ release notes likewise confirm that targeting multiple warded permanents produces a trigger for each applicable permanent.
Target changes can trigger ward
Ward cares about a permanent becoming a target, not only about the targets initially chosen while a spell was cast. If an effect redirects an opponent-controlled spell or ability to your warded permanent, that permanent has become its target and ward triggers.
Changing a target away from the permanent does not erase a ward trigger already on the stack. The trigger exists independently of its source once triggered. Depending on the resulting game state, it may still resolve and attempt to counter the original spell or ability.
Removing the source does not remove the trigger
Once ward triggers, destroying the warded permanent, removing its ward ability, or removing the permanent granting ward does not make the trigger disappear. Wizards specifically documents this principle for cards including Bronze Guardian.
This is the same general reason destroying a creature does not erase an enters-the-battlefield trigger it already created. The ability on the stack is now its own object. Magic is very committed to its paperwork.
Ward only cares about targeting
An effect does not target merely because it affects one permanent or forces a choice involving one. In general, look for the word “target,” although some keyword rules also define targeting. If neither the card text nor the relevant keyword rule targets the warded permanent, ward does not trigger.
- A spell that says “destroy all creatures” does not target those creatures.
- An effect that makes a player sacrifice a creature generally targets neither the chosen creature nor every creature they could choose.
- Combat damage does not target.
- Deathtouch changes how damage is treated as lethal; it does not target. See the guide to deathtouch in Magic for that mechanic’s separate rules.
- Aura spells target while they are on the stack, so casting an Aura on an opponent’s warded permanent can trigger ward.
- An equip ability targets the creature receiving the Equipment, so an opponent-controlled equip ability can trigger ward if it somehow targets your warded creature.
Ward costs are not always mana
A ward cost can ask for any resource or action the rules permit as a cost. Waterfall Aerialist uses the straightforward ward {2}, while other cards turn the payment into a hand, board, or life-total decision.
| Card | Ward cost or effect | Practical pressure |
|---|---|---|
| Timothar, Baron of Bats | Discard a card | Taxes hand size rather than available mana. |
| Saruman of Many Colors | Discard an enchantment, instant, or sorcery card | Requires a particular card type, so an opponent may have cards in hand but still be unable to pay. |
| Mishra, Tamer of Mak Fawa | Gives your permanents ward—sacrifice a permanent | Makes targeted interaction consume material already on the battlefield. |
| Bronze Guardian | Has ward {2} and gives other artifacts you control ward {2} | Creates separate mana taxes across an artifact board. |
The official The Brothers’ War release notes document Mishra’s sacrifice-based ward ability, while The Lord of the Rings release notes provide the exact restricted discard cost on Saruman of Many Colors.
An opponent must be able to pay the complete cost. A player without the required type of card cannot satisfy Saruman’s ward cost merely by discarding something else. Likewise, a player cannot pay a life-based ward cost if the rules prohibit that life payment or they do not have enough life.
Ward versus hexproof, shroud, and protection
| Ability | Can an opponent target it? | Can its controller target it? | What happens? |
|---|---|---|---|
| Ward | Yes | Yes | An opponent’s targeting spell or ability causes a trigger that may counter it unless the ward cost is paid. |
| Hexproof | No | Yes | Opponent-controlled spells and abilities cannot choose it as a target. |
| Shroud | No | No | No player’s spells or abilities can choose it as a target. |
| Protection | Not from sources with the stated quality | Usually, if the controller’s source lacks that quality | Also affects damage, blocking and attachments from the protected quality. |
The practical difference is interaction. Hexproof in MTG prevents the opponent from making the targeted play at all. Ward permits the play but makes its efficiency uncertain. Shroud is more symmetrical, while protection is a larger bundle of rules rather than merely another form of hexproof.
None of these should be treated as universal immunity. Nontargeting removal can get around ward, hexproof, and shroud. Protection only helps against the qualities it names and according to protection’s specific damage, attachment, blocking, and targeting rules.
How to choose ward cards for a real deck
Ward is usually support for a card’s main job, not a reason to play the card by itself. Start by asking what opponents gain by removing the permanent and whether its ward cost will still matter at the stage of the game when you expect to cast it.
For artifact decks: Kappa Cannoneer or Bronze Guardian
Kappa Cannoneer rewards a high artifact count directly. It has improvise and ward {4}, then receives a +1/+1 counter and becomes unblockable for the turn whenever it or another artifact enters under your control. Its ward cost is most punishing when it arrives early enough that four spare mana is unrealistic.
Bronze Guardian serves a different role. Its own ward {2} is modest, but giving your other artifacts ward {2} can make an opponent pay repeatedly to dismantle a developed artifact engine. It is the better ward-focused choice when protecting several important artifacts matters more than presenting one evasive threat.
For a resilient value threat: Tivit, Seller of Secrets
Tivit, Seller of Secrets combines flying and ward {3} with vote-based triggers that create Clue and Treasure tokens. Ward does not make a six-mana threat invincible, but it can make a one-for-one removal spell awkward while Tivit’s other abilities generate resources.
For a buildaround tax: Mishra or Saruman
Mishra, Tamer of Mak Fawa is interesting when the deck can exploit its wider game plan while making targeted removal demand a permanent sacrifice. Saruman of Many Colors instead attacks hand composition: an opponent may have ample mana yet lack an enchantment, instant, or sorcery card to discard.
These examples are use-case suggestions, not claims of legality or strength in every format. Before adding one to a tournament deck, check its current format legality and the relevant banned or restricted list. For Commander, also confirm color identity and ask whether the card advances the deck when nobody points removal at it.
The useful way to think about ward
Ward is not “almost hexproof,” even when a large cost makes it feel that way. It is a delayed decision point. An opponent may target the permanent, the trigger may be answered, resources may change, and payment is not requested until resolution.
For rules calls, keep three objects and moments separate: the warded permanent becomes a target; the ward trigger goes on the stack; the original spell or ability remains underneath it. For deckbuilding, judge ward by the resource it attacks and the turn when that resource will be scarce. That is what turns a parenthetical keyword into actual friction.