MTG Layers Explained (Without Making You Regret Learning to Read)

At some point, every Magic player experiences the same emotion:

“Okay, so my creature is a land, but also not a land, it’s white, but also not white, it lost its abilities, but it still has… an ability? And it’s a 1/1 unless it’s a 4/4, except it’s also getting +1/+1. Cool. Totally normal.”

That feeling is layers.

The layer system is how Magic decides what a permanent “really” is when multiple continuous effects try to rewrite it at the same time. If you’ve ever watched anthem effects + type changes + copy effects turn into rules soup, layers are the ladle that puts the soup back in the bowl.

You don’t need to memorize every rule number to use this. You just need the mental model: Magic applies continuous effects in a fixed order, and when effects fight inside the same step of that order, timestamps and dependency decide who wins.

Quick links to additional resources before we dive in:

What layers are (in plain English)

Layers are a rule-driven checklist the game runs through to determine an object’s characteristics after you start with its printed text (or token definition), then apply all relevant continuous effects. The rules describe this as applying effects “in a series of layers” in a specific order.

This matters because continuous effects don’t “resolve” like spells. They just apply while they exist. Layers are the ordering system that keeps that from becoming a free-for-all.

The 7 layers (the order Magic uses)

Magic applies continuous effects in this order (high-level version):

Layer 1: Copy effects

This is where “it’s a copy of X” is established. Copy effects happen early because they define the baseline “copiable values.”

Why it matters: If something copies a creature, and later something gives “creatures you control +1/+1,” the copy happens first, buffs happen later.

Layers 2–6: The “identity” layers

These are the layers where the game changes what the object is before it messes with numbers.

Layer 2: Control-changing effects (who controls it)
Layer 3: Text-changing effects (the card’s rules text gets edited)
Layer 4: Type-changing effects (creature, land, artifact… and subtypes)
Layer 5: Color-changing effects
Layer 6: Ability-adding/removing effects (flying, lifelink, “loses all abilities,” etc.)

(You don’t need to memorize the exact list to benefit—just know that “what it is” gets decided before “how big it is.”)

Layer 7: Power/Toughness changes

Finally, the game applies effects that change power and toughness, and it does so in sub-layers (7a, 7b, etc.). Importantly, within those sublayers, effects are applied in timestamp order, unless dependency changes the order.

Why it matters: This is where “base P/T set to 1/1” and “gets +1/+1” are separated so they don’t randomly cancel each other depending on table mood.

The rule of thumb that saves your sanity

When continuous effects are involved, ask:

Is this a copy effect? (Layer 1)
Is this changing what it is? (Layers 2–6)
Is this changing how big it is? (Layer 7)

Most game situations that feel like “I can’t believe this is real” become predictable once you sort effects into those buckets.

Timestamps: when two effects collide in the same layer

Inside a layer (or sublayer), Magic usually uses timestamp order: earlier effects apply first, later effects apply after. The rules spell this out: within a layer or sublayer, effects are “usually” applied in timestamp order.

The practical version

If two effects do the same kind of thing in the same layer—like:

one effect says “creature is blue”
another effect says “creature is red”

…the later one tends to “win” because it’s applied after the earlier one.

Dependency: the exception that overrides timestamps

Dependency is the “hold up, order actually matters here” system.

If one continuous effect’s result changes what another effect applies to (or what it does), then the dependent one waits and applies after the one it depends on—even if its timestamp is earlier. The rules explicitly say dependency can override the timestamp system.

Why dependency exists (the human explanation)

Sometimes applying effect A first changes whether effect B even makes sense. So the game forces a logical ordering rather than “who entered first.”

What if dependency loops?

If effects form a dependency loop, the game falls back to timestamp order for that loop.

Why anthem effects + type changes + copying turns into soup

Let’s translate the classic “board state soup” into layers language.

Soup ingredient 1: Anthems (buffs)

“Creatures you control get +1/+1” is a continuous effect that modifies P/T, so it lives in Layer 7 (P/T-changing effects).

Soup ingredient 2: Type changes

“Each nonbasic land is a Mountain” (or “This is an artifact creature,” etc.) changes what something is, so it lives in Layer 4 (type-changing effects).

Soup ingredient 3: Copy effects

Clones and “becomes a copy of” effects live in Layer 1, meaning they establish the baseline before the rest of reality shows up to fight.

Why this creates “I hate this game” moments

Because these effects aren’t competing in one pile—they’re competing in different layers. And that means:

You can’t “solve” the interaction by arguing which effect happened first overall
You have to apply the layer order, and then use timestamps/dependency inside each layer

So the sequence usually looks like:

Copy effects define the starting point (Layer 1)
Type effects decide what category it even belongs to (Layer 4)
Ability removal/addition rewrites what it can do (Layer 6)
Only at the end do anthems and “set base P/T” effects modify the numbers (Layer 7)

That’s why “it’s a land but still gets the anthem buff” can be correct or incorrect depending on whether it’s still a creature after Layer 4 and Layer 6 are done doing crimes.

A quick “layers triage” method you can actually use mid-game

When a pile of effects is on the table and you need an answer fast:

Step 1: Identify the weirdest effect first

“Copy” effects are usually the biggest hidden culprit (Layer 1)
“Becomes a land/creature/artifact” effects are the second (Layer 4)
“Loses all abilities” is the third (Layer 6)
“Gets +X/+X” is the last (Layer 7)

Step 2: Apply in layer order, not in “what happened first” order

If two effects are in different layers, timestamp generally doesn’t matter between them because the layer order already decided the order.

Step 3: If two effects are in the same layer, use timestamp… unless dependency applies

Timestamp is the default. Dependency is the exception.

That’s it. That’s the whole trick.

Wrap-up: layers are annoying, but they’re also your friend

Layers exist because Magic prints cards that would otherwise be physically impossible to referee.

Once you accept that continuous effects are applied in a fixed sequence—and that timestamps and dependency are the tie-breakers—you stop trying to “intuit” interactions and start solving them.

And yes, you’ll still hate some of the answers. But at least you’ll know why you hate them.

John Monsen

All Posts