Quick Verdict
The legend rule is a state-based action that fires whenever a player controls two or more legendary permanents with the same name — that player chooses one to keep, and the others go to the graveyard. The rule changed substantially in 2013 to be per-player rather than global, which is the version every modern player needs to understand.
The legend rule is the most-asked-about, most-misunderstood rule in modern Magic: The Gathering. It governs how legendary creatures, planeswalkers, artifacts, lands, and enchantments interact when more than one copy hits the battlefield — and the rule has changed twice in major ways since the game launched in 1993.
If you started playing during the Commander boom, the rule has always been "you choose one to keep." If you played during the Urza or Kamigawa blocks, you remember when both copies were destroyed automatically. If you've ever wondered why your opponent's Sliver Legion didn't kill yours, or why two Lilianas can sit on the battlefield at the same time, the answer is buried in the legend rule's evolution.
This guide is the comprehensive reference. Modern rules text from CR 704.5j, the historical evolution explaining why competitive play looks the way it does, and the strategic applications that make the legend rule a feature rather than a bug.
The shortest accurate answer: if you control two or more legendary permanents with the same name, you choose one to keep and the rest go to the graveyard. That's the entire rule.
The Modern Legend Rule (CR 704.5j)
The current legend rule lives in Comprehensive Rules section 704.5j, the section that governs state-based actions. The exact rules text:
CR 704.5j: If a player controls two or more legendary permanents with the same name, that player chooses one of them, and the rest are put into their owners' graveyards. This is called the "legend rule."
Three details define the modern version:
Detail 1: The rule is per-player. It only triggers when one player controls multiple copies of a legendary permanent with the same name. Different players can each control their own copy without conflict.
Detail 2: The controller chooses. When the rule fires, the player who controls the duplicates picks one to keep. The others go to their respective owners' graveyards (which matters for cards like Bribery that put a creature you don't own onto the battlefield under your control).
Detail 3: It's a state-based action. The rule is checked constantly, every time the game checks state — which happens whenever a player would receive priority, before any triggered ability is put on the stack, and before any player takes a game action.
For more on exactly when state-based actions fire and how they interact with the rest of the rules engine, see our MTG state-based actions guide.
The 'Same Name' Test
The legend rule only applies when the names match exactly. Liliana of the Veil and Liliana, Heretical Healer are different cards with different names — both can sit on your battlefield simultaneously. This is why planeswalkers with multiple printings (different subtitles) avoid the rule, while two copies of the same printing trigger it.
How the Modern Rule Triggers
A complete walkthrough of a legend-rule trigger:
Setup. You control Sliver Overlord (legendary creature). Your hand contains a second Sliver Overlord.
Action. You cast the second Sliver Overlord. It resolves and enters the battlefield.
State-based action check. Before the next player receives priority, the game checks state-based actions. It identifies that you control two legendary permanents named Sliver Overlord.
Resolution. You choose which copy to keep. The other goes to your graveyard. Both events happen simultaneously as part of the state-based action check — there is no priority window between them, and you cannot respond to the legend rule.
Aftermath. The state-based action check completes. The active player receives priority. The game continues.
The fact that the legend rule cannot be responded to is critical. You cannot, for example, sacrifice the older copy to a sacrifice outlet in response to the legend rule — there is no response window. The choice and the destruction happen as a single atomic event.
The History: From "Both Die" to "You Choose"
Understanding the legend rule's evolution explains why modern Commander works the way it does and why older cards have their text errata-ed.
1994: Legends set introduces legendary creatures. The original rule was binary: if two legendary creatures with the same name were on the battlefield, both were destroyed. The interaction was symmetric and global — your opponent's Lord Magnus could "trade with" yours by simply being played second.
1999: Sixth Edition rules update. The rule was unified across all legendary permanents (not just creatures). The "both die" mechanic remained.
2013: Magic 2014 Core Set update. Wizards rewrote the legend rule to its modern form. The rule became per-player, and the controller of the duplicates was given a choice rather than forced destruction. The rationale was explicit: Commander had become wildly popular, and the old "I attack you with my Niv-Mizzet, you have your own Niv-Mizzet, both die" interaction was killing the format's fun factor.
2018: Planeswalker uniqueness rule removed. Until 2018, planeswalkers had a separate rule preventing two planeswalkers of the same type (e.g., two "Liliana" planeswalkers regardless of subtitle) from coexisting under the same controller. This was removed; planeswalkers now follow the standard legend rule, which is why you can control Liliana of the Veil and Liliana, Dreadhorde General simultaneously.
2024–2026: No further changes. The 2013 framework remains the active legend rule. Recent printings (Foundations, Spider-Man, March of the Machine sub-blocks) all assume the modern rule.
This evolution matters because pre-2013 cards still exist in formats like Vintage and Commander, and the rules text on those cards reads as if the old rule were active. They've been errata-ed silently by Oracle text — the printed card lies, but the Oracle entry on Gatherer is correct.
What Counts as Legendary
The legend rule applies to all legendary permanents, which is broader than just creatures. The full list:
- Legendary creatures — the most common case (Liliana of the Veil, Sliver Overlord, Atraxa, Praetors' Voice, every Commander-eligible creature).
- Legendary planeswalkers — all planeswalkers are legendary by default, even though the supertype isn't always shown on older printings.
- Legendary artifacts — Sword of the Animist, Aetherflux Reservoir-style legendary artifacts, equipment like Sword of Fire and Ice (which is not legendary; check the actual line).
- Legendary lands — Karakas, Maze of Ith, Strip Mine-style nonbasics. Many Commander-staple lands are legendary.
- Legendary enchantments — less common but exist (Cosmic Intervention, certain Sagas).
The legend rule ignores non-legendary permanents entirely. Two copies of a non-legendary creature can coexist freely; only the supertype "Legendary" triggers the rule.
The Saga Subtype Trap
Sagas are enchantments, not creatures, and they have their own quirks. Most Sagas are not legendary, but some specific Saga cards are (especially crossover product like the Lord of the Rings: Tales of Middle-earth set's The Battle of Bywater). Always read the supertype line to confirm.
Strategic Applications: Weaponizing the Rule
The legend rule isn't just a constraint — it's a tool. Skilled players use it to extract value from their own legendary permanents.
Tactic 1: Re-triggering enters-the-battlefield abilities. Play a legendary creature, get the ETB trigger, play a second copy, choose the new one, send the old one to the graveyard via the legend rule. You've effectively cast the spell twice for one ETB cost. This works well with cards like Sun Titan, Conduit of Worlds, and many Commander legendaries.
Tactic 2: Saving your commander from removal. Your opponent casts Path to Exile on your commander. In response (during the priority window before the spell resolves), play a second copy of your commander. Your opponent's removal still resolves, but you keep one copy — the legend rule sacrifices the other one to your graveyard, and your commander is now safely on the battlefield.
Wait — this doesn't work as described. The legend rule fires immediately upon the second copy entering, before the original's removal resolves. Let me correct: actually, the second copy resolves, the legend rule check sends one to the graveyard, and the original removal then resolves on whichever copy you kept (or fizzles if you kept the new one and your opponent's removal targeted the original, since the original is now in the graveyard).
The cleaner play: cast the second copy as your opponent's removal sits on the stack. Choose to send the original (the targeted one) to the graveyard via the legend rule. The removal spell now has no legal target and fizzles on resolution.
Tactic 3: Token copy abuse. Token copies of legendary permanents trigger the legend rule. Mirage Mirror copying your legendary creature creates a duplicate; you sacrifice the token to the legend rule and keep your original. This lets you "use" the Mirror for its activated ability without long-term cost.
Tactic 4: Combo lines via repeatable death triggers. Pestilent Spirit + Yawgmoth, Thran Physician in a Commander aristocrat shell: each death trigger creates value, and the legend rule lets you re-cast the same legendary creature multiple times across a long game.
For more on Commander deck building principles that account for the legend rule, see our best Magic: The Gathering Commander decks ranking.
Format-by-Format Verdict
Standard. Legendary creatures are common in Standard sets. The legend rule rarely comes up in matches because deck composition usually limits you to one or two copies of any specific legendary card. When it does fire, it's usually a positive ETB re-trigger.
Pioneer / Modern. Legend rule interactions are more common because midrange decks frequently run two copies of a legendary creature (e.g., Geist of Saint Traft in Pioneer when it was legal, Wrenn and Six in Modern). Players time their second copies to trigger ETB effects deliberately.
Commander. The legend rule is foundational to the format. Every commander is legendary by definition, and the per-player nature of the rule means multiple players can run the same commander archetype without conflict. The rule's strategic depth — sacrificing your own commander to refresh ETB effects, killing your opponent's commander through tokens — defines high-level Commander play.
Legacy / Vintage. Legacy is where pre-2013 legend rule interactions used to matter most. Old cards with errata-ed text still confuse newer players. Vintage tournaments frequently see judge calls about Oracle text vs printed text on legendary cards.
Common Misconceptions
Misconception 1: "Two Lilianas can't be on the battlefield." Wrong if they have different names (different subtitles). Liliana of the Veil and Liliana, Heretical Healer are separate cards. The legend rule only triggers on identical names.
Misconception 2: "If my opponent plays my commander, the legend rule kills both." Wrong on multiple counts. The legend rule is per-player. If your opponent steals your commander and you cast another copy yourself, you each control one — no rule fires. If your opponent plays a second copy after stealing yours, they control two and choose one to keep; you're unaffected.
Misconception 3: "I can respond to the legend rule by sacrificing the older copy." Wrong. State-based actions are atomic and don't use the stack. There is no response window. The choice and the destruction are one event.
Misconception 4: "Token copies don't trigger the legend rule." Wrong. Token copies have the same name as the original (CR 707), so they trigger the rule. Sacrificing the token to the rule is the standard play.
For a deeper look at how the legend rule interacts with Commander damage and the command zone, see our MTG vigilance guide, which touches on combat-step priority windows where legend rule interactions often matter.
The Legend Rule and Replacement Effects
A subtle interaction: if you'd be put into a position where the legend rule would fire, replacement effects can intercept before the rule kicks in.
Example: Commander to command zone. When your commander would be put into your graveyard from the battlefield (because the legend rule sent it there), you may instead put it into the command zone (CR 903.9). This is a replacement effect, and it applies before the legend rule's "go to graveyard" event fully completes. Effectively, you can save your commander from your own legend rule by routing it to the command zone instead.
Example: Indestructible plus legend rule. Indestructible doesn't help. The legend rule destroys via direct movement to the graveyard, not via combat damage or destroy effects. Indestructible only protects against effects that say "destroy." The legend rule moves the card directly, bypassing destruction.
This matters because aggressive Commander players frequently exploit the command zone replacement to refresh their commander whenever the legend rule fires — paying the increased commander tax instead of losing the card to the graveyard.
The Bottom Line
The legend rule is a state-based action that triggers when one player controls two or more legendary permanents with the same name. The controller picks one to keep; the rest go to the graveyard. The rule is per-player (you and your opponent can each control your own copy without conflict), atomic (no response window), and applicable to all legendary permanents — creatures, planeswalkers, lands, artifacts, and enchantments.
The 2013 update from "both die globally" to "controller chooses, per-player" was the single biggest rules change in modern Magic, made specifically to enable Commander as a long-form format. Mastering the rule unlocks a layer of strategic decisions — when to play a second copy, how to weaponize ETB triggers, when to sacrifice tokens to refresh originals — that defines Commander deck construction in 2026.
Frequently Asked Questions
🔗 Related Resources
More Reviews:
Related Articles
.jpg)
Hexproof vs Shroud MTG: The Complete Difference Explained (2026)
Hexproof vs Shroud in Magic: The Gathering — what the two abilities actually do, why they're not the same, and which one is stronger in 2026 Commander, Modern, and Standard play.
.png)
MTG Persist vs Undying: The Complete Mechanic Comparison (2026)
Persist vs Undying in Magic: The Gathering — the rules, counter interactions, combo applications, and which one is stronger in 2026 Modern, Commander, and Pioneer.
.png)
MTG The Stack Explained: How Spells and Abilities Resolve (2026)
How does the stack work in Magic: The Gathering? A complete rules guide to MTG's stack mechanic — last-in, first-out resolution, priority windows, and the interactions every player must understand.

.png)