TLDR
Indestructible stops a permanent from being destroyed. It does not stop sacrifice, exile, returning the permanent to its owner’s hand, putting it into a library, or putting a creature into a graveyard for having 0 or less toughness. In practical terms, sacrifice and exile both answer an indestructible permanent because neither action destroys it. Magic cares about the exact verb, not the general emotional experience of losing your favorite creature.
- Destroy: Indestructible stops effects that say “destroy,” destruction from lethal damage, and destruction caused by deathtouch damage.
- Sacrifice: The permanent’s controller moves it from the battlefield to its owner’s graveyard. Indestructible does not help.
- Exile: The object moves to the exile zone. Indestructible does not help.
- Zero toughness: A creature with 0 or less toughness goes to its owner’s graveyard as a state-based action. This is not destruction.
- Bounce or tuck: Returning a permanent to a hand or putting it into a library also bypasses indestructible.
These distinctions come from the official Magic Comprehensive Rules. Wizards also maintains a central Magic rules hub with the current rules documents and related resources.
What indestructible actually protects against
Indestructible is a keyword ability meaning that a permanent cannot be destroyed. “Destroy” is a specific rules action rather than a catch-all term for removing something from the battlefield. A permanent can be destroyed by a resolving effect that uses the word “destroy,” or a creature can be destroyed by the state-based actions associated with lethal damage and damage from a source with deathtouch.
Suppose an indestructible 4/4 creature has 10 damage marked on it. It remains on the battlefield because the lethal-damage state-based action cannot destroy it. Indestructible does not prevent the damage, remove the damage, or make the creature immune to other effects. The damage remains marked until the cleanup step unless something removes it earlier.
The same principle applies to deathtouch. Damage from a source with deathtouch would ordinarily cause the damaged creature to be destroyed during a state-based-action check. An indestructible creature cannot be destroyed that way, so it survives.
Regeneration works within a similarly narrow lane. A regeneration effect replaces an upcoming destruction event. It cannot replace sacrifice, exile, or the state-based action that puts a creature with 0 or less toughness into its graveyard. Regeneration and indestructible are not interchangeable, but both require the event to be destruction before they can matter.
Sacrifice is not destruction
To sacrifice a permanent, its controller moves it directly from the battlefield to its owner’s graveyard. Only the permanent’s controller can sacrifice it. An opponent can instruct you to sacrifice something, but that opponent does not perform the sacrifice or choose your permanent unless the effect specifically changes who makes the choice.
Because sacrifice is not destruction, indestructible cannot stop it. Liliana of the Veil provides the classic example: her −2 ability says, “Target player sacrifices a creature.” The ability targets the player, not the creature that player eventually chooses. An indestructible creature can therefore be selected and sacrificed.
That distinction also explains why hexproof, shroud, and protection on the creature usually do not save it from an edict-style sacrifice instruction. The creature is not being targeted. If the ability targets a player, protection or hexproof on that player may matter instead. An instruction such as “each opponent sacrifices a creature” does not target merely because each affected player must make a choice. ProxyKing’s guide to protection and targeting in MTG covers that adjacent rules distinction in more detail.
Sacrifice as a cost happens immediately
Text before the colon in an activated ability is its cost. If that cost includes sacrificing a permanent, the permanent is sacrificed while the ability is being activated. Players do not receive priority in the middle of paying the cost, so an opponent cannot wait to see the activation and then remove the permanent before it is sacrificed. By the time anyone can respond to a nonmana ability on the stack, the cost has already been paid.
Gilded Goose demonstrates the pattern with a mana ability whose cost includes “Sacrifice a Food.” The Food is sacrificed while paying the activation cost. Because this is a mana ability, it does not use the stack and resolves immediately after it is activated; players cannot respond to or counter it.
This is also why It That Betrays can trigger when an opponent sacrifices a nontoken permanent to pay a cost. If that cost was paid to cast a spell or activate a nonmana ability, the sacrifice event occurs first, its triggered ability waits to be put onto the stack, and the original spell or ability has not yet resolved. A mana ability instead resolves immediately, and the trigger waits to be put onto the stack the next time a player would receive priority. “Sacrificed” is an event category with its own rules consequences; it is not informal shorthand for “was destroyed somehow.”
If activation timing is the confusing part, the broader distinction between activating an ability and resolving it is covered in the guide to using tap abilities and priority.
Sacrifice during resolution works differently
Sometimes sacrifice is an instruction performed while a spell or ability resolves rather than a cost paid to put it on the stack. Players can respond before that spell or ability begins resolving. Once resolution starts, however, players generally do not receive priority between its individual instructions. The affected player makes the required sacrifice at the appropriate point in that resolution.
This gives you a useful table shortcut: look for the colon. “Sacrifice a creature: Draw a card” uses the sacrifice as an activation cost. “Target player sacrifices a creature” performs the sacrifice during resolution. The first creature is gone before opponents can respond to the ability; the second instruction can be answered while its source is still on the stack.
Exile bypasses indestructible
Exile is a zone, and moving an object there is not destruction. An effect that says “exile target creature” can remove an indestructible creature normally. Some exile effects include instructions that later return the card, but exile itself does not promise a return trip. Read the entire effect rather than treating exile as temporary by default.
Indestructible also does not make a permanent an illegal target for an exile spell. You can respond to targeted exile before it resolves by countering the spell, giving the target relevant hexproof or protection, sacrificing the target to another effect, or otherwise making the target illegal. If the target remains legal when the exile spell resolves, it is exiled. If every target of a targeted spell or ability is illegal at resolution, that spell or ability does not resolve.
When a card changes zones, it generally becomes a new object with no memory of its previous existence. If a creature is exiled and then returned, it is normally a fresh battlefield object. Damage, counters, Auras, Equipment attachments, and effects that applied to its previous existence do not simply follow it through exile. An effect can create specific exceptions, but the new-object rule is the baseline.
Sacrifice, exile, and “dies” triggers
A creature “dies” when it is put into a graveyard from the battlefield. A creature sacrificed normally goes from the battlefield to the graveyard, so it dies and can trigger abilities that care about a creature dying. An exiled creature does not go to the graveyard, so it does not die.
The event can become more complicated when a replacement effect changes the destination. If an effect replaces the graveyard move with exile, a creature can still have been sacrificed even though it did not die. The sacrifice action happened, but the resulting zone change was modified. Abilities watching for a sacrifice may trigger; abilities watching for a creature to die will not.
| Event | Stops an indestructible permanent? | Does a creature normally die? | Targets by default? |
|---|---|---|---|
| Destroy | No | Yes, if destruction puts it into the graveyard | Only if the effect says “target” |
| Sacrifice | Yes | Yes | No |
| Exile | Yes | No | Only if the effect says “target” |
| 0 or less toughness | Yes | Yes | No |
| Return to hand | Yes | No | Depends on the effect |
“Yes” in the second column means the event can remove or otherwise answer the indestructible permanent. The exact result still depends on replacement effects and the spell or ability’s full text.
Why toughness reduction defeats indestructible
A creature with 0 or less toughness is put into its owner’s graveyard during a state-based-action check. The rules do not destroy that creature, so indestructible cannot save it. This is why effects that reduce toughness are reliable answers to indestructible creatures.
Massacre Wurm is a practical example because its enters ability gives creatures your opponents control −2/−2 until end of turn. An indestructible 2/2 affected by that ability becomes a 0/0 and goes to the graveyard. A larger indestructible creature may survive the reduction, so the actual toughness still matters; “minus” is not a magical synonym for removal.
Damage and toughness reduction are different. If a 5/5 indestructible creature has 4 damage marked on it and then gets −1/−1, it becomes a 4/4 with 4 damage. Lethal damage still cannot destroy it. If it instead gets −5/−5, its toughness becomes 0, and the separate 0-toughness state-based action puts it into the graveyard.
Edge cases that decide real games
Tokens can be sacrificed or exiled
A token can move from the battlefield to the graveyard or exile like another permanent. It then ceases to exist during a state-based-action check. A sacrificed token can still cause appropriate sacrifice and death triggers because it reached the graveyard before disappearing. An exiled token did not die because it did not enter a graveyard.
Commanders visit the graveyard or exile first
If a commander is sacrificed, it goes to the graveyard. If it is exiled, it goes to exile. During the next state-based-action check, its owner may move it from that zone to the command zone. That means the commander did enter the graveyard or exile, which can matter for applicable triggers and replacement effects. Moving it to the command zone does not rewrite the earlier event.
Simultaneous sacrifice uses APNAP choices
When an effect instructs multiple players to choose permanents and sacrifice them simultaneously, choices are made in active-player/nonactive-player order. The active player chooses first, followed by each other player in turn order, and then the chosen permanents are sacrificed simultaneously. Later players therefore know the earlier choices, even though all the permanents leave together.
Removing the source may not stop the instruction
Once an activated or triggered ability is on the stack, removing its source usually does not remove that ability. Destroying Liliana in response to her −2 ability, for example, does not by itself stop the targeted player from sacrificing a creature. You need to counter the ability, make its target illegal, or change the game state so the instruction produces a better outcome.
The table shortcut to remember
The fastest sequence is: identify the verb, check for the word “target,” locate any colon, and determine the destination zone. Those four checks settle most indestructible-versus-removal disputes before the table needs to form a rules committee with snacks.
References
- media.wizards.com
- Rules | Magic: The Gathering
- Liliana of the Veil – MTG Proxy Innistrad – Proxy King
- Protection From a Color in MTG: Damage, Enchanting, Blocking, and Targeting – Proxy King
- Gilded Goose (Foil Showcase) – MTG Proxy Throne of Eldraine – Proxy King
- It That Betrays – MTG Proxy Rise of the Eldrazi – Proxy King
- Massacre Wurm (Showcase) – MTG Proxy Core Set 2021 – Proxy King
