How does Storm work in MTG?

When you cast a spell with Storm, it triggers an ability that counts how many spells were cast before it during the same turn. It then creates that many copies of the spell on the stack. So if you cast five spells before a Storm spell, you get five extra copies of it — six total. The copies are not cast, just created, so they don't retrigger Storm.

Does countering a Storm spell stop the copies?

No. Once the Storm trigger resolves and the copies are on the stack, countering the original spell only removes the original. The copies remain and will still resolve. To truly stop a Storm spell, you need to either counter it before the Storm trigger resolves, or use effects that can deal with multiple spells simultaneously.

Do your opponent's spells count towards your Storm count?

Yes. Storm counts every spell cast during the current turn, by any player. If your opponent cast two spells earlier in the turn and you then cast a Storm spell, those two spells count toward your Storm total.

Why is Storm banned or restricted in so many formats?

Storm scales exponentially with the number of cheap spells in a deck. In formats with access to powerful cantrips and mana rituals, a Storm deck can win on turn one or two with the right hand — before opponents have a chance to interact. This makes it extremely difficult to balance in competitive play. It's illegal in Standard and Pioneer, and several key Storm spells are banned in Modern and restricted in Legacy/Vintage.

What is the Storm Scale?

The Storm Scale is a semi-official design metric used by Wizards of the Coast to rate how unlikely a mechanic is to return to Standard, rated 1 to 10. Storm itself sits at a 10 — the highest rating — meaning Wizards considers it essentially off the table for Standard and premier sets. It still appears occasionally in supplemental products and Commander content.

Can cards grant Storm to other spells?

Yes. A few cards give Storm to spells that don't inherently have it. Crackling Spellslinger, Ral, Crackling Wit, and Storm, Force of Nature all have abilities that grant Storm to other spells, opening up creative deck-building around non-Storm spells as the primary payoff.

Storm: MTG Mechanic Explained

There are mechanics in Magic that are powerful, and then there is Storm. Few keywords in the game's history have produced the same mix of awe, dread, and occasional table-flipping frustration. If you've ever watched someone cast ten spells in a single turn and then look up with a grin, you've probably seen Storm in action.

What is Storm?

Storm is a keyword ability on Instant and Sorcery spells. When you cast a spell with Storm, you get a copy of that spell for each spell that was cast before it during the same turn. Cast five spells before the Storm spell? You get five additional copies. Cast ten spells first? Ten copies.

The setup requires work - you need to chain together cheap spells to build up that count - but the payoff can be enormous. A single Storm spell at the right moment can end a game on the spot, counter a dozen spells at once, or generate a board-state that's impossible to claw back from.

Rules note: The copies are created on the stack, not cast, so they don't trigger Storm again. Only the original spell was cast.

Rules

Here's how Storm plays out step by step:

You cast the Storm spell. It goes onto the stack.
Storm triggers. The ability counts every spell cast before this one during the current turn - by any player.
That many copies of the spell are put onto the stack.
The copies resolve from the top of the stack, followed finally by the original spell.

A few important things to keep in mind:

It counts all spells, not just yours. If your opponent cast two spells earlier in the turn, those count towards your Storm total.
The copies are not cast. This matters for a lot of interactions - the copies won't trigger "whenever you cast a spell" effects, and they can't be countered by things like Flusterstorm (which specifically copies itself via Storm, but the copies of Flusterstorm can only counter the original spell they were aimed at, not each other).
The copies can have new targets chosen. If the Storm spell targets something, each copy can target something different - or the same thing.
Copies that become tokens are noted explicitly on some cards. Tempest Technique**, for example, states in its reminder text: "Copies become tokens."

Rules note: The comprehensive rules define Storm under keyword abilities (CR 702.40). The trigger reads: "When you cast this spell, copy it for each other spell that was cast before it this turn." The copies are put directly onto the stack - they aren't cast.

Common misunderstandings

Countering the original Storm spell does not counter the copies already on the stack. The Storm trigger has already resolved and put those copies up there. If you want to stop a Storm spell, you either need to counter it before the trigger resolves, or have a way to deal with multiple spells on the stack.
You can choose new targets for each copy independently. This makes Storm spells with targeted effects extremely flexible.
Spells cast during previous turns do not count. The storm count resets at the start of each turn.

Strategy

Building towards a Storm turn

The central challenge of Storm is generating a high spell count before you fire off the Storm spell itself. Decks built around Storm typically rely on a mix of:

Cheap cantrips - spells that cost one or two mana and draw a card, letting you chain into the next spell and the next.
Ritual effects - spells that produce more mana than they cost, like the classic Dark Ritual ('{B}' for '{B}{B}{B}'), letting you keep casting even when you're emptying your hand.
Bounce spells - returning a land or permanent to hand to replay it, generating additional spell triggers in some configurations.
Mana artifacts - early-game acceleration so you can reach a critical mass of mana and cards by the turn you want to go off.

The goal is to reach a point where you've cast enough spells that one final Storm card wins the game - either by creating a lethal number of copies or by overwhelming any response your opponents might have.

Playing against Storm

Stopping a Storm turn is much easier before it starts than once it's underway.

Discard is your best friend pre-emptively. Strip the Storm spell or the key rituals before the combo player even gets to untap.
"Can't cast spells" effects - like Teferi, Time Raveler's static ability in formats where it's legal - can shut off the chain entirely.
Artifact and graveyard hate can disrupt the mana or card-draw engines that enable the Storm turn.
Counterspells are risky but valid. Counter early in the chain if you can. If the Storm spell is already on the stack and the copies are already created, you've likely lost the counter war.

Format check: Storm is legal in Legacy, Vintage, and Commander, but not in Standard or Pioneer. Many of the most powerful Storm spells are also banned in several of those formats. Check the current banlist for your format before building.

Commander Storm

A small cycle of Commander-specific Storm spells exists - Empyrial Storm, Echo Storm, Skull Storm, Fury Storm, and Genesis Storm - each tuned for the multiplayer long-game environment. These tend to have higher base costs but bigger payoffs, reflecting that a Commander game naturally involves more spells cast over a longer period before someone tries to close things out.

Cards that grant Storm

Storm isn't always printed directly on a spell. A few cards grant Storm to other spells:

Crackling Spellslinger
Ral, Crackling Wit
Storm, Force of Nature

These open up interesting possibilities - you can build a deck around a non-Storm spell and then turn it into a Storm payoff when the moment is right.

Notable cards

Flusterstorm ('{U}') - An Instant that counters a target instant or sorcery unless its controller pays '{1}', with Storm. At one mana, it's the kind of card that counters itself into oblivion in a counter war, with each copy capable of targeting a different spell. In Legacy, this is one of the most important interaction pieces in the format. It rewards the player who had built up more spells in a turn - a meta-game within a meta-game.

Mordor on the March ('{3}{B}{R}') - A Sorcery from the Lord of the Rings crossover that exiles a creature card from your graveyard, creates a haste token copy of it, then exiles it at end of turn. With Storm, each copy does that again - potentially filling your board with multiple haste threats for a single turn swing. It's a more recent and accessible example of Storm's scaling power.

Tempest Technique ('{3}{W}') - An Aura with Storm that gives the enchanted creature +1/+1 for each enchantment you control. The reminder text notes explicitly that copies become tokens, meaning a single cast in an enchantment-heavy deck can pile multiple Aura tokens onto your creatures simultaneously.

History

Storm was introduced in Scourge (2003), the third set in the Onslaught block. The design space was immediately apparent - and immediately terrifying. Several Storm spells from that era became cornerstones (or cautionary tales) of competitive formats almost overnight.

The mechanic is now the namesake of the Storm Scale, a semi-official design metric used by Wizards of the Coast's design team. The Storm Scale rates how unlikely a mechanic is to return to Standard, on a scale of 1 to 10. Storm sits at a 10 - the maximum. It is considered one of the most broken mechanics ever designed, and Wizards has explicitly stated it has no plans to bring it back to premiere limited or Standard environments.

That said, Storm has never fully gone away. It reappears occasionally in supplemental products, Commander precons, and crossover sets - usually on cards specifically tuned to be powerful but not format-warping. The Commander Storm cycle is a good example of this careful stewardship: Storm's flavour and feel, at a power level that won't break a multiplayer game in two.

The mechanic's legacy is genuinely complicated. It produced some of the most memorable and skill-testing gameplay in Magic's history. It also produced situations where a player goldfish-ed a perfect hand on turn one and the game was functionally over before it started. Both things are true, and I think that tension is exactly why Storm continues to fascinate players decades after its introduction. ✨