MTG Legend Rule Explained: What It Actually Says, Every Way Around It, and the Cards That Break It (2026)

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).

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.

Every rule below is quoted verbatim from the official Magic: The Gathering Comprehensive Rules, effective 7 August 2026. Every card is verified against the live Scryfall database — oracle text, type line, and format legality at the time of writing.

The legend rule, in one sentence

CR 704.5j — “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.'”

Four things are load-bearing in that sentence, and each one is a myth-killer:

• “legendary permanents” — not “creatures.” Lands, artifacts, enchantments, planeswalkers and battles are all included.
• “with the same name” — name, not character, not card. This is the one that matters most this month.
• “controlled by the same player” — you and your opponent can each have your own. This is the 2013 change.
• “that player chooses” — you pick the survivor, and you may keep the one you just played.

The supertype rule confirms the scope explicitly:

CR 205.4d — “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).”

Four things the top search results still get wrong

This is not a strawman. These are claims sitting on page one and page two for this exact query right now.

That last one deserves a moment. The planeswalker uniqueness rule used to stop you controlling two planeswalkers sharing a planeswalker type — two Jaces, two Chandras — 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 and Jace, Telepath Unbound can share a battlefield with any other differently-named Jace.

How it actually resolves — and why you can’t respond

The legend rule is a state-based action. 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.

CR 117.5 — “Each time a player would get priority, the game first performs all applicable state-based actions as a single event… Then the player who would have received priority does so.”

So the sequence is fixed:

Two consequences people get wrong at the table. First, you cannot respond to the legend rule — there is no window between the copy arriving and the extra dying, so you cannot sacrifice the old one for value “in response.” Second, you may keep the new one. Nothing forces you to keep the older permanent, which matters when the new copy is untapped, has a counter on it, or entered as a copy of something better. If you want the details of how priority and state-based actions interact, our guide to flash, priority and the stack walks the whole timing system, and our indestructible guide covers the other state-based actions that put permanents in the graveyard without destroying them — indestructible does not save a creature from the legend rule, because the legend rule never destroys anything.

“Same name” is not “same character” — and The Hobbit is about to prove it

This is the single most useful thing in this article for the next two weeks. The rule keys on name, and the rules define that narrowly:

CR 201.2a — “Two or more objects have the same name if they have at least one name in common, even if one or more of those objects have additional names.”

Two cards depicting the same character with different card names are, as far as Magic is concerned, two completely different permanents. The Hobbit (set code HOB, released 14 August 2026, 321 cards) is going to put that in front of every table during prerelease weekend, because it prints multiple differently-named versions of the same characters.

Three Bilbos on your battlefield at once is completely legal. So is a board with all three Gandalfs. The set contains 55 legendary cards across creatures, equipment and adventures, and the character-name overlap is dense enough that this will come up on day one of prerelease. If you are drafting or playing Sealed with it, our The Hobbit set guide covers the products and mechanics, and the best Hobbit commanders breakdown ranks the legends for EDH.

One honesty note: because The Hobbit does not release until 14 August 2026, Scryfall currently reports every card in the set as not yet legal in Commander. They become legal on the release date, not at prerelease.

Every card in Magic that turns the legend rule off

There are exactly nine cards whose text references the legend rule. Only one of them switches it off for everybody.

Three details worth pulling out. Mirror Gallery is symmetric — 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: it is two mana cheaper, one-sided, and adds two anthem effects on top. And Brothers Yamazaki is the strangest card in Magic’s rules text — it works at exactly two and breaks at three.

The legal way around it: make the copy nonlegendary

You do not need to switch the rule off. You need the copy to not share a name — or to not be legendary in the first place. Copy effects normally hand you the problem, because copying grabs the supertype:

CR 707.2 — “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, rules text, power, toughness, and/or loyalty)… Other effects (including type-changing and text-changing effects), status, counters, and stickers are not copied.”

So a plain Clone 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:

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 — 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.

The traps: cards that kill your own board

These are the ones that cost games, because each looks like a copy effect and none of them has the “isn’t legendary” clause.

The single most important consequence of “controlled by the same player”: copying an opponent’s 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.

Using the legend rule on purpose

The rule is also a resource. The classic version is a two-card land combo that reads like a bug and is entirely intentional.

Dark Depths + Thespian’s Stage. 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:

1. Play Dark Depths (it enters with ten ice counters).
2. Play Thespian’s Stage and activate “{2}, {T}: This land becomes a copy of target land,” targeting Dark Depths.
3. Per CR 707.2, counters are not copied — so the Stage becomes a Dark Depths with zero ice counters.
4. Both are now legendary lands named Dark Depths that you control, so the legend rule fires. You choose — keep the copy with no counters.
5. That copy has no ice counters, so its own trigger sacrifices it and you get Marit Lage.

The legend rule is not an obstacle here, it is the disposal mechanism. Note the legality: Dark Depths is banned in Modern, and legal in Commander, Legacy and Vintage.

The other deliberate use is the legendary-matters payoff shell — Mox Amber 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.

Legendary lands worth playing

Every one of these is subject to the legend rule, which almost never matters in Commander singleton — until someone copies one with Vesuva or Thespian’s Stage.

Honesty flag: Tolarian Academy is banned in Commander (and in Legacy; restricted in Vintage). It shows up on most “best legendary lands” lists and you cannot play it in EDH. If you are building a mana base, our complete EDH mana base guide covers the legal options in depth. Prices in this article were pulled at the time of writing and legendary lands move fast — check current numbers with our card price tool before you buy.

Legendary sorceries

A Dominaria-era card type gated behind the legend rule’s ecosystem. Each one carries the same reminder text: “You may cast a legendary sorcery only if you control a legendary creature or planeswalker.”

Urza’s Ruinous Blast is the standout and it is under a dollar. In a deck built around legends it is a board wipe that leaves your side almost untouched — see our board wipe guide for how it compares to the symmetric options.

The legend rule in Commander

Commander is singleton, so you cannot draw a second copy of your own legend. The rule still comes up in three ways: copy effects, token copies, and the format’s own state-based action.

CR 903.9a — “If a commander is in a graveyard or in exile and that object was put into that zone since the last time state-based actions were checked, its owner may put it into the command zone. This is a state-based action.”

That is the same state-based action check that runs the legend rule. If your commander is the permanent that loses the legend-rule choice, it goes to the graveyard — and you may then move it to the command zone. You do not lose it. Command Beacon ({T}, sacrifice: put your commander into your hand from the command zone) is the standard answer to escalating commander tax if you would rather recast it cheaply.

The other Commander-specific note: partner commanders like Sakashima of a Thousand Faces let you run two commanders, and Sakashima brings a legend-rule shutoff into the command zone where it is always available.

The world rule: the legend rule’s meaner sibling

Almost nobody knows this one exists. There are exactly 26 cards with the world supertype in paper Magic, and every one of them is a World Enchantment.

CR 704.5k — “If two or more permanents have the supertype world, all except the one that has had the world supertype for the shortest amount of time are put into their owners’ graveyards. In the event of a tie for the shortest amount of time, all are put into their owners’ graveyards. This is called the ‘world rule.'”

In practice this means World Enchantments are self-replacing: play yours and it evicts whatever was there before. They are also mostly expensive Reserved List cards.

A legendary-matters core package

If you want to build around the rule rather than around it, this is the compact shell — the shutoffs, the nonlegendary-copy makers, the payoffs, and the mana.

Two notes on the build. Blade of Selves is deliberately excluded unless you already have Mirror Gallery, Mirror Box or Cadric on the battlefield — without one of them, myriad on a legendary creature produces tokens that die on arrival. And Mox Amber is only a Mox in a deck with a high legendary-permanent count; in anything else it is a blank artifact. If you want to sanity-check a list before you buy it, our deck analyzer will flag the curve and color problems, and you can browse community decklists for full builds.

Frequently asked questions

How many legendary creatures can I have in my deck?

As many as the format allows for any card — four copies of each in Constructed, one of each in Commander singleton. There is no cap on legendary cards specifically. The legend rule only cares about permanents on the battlefield.

Can two players each have the same legendary creature?

Yes. CR 704.5j says “controlled by the same player.” Since the 2013 change, you and your opponent can each control your own copy indefinitely.

Does the legend rule apply to tokens?

Yes. Tokens are permanents, and if a token is legendary and shares a name with another legendary permanent you control, the rule applies. Boo from Minsc & Boo is the common example. This is why “except the token isn’t legendary” appears on so many cards.

Which copy dies — the old one or the new one?

Whichever you choose. You are the controller, you make the choice, and you can keep the newly arrived one.

Can I respond to the legend rule?

No. It is a state-based action, it does not use the stack, and CR 117.5 puts it before any player receives priority. You cannot sacrifice the extra copy for value in response.

Does the extra copy go to the graveyard or exile?

The graveyard, always — “put into their owners’ graveyards.” It triggers death triggers and can be reanimated normally.

Do two different cards of the same character collide?

Only if they share a card name. Bilbo Baggins, Burglar and Bilbo, Thief in the Night are different names, so you can control both.

Is there still a planeswalker uniqueness rule?

No. CR 306.4 states it has been removed and affected cards were errata’d. Planeswalkers follow the ordinary legend rule.

What happens if my commander loses the legend-rule choice?

It is put into your graveyard, and CR 903.9a then lets you move it to the command zone as a state-based action. You do not lose it.

Does copying an opponent’s legendary creature kill theirs?

No. The rule is per player. You control your copy, they control theirs, and both survive.