The Layering System in Magic: The Gathering, Explained

When several continuous effects modify the same permanent at once, Magic: The Gathering needs a rule that says which effect happens first. The layering system solves this by sorting every continuous effect into one of seven layers and applying them in a fixed order, regardless of the order the effects were created. This keeps results consistent: two players reading the same board will always reach the same answer.

The seven layers, in order, are: (1) copy effects, (2) control-changing effects, (3) text-changing effects, (4) type-changing effects, (5) color-changing effects, (6) ability-adding and ability-removing effects, and (7) power/toughness changes. You always work top to bottom. Only when two effects sit in the same layer do you start asking which one applies first, using timestamps and dependency.

Layer 1 handles copy effects, like a Clone entering as a copy of another creature. Layer 2 changes who controls a permanent, such as Control Magic. Layer 3 changes a card's text, Layer 4 changes its types (for example, turning a land into a creature), Layer 5 changes its colors, and Layer 6 adds or removes abilities like flying or 'can't block'. Because these run before power and toughness, a creature must first BE a creature (layer 4) before it can have its stats set.

Layer 7 is special and split into sublayers applied in this order: 7a sets power/toughness to a specific value (characteristic-defining abilities and effects that 'set' P/T), 7b applies effects that 'set' P/T from other sources, 7c applies +X/+X and -X/-X modifications, and 7d applies counters. Within a single layer, the timestamp order (which effect started first) breaks ties, unless one effect depends on another, in which case the dependent effect waits and applies after the one it depends on.

Most same-layer conflicts are resolved by timestamp: the effect that came into existence earlier applies first. A permanent's own timestamp can change, for example when it becomes a copy or gains an effect, which is why card interactions sometimes surprise players who only track the order spells were cast.

Dependency overrides timestamp in one situation: if applying effect A would change what effect B does (or whether B even applies), and the reverse is not also true, then B is dependent on A and waits for A to be applied first. A classic example is a 'set this creature's power to 0' effect interacting with a '+2/+2' effect, but dependency only triggers in layer-internal cases where one effect literally changes the existence or text of the other. When effects are mutually dependent or independent, you fall back to timestamps.