TLDR: Ward allows targeting but threatens to counter the spell or ability unless its controller pays. Hexproof prevents opponents from targeting the permanent in the first place. Protection prevents targeting by a specified quality and also affects damage, blocking, and attachments. Before using interaction, ask three questions: Does my effect target? Is this a legal target now? What happens between targeting and resolution?
The practical question behind ward, hexproof, and protection how they change interaction is not simply whether a creature is “protected.” It is where your attempted answer can break down. Ward changes the resource transaction after targeting. Hexproof changes whether targeting is legal. Protection can change targeting, combat, damage, and attachments, but only in relation to the quality it names.
That distinction determines whether you should cast targeted removal, find a non-targeting answer, wait for a better window, or force an opponent to spend their defensive effect first.
Start every interaction with the word “target”
A Magic spell or ability targets when its rules text uses the word “target.” Targets are chosen as that spell or ability is put on the stack. This happens before the spell resolves.
That gives you a reliable first checkpoint: read the effect rather than sorting it into a loose category such as “removal.” “Destroy target creature” targets. An effect that instructs each player to sacrifice a creature does not target unless its text also says that it does. A global effect applying to all creatures generally does not target either.
Once you know whether the effect targets, use this sequence:
- Identify every target the spell or ability requires.
- Check whether each chosen object or player is a legal target right now.
- Put the spell or ability on the stack and account for any ward triggers.
- Decide whether paying ward still advances your plan.
- Before resolution, reassess whether the target remains legal.
If every target has become illegal by the time a spell or ability would resolve, it does not resolve. This is why gaining hexproof or appropriate protection in response can defeat removal that was legal when cast.
Ward changes the price, not initial legality
Ward does not prevent an opponent from choosing the permanent as a target. It is a triggered ability that triggers when an opponent’s spell or ability targets that permanent. When the ward ability resolves, it counters the triggering spell or ability unless that opponent pays the stated cost. Wizards introduced the mechanic as protection that still permits opponents to attempt interaction rather than stopping the attempt outright.
Suppose you cast a spell that says “destroy target creature” targeting an opposing creature with ward. The removal goes onto the stack. Ward then triggers and is placed above it. When the ward trigger resolves, you choose whether to pay. If you decline, the ward ability counters your removal. If you pay, the removal remains on the stack and can eventually resolve, assuming its target remains legal.
This matters because ward is not an additional cost paid while casting the removal. Your mana or other ward payment is committed later, during resolution of the ward trigger. That creates another decision point rather than merely making the removal spell more expensive.
Treat ward as a complete transaction
Do not ask only, “Can I pay for ward?” Ask whether the entire exchange is favorable. Count the removal spell, the ward payment, the mana you must leave unavailable afterward, and any defensive response the opponent is representing.
For example, you target a ward creature and can exactly afford the tax. If your opponent can give that creature hexproof after you pay, your removal may still lose its only legal target before resolving. You have then spent both the card and the ward payment without removing the threat. Sometimes that exchange is unavoidable, but recognizing the exposure can point to a better sequence: force out the protection effect first, interact with the defensive permanent, or wait until the opponent cannot represent the response.
A spell or ability targeting multiple ward permanents can cause each applicable ward ability to trigger. One unpaid ward trigger can counter the entire original spell or ability, not merely the portion aimed at that permanent. Multi-target interaction therefore demands that you budget for the complete set of ward triggers rather than treating each target as an independent bargain.
Hexproof closes the opponent’s targeting route
Hexproof means a permanent cannot be targeted by spells or abilities its opponents control. The permanent’s controller can still target it with their own spells and abilities. Unlike ward, hexproof does not allow an opponent to target first and pay later. The proposed target is illegal from the beginning.
Imagine an opponent controls a creature with hexproof. Your “destroy target creature” spell cannot be cast targeting it. Paying more mana changes nothing because there is no ward-style transaction to complete. Your next question should be whether another type of interaction can affect it without targeting.
Depending on the exact text and board state, possible routes include:
- A global effect that affects all creatures without targeting.
- An effect that makes a player sacrifice a creature without targeting that creature.
- Removing the source that grants hexproof, if that source is itself vulnerable.
- Countering the creature spell before it resolves and becomes a hexproof permanent.
- Changing combat incentives so the creature cannot attack or block profitably.
These are categories, not interchangeable solutions. A sacrifice effect may be poor when the opponent controls expendable creatures, while a global effect may damage your own board. The tactical goal is to change the axis of interaction, not merely replace one removal card with another at random.
Hexproof gained in response is different from hexproof already present
If a permanent already has hexproof from you when you try to cast opposing targeted removal, you cannot choose it as the target. If it gains hexproof after being legally targeted, the spell stays on the stack but checks target legality again as it tries to resolve. If that permanent is its only target, the spell does not resolve because every target is now illegal.
This makes timing central. When an opponent has an untapped permanent or card that can grant hexproof, you are not evaluating only their current board. You are also evaluating the response they can represent. Improving this habit is part of making your assumptions and alternatives visible during a game, a broader process covered in the gameplay decisions that matter most.
Protection changes more than targeting
Protection applies against the quality stated by the ability, such as a color or card type. It prevents four main things commonly remembered with DEBT: damage, enchanting or equipping, blocking, and targeting. Fortifications are covered by the same relevant attachment restriction.
- Damage from sources with the stated quality is prevented.
- Auras, Equipment, and Fortifications with that quality cannot be attached to the protected object.
- Creatures with that quality cannot block a protected attacking creature.
- Spells and abilities from sources with that quality cannot target the protected object.
The named quality is the limiting factor. Protection from red does not prevent a nonred source from targeting, blocking, attaching, or dealing damage. It also does not automatically stop a red effect that does not target, deal damage, attach, or block. Read what the effect does rather than treating protection as universal immunity.
Protection can turn a defensive trick into a combat trick
Suppose your attacker gains protection from the color of its blocker before combat damage. The matching creature can no longer legally block it. If it was already declared as a blocker, granting protection does not make the attacker unblocked, but damage that matching source would deal to the protected creature is prevented. Protection therefore affects both combat access and damage, but the timing changes which benefit you receive.
The same ability can defeat targeted removal when the removal’s source has the protected quality. If a red spell targets your creature and you grant protection from red in response, that creature becomes an illegal target for that spell. If it was the spell’s only target, the spell will not resolve.
Check your own attachments before granting protection
Protection can also interfere with your own board. If a creature gains protection from a quality shared by an Aura, Equipment, or Fortification attached to it, that object cannot remain attached in the prohibited way.
This is an easy cost to miss when protection is being used as a removal answer or combat trick. Before choosing the protected quality, inventory both sides of the battlefield. Saving the creature may still be correct, but you should know whether doing so sacrifices an Aura’s position or causes Equipment to fall off at an inconvenient moment.
Ward vs. hexproof vs. protection at a glance
| Question | Ward | Hexproof | Protection |
|---|---|---|---|
| Can an opponent initially target it? | Yes | No | Not with a source matching the protected quality |
| What happens on the stack? | Ward triggers and may counter the targeting spell or ability unless its cost is paid | No hexproof-prohibited target can be chosen; gaining hexproof later can make an existing target illegal | Appropriate protection prevents the target from being chosen; gaining it later can make that target illegal |
| Do non-targeting effects still matter? | Usually, because ward triggers from targeting | Yes, if the effect does not otherwise depend on targeting | Often, but protection may still prevent matching damage or affect attachments and blocking |
| Does it affect combat by itself? | No | No | Yes; it can restrict blockers and prevent matching damage |
| Can it disrupt attachments? | No | No | Yes, when the attachment has the protected quality |
The table is a starting point, not a substitute for reading the exact effect. Ward costs vary, protection names different qualities, and non-targeting effects can still fail for unrelated reasons. The useful habit is to classify the interaction before committing resources.
Use this checklist before committing interaction
When a protected threat must be answered, I would run through these questions in order:
- Does my spell or ability actually use the word “target”?
- Is the object a legal target under its current hexproof or protection abilities?
- If it has ward, what is the complete cost of the exchange—not just the printed removal cost?
- How many ward triggers will the spell create?
- Can the opponent make the target illegal after I pay for ward?
- Would a non-targeting effect attack the board more efficiently?
- If protection is involved, does it also change blocking, damage, or attachments?
- Is there a sequencing line that forces the defensive response before I commit my best answer?
The fastest practical distinction is this: ward asks whether the interaction is worth paying for, hexproof asks whether the interaction can target at all, and protection asks whether the source matches a prohibited quality—and then makes you check combat, damage, and attachments too.
Make the mechanic identify your next line
Do not stop at “that creature is protected.” Name the actual restriction. Against ward, calculate and sequence the transaction. Against hexproof, change from targeted interaction to another axis. Against protection, identify the named quality and check all four relevant dimensions: damage, attachments, blocking, and targeting.
On your next removal decision, pause before announcing the target. Confirm legality, map the stack, and decide what response the opponent can represent. That short check will prevent wasted spells and often reveal a stronger line before any resources are committed. The official Magic rules page is the right place to verify current rules documents when an unusual interaction turns on exact wording.