The Legendary Rule in Magic: The Gathering Explained

The legendary rule is one of Magic: The Gathering's oldest and most consequential state-based actions, governing what happens when a player controls two or more permanents that share a legendary supertype and an identical name. It affects commanders, planeswalkers in some contexts, and a significant portion of the most powerful cards ever printed. Understanding exactly when it triggers, how players navigate it, and where its edges get genuinely strange is essential to playing the game correctly at any level.

Definition and scope

The legendary rule is a state-based action defined in the Magic: The Gathering Comprehensive Rules — specifically rule 704.5j, which states that if a player controls two or more legendary permanents with the same name, that player chooses one and puts the rest into their owners' graveyards.

A few things are worth unpacking immediately. The rule applies to the legendary supertype, not to a creature type or card type alone. A card is legendary because it carries that printed designation — kings, artifacts, enchantments, lands, and planeswalkers can all be legendary. The rule also fires on name, not on card identity in any broader sense. Two legendaries with different names, even if they're the same character at different points in a story, coexist without any friction.

The supertype applies across all card types and subtypes that can bear it. Legendary lands, legendary artifacts like the Mirari, legendary enchantments — all fall under the same state-based action. This isn't just flavor. It shapes deck construction in Commander format, where 99 of 100 cards in a deck are required to be singleton, partly because the format is built around legendary creatures as commanders.

How it works

State-based actions in Magic don't use the stack. They're checked by the game automatically, before any player receives priority, any time a player would receive priority. The legendary rule fires at that moment — not when a second legendary enters the battlefield, but immediately as the game checks its own health.

Here's the sequence:

That word owners matters. If the second legendary came from the opponent's deck (via a theft effect, for example), the legendary that goes to the graveyard goes to the owner's graveyard — not necessarily the controller's.

Also notable: the rule is checked per player, not globally. Two different players can each control a legendary permanent with the same name without any conflict. The rule only fires when one player controls multiple copies. This comes up constantly in Commander format multiplayer games, where 4 players at a table might each have their own Urza's Saga in play simultaneously.

Common scenarios

Commander and the legend rule: In Commander, the legendary rule still applies to non-commander permanents. If a commander ability or spell puts a legendary creature onto the battlefield and a player already controls that creature, the rule fires. Commanders have a special replacement effect — the command zone — but that applies only when a commander would go to a graveyard or be exiled, not as an override of the legendary rule itself.

Clones: One of the trickiest intersections involves Clone-type creatures that copy a legendary permanent. If a player controls Sigarda, Host of Herons and then copies it with a Clone, that player now controls two permanents named Sigarda, Host of Herons — and must sacrifice one. Notably, the player chooses which one to keep. This means a Clone copying a legendary can immediately cause the original to go to the graveyard, which is sometimes the entire point of the play.

Legendary lands: Legendary lands like Karakas or Dark Depths are subject to the same rule. Two Karakas in play under the same player means one goes to the graveyard. Unlike creatures, there's no commander zone to catch them. This has direct implications in Legacy format, where Karakas sees significant competitive play.

Sagas and other legendary enchantments: Legendary Sagas follow the same rule. If a second copy of a Saga enters while the first is still on the battlefield, the player keeps one. The lore counter count on the surviving copy is unchanged by the rule's application.

Decision boundaries

The rule offers genuine strategic texture because the player chooses which copy survives. This isn't symmetrical in practice.

The two most relevant contrasts:

• Fresh copy vs. spent copy: A newly entered legendary arrives without summoning sickness effects already applied, without -1/-1 counters accumulated, without abilities already activated. Keeping the fresh copy is often correct. Keeping the old one might preserve lore counters already accrued on a Saga, or loyalty counters on a legendary planeswalker.

• Triggered abilities already on the stack: The legendary rule fires before priority, but if the entering legendary triggered an ability, that trigger is already waiting on the stack. Sending that permanent to the graveyard doesn't remove the trigger. The ability still resolves.

The judge program and rules enforcement framework treats failure to apply state-based actions as a game rules violation, and at competitive events, players are responsible for recognizing when the rule applies — not just opponents and judges.

The legendary rule sits at an intersection that's worth knowing deeply: part game rule, part deckbuilding constraint, part live tactical decision. The comprehensive rules overview and format-specific contexts like Commander add further wrinkles that can make the same rule behave very differently depending on where the game is being played.