Deathtouch has one central rule: when a source with deathtouch deals any positive amount of damage to a creature, that creature is destroyed the next time state-based actions are checked. It does not matter whether the damage was dealt in combat, during a fight, or through an ability that names the deathtouch creature as the damage source. This destruction is a state-based action, not a triggered ability, so nobody puts “the deathtouch trigger” on the stack. There is no such trigger.
That compact rule creates several less-obvious consequences. Zero damage does nothing. Prevented damage does nothing. Indestructible survives. First strike helps only if it removes the deathtouch creature before that creature deals damage. Trample, meanwhile, turns deathtouch into a remarkably efficient way to get damage past a blocker.
The interactions below follow the Comprehensive Rules effective September 25, 2026. The same core rules apply across formats, although the legality of individual cards depends on the format. Wizards maintains the current documents on its official Magic rules hub.
What deathtouch actually checks
The game checks whether a creature with toughness greater than zero has been dealt damage by a source with deathtouch since state-based actions were last checked. If so, that creature is destroyed. The source does not necessarily need to remain on the battlefield afterward; what matters is the source of the damage and its relevant characteristics when the damage was dealt.
| Situation | Result |
|---|---|
| A 1/1 with deathtouch deals 1 damage to a 10/10 | The 10/10 is destroyed when state-based actions are checked. |
| A 0/1 with deathtouch would deal normal combat damage | Its power is 0, so it deals no combat damage and deathtouch does nothing. |
| All damage from a deathtouch source is prevented | No damage was dealt, so deathtouch does not destroy the creature. |
| A deathtouch source damages an indestructible creature | Deathtouch attempts to destroy it, but indestructible prevents that destruction. |
| A deathtouch creature damages a planeswalker | The planeswalker loses loyalty normally; deathtouch itself has no additional effect. |
Zero damage is not a tiny amount of damage
A source that would deal 0 damage deals no damage. A 0-power creature with deathtouch therefore does not destroy a blocker through ordinary combat. Reducing a deathtouch creature to 0 power can be an effective combat answer, provided no effect increases its power again before damage.
Power reduction does not shut off every damage ability, however. If an ability independently says that the creature deals a fixed amount—such as 1 damage—the ability does not use the creature’s power unless its text says it does. Kelsien, the Plague, for example, has an activated ability under which Kelsien itself deals 1 damage to a target creature an opponent controls. If Kelsien has deathtouch when that damage is dealt, that 1 damage is enough for deathtouch to apply even if Kelsien’s power is 0.
Prevented damage does not count
If an effect prevents all damage that a deathtouch source would deal, the target was never dealt damage by that source. Deathtouch therefore has nothing to act on. If an effect prevents only part of the damage and at least 1 damage still gets through, deathtouch applies normally.
Protection can matter here because it prevents damage from sources with the protected quality. It can also stop blocking or targeting in the appropriate circumstances. Those are separate parts of the ability, covered in our guide to protection, trample, targeting, and the DEBT mnemonic.
Deathtouch in ordinary combat
Suppose a 1/1 creature with deathtouch is blocked by a 7/7. Unless first strike, prevention, or another effect intervenes, both creatures deal combat damage simultaneously. The 1/1 is likely destroyed for having lethal damage marked on it, while the 7/7 is destroyed because it was dealt damage by a deathtouch source.
This is a trade, not an invulnerability trick. Deathtouch changes what the creature’s damage does; it does not protect the creature from damage coming back.
Multiple blockers
When an attacker is blocked by multiple creatures, its controller divides its combat damage among those blockers. A 2-power attacker with deathtouch can assign 1 damage to each of two blockers. A 1-power attacker cannot somehow stretch one point across two creatures; it can assign that single point to only one blocker.
This makes power increases meaningful even when every positive amount of deathtouch damage is deadly. Going from 1 power to 2 power may not help against one enormous blocker, but it can let the attacker threaten two blockers at once.
Why deathtouch and trample work so well together
Trample allows an attacking creature to assign excess combat damage beyond its blockers. Before assigning damage to the defending player, planeswalker, or battle, the attacker must assign lethal damage to its blockers. For this calculation, any nonzero amount of damage from a source with deathtouch counts as lethal.
Consider a 4/4 with deathtouch and trample blocked by an 8/8. Its controller may assign 1 damage to the blocker and the remaining 3 damage to the defending player. Without deathtouch, all 4 damage would normally need to be assigned to the blocker because that is still less than the blocker’s lethal threshold.
With two blockers, the trampling attacker must assign lethal damage to each before assigning the remainder beyond them. A 5/5 with deathtouch and trample blocked by two ordinary creatures can assign 1 to the first, 1 to the second, and 3 to the defending player.
Indestructible and protection do not change trample assignment
The assignment calculation asks what counts as lethal damage, not whether the blocker will ultimately be destroyed. A deathtouch trampler generally needs to assign only 1 damage to an indestructible blocker before assigning the rest through. The blocker survives because it cannot be destroyed.
The same assignment principle applies when protection will prevent the damage. The attacker can assign 1 damage to the protected blocker and the remainder through; protection then prevents the damage assigned to that blocker. This feels strange because the assigned point was never likely to kill anything, but combat assignment and the eventual damage result are different steps.
First strike and double strike
When first strike or double strike is involved, combat has two combat-damage steps. Creatures with first strike and double strike deal damage in the first one. Surviving creatures that have not already dealt first-strike damage, plus creatures with double strike, deal damage in the second. State-based actions are checked between those steps.
First strike against deathtouch
First strike can neutralize a deathtouch blocker, but only if the first-strike damage actually removes it. If a 2/2 with first strike is blocked by a 1/1 with deathtouch, the 2/2 deals 2 damage in the first damage step. The 1/1 is destroyed before the regular damage step and never deals its deathtouch damage.
Now make the deathtouch creature a 3/3. The 2/2 first striker deals 2 damage, which is not enough to destroy it. The 3/3 survives into the regular damage step, deals damage, and deathtouch destroys the first striker. First strike is timing, not a magical anti-deathtouch force field.
First strike plus deathtouch
A creature with both abilities can destroy an ordinary blocker during the first combat-damage step, before that blocker gets to deal regular combat damage. Even a 1/1 with first strike and deathtouch can do this to a much larger creature, assuming its damage is not prevented and the blocker is not indestructible.
Double strike plus deathtouch
Double strike allows a creature to deal damage in both steps if it remains in combat. If a 1/1 with double strike and deathtouch kills its only blocker during the first step, the attacker remains blocked. Without trample, it does not suddenly deal its second-step damage to the defending player. With trample, it may be able to assign damage beyond the now-absent blocker in the second step.
Additional combat phases repeat the relevant combat structure rather than adding extra damage to an existing step. If that is the engine you are building, see our overview of extra-combat cards in Magic.
Deathtouch versus indestructible and regeneration
Indestructible means a permanent cannot be destroyed. Because deathtouch’s state-based action destroys a creature, an indestructible creature survives deathtouch damage. The damage is still dealt and remains marked until the cleanup step, but neither lethal marked damage nor deathtouch destruction can destroy that creature.
Indestructible does not stop other ways of removing a creature. An indestructible creature can still be exiled, sacrificed, returned to its owner’s hand, or put into a graveyard for having toughness 0 or less. That last event is not destruction.
Regeneration works differently. A regeneration shield can replace the destruction event caused by deathtouch. The creature becomes tapped, its marked damage is removed, and it is removed from combat if applicable. Regeneration cannot save a creature with toughness 0 or less because that creature is put into the graveyard rather than destroyed.
Noncombat damage: identify the source
Deathtouch is not restricted to combat damage. The useful question is always: what object is dealing the damage? If the deathtouch creature is the source, deathtouch can apply. If a separate spell is the source, merely controlling a deathtouch creature does not lend the spell its ability.
| Effect type | Damage source | Does the creature’s deathtouch matter? |
|---|---|---|
| Fight | Each fighting creature deals damage to the other | Yes, for any fighting creature that has deathtouch and deals positive, unprevented damage. |
| Rabid Bite-style effect | The chosen creature deals the damage | Yes. The spell instructs that creature to deal damage. |
| Creature’s own damage ability | The creature named as the source | Yes, if it has deathtouch when the damage is dealt. |
| Separate direct-damage spell | The spell itself | No. A creature elsewhere on the battlefield does not give the spell deathtouch. |
Fighting
A fight is not combat. Each fighting creature deals damage equal to its power to the other creature, normally at the same time. If one has deathtouch and deals at least 1 unprevented damage, the other creature is destroyed when state-based actions are checked. The opposing creature still deals its own damage during the fight, so the deathtouch creature may die too.
One-sided creature damage
Rabid Bite instructs a creature you control to deal damage equal to its power to a target creature you do not control. The chosen creature—not Rabid Bite—is the damage source. Its deathtouch therefore applies, provided it deals positive, unprevented damage. Unlike a fight, the opposing creature does not automatically deal damage back.
This distinction is the whole machine underneath the combo: deathtouch does not make a spell deadly simply because the spell involves your creature. The wording must make that creature the source of the damage.
Does deathtouch destroy planeswalkers?
Ordinary deathtouch does not destroy planeswalkers, battles, or players. If a creature with deathtouch deals 1 damage to a planeswalker, the planeswalker loses one loyalty counter in the normal way. Deathtouch adds nothing to that result. A planeswalker with zero loyalty is then put into its owner’s graveyard as a separate state-based action.
Some cards have additional text that resembles “deathtouch for planeswalkers,” but the additional ability is doing the work. Vraska, Swarm’s Eminence creates Assassin tokens with deathtouch and a separate triggered ability that destroys a planeswalker dealt damage by that creature. The planeswalker is destroyed by the printed trigger, not by deathtouch.
Practical ways to play around deathtouch
Deathtouch is excellent at making combat trades awkward, but it is not unconditional removal. The cleanest answer depends on what is creating the danger.
- Use first strike or double strike when your creature can deal enough early damage to remove the deathtouch creature before regular combat damage.
- Reduce its power to 0 to stop ordinary combat damage. Check whether an ability uses power or specifies a fixed amount of damage.
- Prevent the damage. If no damage is dealt, deathtouch cannot apply.
- Use indestructible when destruction is the problem, while remembering that trample may still carry most of the attacker’s damage through.
- Use disposable creatures or tokens when a trade is unavoidable and preserving a more valuable creature matters more.
- Attack or block around it with appropriate evasion. Flying, menace, and similar abilities change which blocks are available, but none is a universal answer.
- Remove it before combat. If the removal spell targets, hexproof and ward may interfere; blocking itself does not target. Wizards’ keyword glossary summarizes those abilities.
The most common mistake is treating an ability as a blanket answer. First strike works only when the early damage is enough. Evasion works only when the relevant creatures cannot block. Power reduction works only when the damage depends on power. The board state, not the keyword label, decides the outcome.
The reliable deathtouch checklist
When a complicated interaction appears, resolve it in this order:
- Identify the damage source.
- Check whether that source has deathtouch when it deals damage.
- Determine whether it deals at least 1 damage after prevention and replacement effects.
- If combat includes trample, calculate lethal assignment using 1 damage from a deathtouch source for each blocker.
- After damage, check state-based actions. A damaged creature can be destroyed by deathtouch unless indestructible or a replacement effect such as regeneration saves it.
- For planeswalkers, players, and battles, ignore ordinary deathtouch and process the damage normally unless another ability explicitly says otherwise.
Deathtouch feels complicated because it touches several systems at once: damage assignment, timing, prevention, destruction, and state-based actions. Once those systems are separated, the mechanic becomes pleasantly mechanical. Find the source, confirm that positive damage was actually dealt, and then check whether anything prevents the resulting destruction.