{"id":1461,"date":"2026-08-05T06:51:15","date_gmt":"2026-08-05T06:51:15","guid":{"rendered":"https:\/\/krakenthemeta.com\/blog\/mtg-legend-rule\/"},"modified":"2026-08-05T06:51:15","modified_gmt":"2026-08-05T06:51:15","slug":"mtg-legend-rule","status":"publish","type":"post","link":"https:\/\/krakenthemeta.com\/blog\/mtg-legend-rule\/","title":{"rendered":"MTG Legend Rule Explained: What It Actually Says, Every Way Around It, and the Cards That Break It (2026)"},"content":{"rendered":"
The legend rule is one line long, it has not meaningfully changed since 2013, and it is still the most consistently mis-explained rule in Magic. Search for it and you will be told that you may only run four legendary cards in a deck (there is no such rule), that it only applies to creatures (it applies to every legendary permanent), that both copies die (they have not since 2013), and that the loser goes to some kind of limbo (it goes to the graveyard).<\/p>\n\n
So here is the rule, quoted from the source, followed by everything that actually trips people up: how it resolves, why you cannot respond to it, the exact difference between “same name” and “same character,” all nine cards in Magic that switch it off, the legal ways to make copies of your legends anyway, and the traps that quietly kill your board.<\/p>\n\n
Every rule below is quoted verbatim from the official Magic: The Gathering Comprehensive Rules<\/strong>, effective 7 August 2026. Every card is verified against the live Scryfall database \u2014 oracle text, type line, and format legality at the time of writing.<\/p>\n\n
The legend rule, in one sentence<\/h2>\n\n
CR 704.5j<\/strong> \u2014 “If two or more legendary permanents with the same name are controlled by the same player, that player chooses one of them, and the rest are put into their owners’ graveyards. This is called the ‘legend rule.'”<\/p><\/blockquote>\n\n
Four things are load-bearing in that sentence, and each one is a myth-killer:<\/p>\n\n
\n
“legendary permanents”<\/strong> \u2014 not “creatures.” Lands, artifacts, enchantments, planeswalkers and battles are all included.<\/li>\n
“with the same name”<\/strong> \u2014 name, not character, not card. This is the one that matters most this month.<\/li>\n
“controlled by the same player”<\/strong> \u2014 you and your opponent can each have your own. This is the 2013 change.<\/li>\n
“that player chooses”<\/strong> \u2014 you pick the survivor, and you may keep the one you just played.<\/li>\n<\/ul>\n\n
The supertype rule confirms the scope explicitly:<\/p>\n\n
CR 205.4d<\/strong> \u2014 “Any permanent with the supertype ‘legendary’ is subject to the state-based action for legendary permanents, also called the ‘legend rule’ (see rule 704.5j).”<\/p><\/blockquote>\n\n
Four things the top search results still get wrong<\/h2>\n\n
This is not a strawman. These are claims sitting on page one and page two for this exact query right now.<\/p>\n\n
\n
What you’ll read<\/th>
What the rules actually say<\/th><\/tr><\/thead>\n
\n
“You’re only allowed four legendary cards in your deck, and no copies of the same one.”<\/td>
No such rule exists.<\/strong> Deck limits come from format rules \u2014 four copies of a card in Constructed, one copy in Commander singleton. The legend rule is about the battlefield<\/em>, not the deck. You can run four copies of a legendary creature in Standard and that is completely legal.<\/td><\/tr>\n
“No two legendary creatures<\/em> with the same name.”<\/td>
CR 205.4d applies it to every legendary permanent<\/strong>. Two copies of a legendary land, artifact, enchantment or planeswalker collide exactly the same way.<\/td><\/tr>\n
“If two are on the battlefield, all are put into their owners’ graveyards.”<\/td>
That was the pre-2013 rule and it checked the whole battlefield. Today it is per player<\/strong>, and only the extras die \u2014 you keep one.<\/td><\/tr>\n
“The extra copy goes into a limbo zone.”<\/td>
It goes to the graveyard<\/strong>. There is no limbo zone. It can be reanimated, it triggers death triggers, and it fills your yard for delirium and threshold.<\/td><\/tr>\n
“There’s also a planeswalker uniqueness rule.”<\/td>
Removed.<\/strong> CR 306.4: “This rule has been removed and planeswalker cards printed before this change have received errata.” Two different<\/em> Jace planeswalkers coexist fine.<\/td><\/tr>\n<\/tbody>\n<\/table>\n\n
That last one deserves a moment. The planeswalker uniqueness rule used to stop you controlling two planeswalkers sharing a planeswalker type \u2014 two Jaces, two Chandras \u2014 regardless of name. It is gone. The rules file is blunt about it: “This rule was called the ‘planeswalker uniqueness rule’ and no longer exists.” Old cards were errata’d. Today planeswalkers follow the same legend rule as everything else, which is why Jace, Vryn’s Prodigy<\/strong> and Jace, Telepath Unbound<\/strong> can share a battlefield with any other differently-named Jace.<\/p>\n\n
How it actually resolves \u2014 and why you can’t respond<\/h2>\n\n
The legend rule is a state-based action<\/em>. That single word answers most of the follow-up questions people ask, because state-based actions do not use the stack and nobody gets a window.<\/p>\n\n
CR 117.5<\/strong> \u2014 “Each time a player would get priority, the game first performs all applicable state-based actions as a single event\u2026 Then the player who would have received priority does so.”<\/p><\/blockquote>\n\n
So the sequence is fixed:<\/p>\n\n
\n
Step<\/th>
What happens<\/th><\/tr><\/thead>\n
\n
1<\/td>
Your second copy of a legend finishes entering the battlefield.<\/td><\/tr>\n
2<\/td>
Before any<\/em> player would receive priority, the game checks state-based actions.<\/td><\/tr>\n
3<\/td>
The legend rule applies. You<\/strong> choose which one survives.<\/td><\/tr>\n
4<\/td>
The rest are put into their owners’ graveyards. Nothing goes on the stack, so nothing can be responded to.<\/td><\/tr>\n
5<\/td>
Any death triggers from step 4 go on the stack. Now<\/em> a player gets priority.<\/td><\/tr>\n<\/tbody>\n<\/table>\n\n
“If there are exactly two permanents named Brothers Yamazaki on the battlefield, the ‘legend rule’ doesn’t apply to them”<\/td>
Exactly two \u2014 a third still dies<\/td><\/tr>\n<\/tbody>\n<\/table>\n\n
Three details worth pulling out. Mirror Gallery is symmetric<\/strong> \u2014 its oracle text is four words long and contains no “you control” clause, so in a four-player pod you have just handed everyone permission to double up on their own legends. Mirror Box is the strictly-better card for most decks<\/strong>: it is two mana cheaper, one-sided, and adds two anthem effects on top. And Brothers Yamazaki<\/strong> is the strangest card in Magic’s rules text \u2014 it works at exactly two and breaks at three.<\/p>\n\n
The legal way around it: make the copy nonlegendary<\/h2>\n\n
You do not need to switch the rule off. You need the copy to not share a name \u2014 or to not be legendary in the first place. Copy effects normally hand you the problem, because copying grabs the supertype:<\/p>\n\n
CR 707.2<\/strong> \u2014 “The copiable values are the values derived from the text printed on the object (that text being name, mana cost, color indicator, card type, subtype, supertype<\/strong>, rules text, power, toughness, and\/or loyalty)\u2026 Other effects (including type-changing and text-changing effects), status, counters<\/strong>, and stickers are not copied.”<\/p><\/blockquote>\n\n
So a plain Clone<\/strong> copying your legend is legendary, shares the name, and immediately dies to the legend rule. These cards solve that by writing an exception into their own text:<\/p>\n\n
\n
Card<\/th>
Mana<\/th>
The exception clause<\/th>
Price<\/th><\/tr><\/thead>\n
\n
Helm of the Host<\/strong><\/td>
{4}<\/td>
“create a token that’s a copy of equipped creature, except the token isn’t legendary<\/strong>” \u2014 every combat, permanently<\/td>
$5.14<\/td><\/tr>\n
Spark Double<\/strong><\/td>
{3}{U}<\/td>
Copy a creature or planeswalker<\/em> you control, “and it isn’t legendary<\/strong>” \u2014 plus an extra +1\/+1 or loyalty counter<\/td>
$13.92<\/td><\/tr>\n
Irenicus’s Vile Duplication<\/strong><\/td>
{3}{U}<\/td>
Token copy of a creature you control, “the token has flying and it isn’t legendary<\/strong>“<\/td>
$12.46<\/td><\/tr>\n
Vesuvan Duplimancy<\/strong><\/td>
{3}{U}<\/td>
Whenever you target a single artifact or creature you control, token copy, “it’s not legendary<\/strong>” \u2014 repeatable<\/td>
$6.05<\/td><\/tr>\n
Sakashima the Impostor<\/strong><\/td>
{2}{U}{U}<\/td>
Copies any creature “except its name is Sakashima the Impostor<\/strong>” \u2014 different name, so no collision<\/td>
$18.17<\/td><\/tr>\n
Godo, Bandit Warlord<\/strong><\/td>
{5}{R}<\/td>
Not an exception itself \u2014 it tutors<\/em> Helm of the Host onto the battlefield on cast<\/td>
$1.20<\/td><\/tr>\n<\/tbody>\n<\/table>\n\n
Sakashima the Impostor is the elegant one: it does not turn off a rule, it simply keeps its own name. That is enough. Helm of the Host is the workhorse \u2014 it is in nearly every Voltron and combat-focused list for a reason, and we cover the whole category in our best equipment in MTG guide<\/a>.<\/p>\n\n
Moritte of the Frost<\/strong> \u2014 {2}{G}{U}{U}<\/td>
Copies a permanent you control “except it’s legendary<\/strong> and snow in addition to its other types.” It adds<\/em> the supertype. Copy your own legend and one of them dies immediately. Copy a nonlegendary<\/em> permanent and it is fine.<\/td><\/tr>\n
Sakashima’s Will<\/strong> \u2014 {3}{U}<\/td>
Mode two: “Each other creature you control becomes a copy of that creature until end of turn.” Choose a legendary<\/strong> creature and your whole board now shares one name \u2014 the legend rule kills all but one. Choose a nonlegendary creature instead.<\/td><\/tr>\n
Blade of Selves<\/strong> \u2014 {2}<\/td>
Myriad creates token copies attacking each opponent. On a legendary creature those tokens are legendary with the same name and die instantly to the legend rule. Needs Mirror Gallery, Mirror Box or Cadric to work at all.<\/td><\/tr>\n
Rite of Replication<\/strong> \u2014 {2}{U}{U}<\/td>
Kicked for five tokens on a legendary creature returns exactly one survivor. On a nonlegendary<\/em> bomb it is one of the best cards in Commander.<\/td><\/tr>\n
Followed Footsteps<\/strong> \u2014 {3}{U}{U}<\/td>
A token copy every upkeep. On a legend that is one copy every turn that dies the moment it arrives.<\/td><\/tr>\n
Minsc & Boo, Timeless Heroes<\/strong><\/td>
Creates “Boo<\/strong>, a legendary 1\/1 red Hamster creature token.” Tokens obey the legend rule too \u2014 you cannot stockpile Boos.<\/td><\/tr>\n
All straight copy effects with no legendary exception. Fine on opponents’ legends (the rule is per-player), fatal on your own.<\/td><\/tr>\n<\/tbody>\n<\/table>\n\n
The single most important consequence of “controlled by the same player”:<\/strong> copying an opponent’s<\/em> legendary creature does not kill theirs. You each control one. Players still misplay this constantly, expecting a Clone to two-for-one an opposing commander.<\/p>\n\n
Using the legend rule on purpose<\/h2>\n\n
The rule is also a resource. The classic version is a two-card land combo that reads like a bug and is entirely intentional.<\/p>\n\n
Dark Depths + Thespian’s Stage: the legend rule is the disposal mechanism, not the obstacle.<\/figcaption><\/figure>\n\n
Dark Depths + Thespian’s Stage.<\/strong> Dark Depths is a Legendary Snow Land that enters with ten ice counters and only makes a 20\/20 flying indestructible Marit Lage when it has none. Paying {3} ten times is not a plan. Instead:<\/p>\n\n\n
Play Dark Depths<\/strong> (it enters with ten ice counters).<\/li>\n
Play Thespian’s Stage<\/strong> and activate “{2}, {T}: This land becomes a copy of target land,” targeting Dark Depths.<\/li>\n
Per CR 707.2, counters are not copied<\/strong> \u2014 so the Stage becomes a Dark Depths with zero<\/em> ice counters.<\/li>\n
Both are now legendary lands named Dark Depths that you control, so the legend rule fires. You choose<\/strong> \u2014 keep the copy with no counters.<\/li>\n
That copy has no ice counters, so its own trigger sacrifices it and you get Marit Lage.<\/li>\n<\/ol>\n\n
The legend rule is not an obstacle here, it is the disposal mechanism. Note the legality: Dark Depths is banned in Modern<\/strong>, and legal in Commander, Legacy and Vintage.<\/p>\n\n
The other deliberate use is the legendary-matters payoff shell \u2014 Mox Amber<\/strong> only produces mana if you control legendary creatures or planeswalkers, the Kamigawa channel lands cost {1} less to activate per legendary creature you control, and legendary sorceries cannot be cast at all without one.<\/p>\n\n
Legendary lands worth playing<\/h2>\n\n
Every one of these is subject to the legend rule, which almost never matters in Commander singleton \u2014 until someone copies one with Vesuva or Thespian’s Stage.<\/p>\n\n
\n
Land<\/th>
What it does<\/th>
Price<\/th><\/tr><\/thead>\n
\n
Gaea’s Cradle<\/strong><\/td>
“{T}: Add {G} for each creature you control.” The best land in green go-wide decks and priced accordingly<\/td>
$1,662.92<\/td><\/tr>\n
Serra’s Sanctum<\/strong><\/td>
{W} for each enchantment you control \u2014 the enchantress equivalent<\/td>
$501.40<\/td><\/tr>\n
Urborg, Tomb of Yawgmoth<\/strong><\/td>
“Each land is a Swamp in addition to its other land types”<\/td>
![\"Three](\"https:\/\/krakenthemeta.com\/blog\/wp-content\/uploads\/2026\/08\/kraken-img-1785912470-mtg-legend-rule-names-1.jpg\")
![\"Mirror](\"https:\/\/cards.scryfall.io\/art_crop\/front\/0\/0\/00beba34-54cc-4a30-8424-71a1215647a6.jpg?1783944177\")
![\"Two](\"https:\/\/krakenthemeta.com\/blog\/wp-content\/uploads\/2026\/08\/kraken-img-1785912527-mtg-legend-rule-depths-1.jpg\")