Do You “Cast” Copies in MTG? Usually No (But Sometimes Yes)

TLDR

  • If an effect says “copy target spell”, the copy is not cast. It’s just created on the stack.
  • If an effect says “you may cast the copy”, then yes, you’re casting it (and “when you cast” triggers will care).
  • The easiest tell: look for the word “cast.” Magic is painfully literal on this one.

“Copy” is one of those MTG words that sounds simple until you run into Prowess, Storm, Magecraft, and a table full of people saying “wait, does this count?”

So let’s clean it up.

The big rule: copying a spell is not casting a spell

Most of the time, when you copy something, you’re copying a spell that’s already on the stack.

Think cards like Twincast. You target an instant or sorcery spell, and the game makes a duplicate of that spell on the stack. You didn’t put a card on the stack from a zone, you didn’t pay costs, and you didn’t go through the normal “casting” process.

Result:

  • The copy exists as a spell on the stack (so it can resolve and it can be countered).
  • But it wasn’t cast, so it won’t trigger things that say “Whenever you cast a spell…”

That’s why copying a spell usually does not add to Storm count, does not trigger “cast” triggers, and does not satisfy “cast two spells this turn” style conditions.

The exception: sometimes you really do cast the copy

Some cards don’t just copy a spell. They copy a card (often in exile or graveyard), and then explicitly tell you that you may cast the copy.

Classic examples:

  • Isochron Scepter copies the exiled card, then lets you cast the copy.
  • Mizzix’s Mastery copies exiled cards and lets you cast the copies.

When the card says you’re casting it, you’re casting it. That means:

  • “Whenever you cast…” triggers will fire.
  • The copy goes on the stack as a spell and can be responded to like normal.

One weird-but-important note: these “cast the copy” effects often happen while another spell/ability is resolving. You still end up with a spell on the stack that players can respond to once the current effect finishes doing its thing.

Why this matters in real games

Here are the most common “gotcha” moments:

1) Prowess and “Whenever you cast…”

If you copy a spell (Twincast style), you didn’t cast it, so Prowess-type triggers won’t see a second cast.

If you cast the copy (Isochron Scepter style), you absolutely did cast it, and those triggers will fire.

2) Storm

Storm cares about spells cast before the Storm spell, and then it copies the Storm spell. Those copies are not cast, which is why Storm doesn’t chain itself forever.

3) Magecraft and “cast OR copy”

Magecraft is the big hint Wizards printed to reduce arguments. A lot of Magecraft cards say “Whenever you cast or copy an instant or sorcery…” meaning the game rewards you for either action.

  • If you cast the original spell: that’s a cast.
  • If you copy it: that’s a copy event.
    Either way, Magecraft is happy.

A quick “spot check” you can do mid-game

Ask yourself: Where did this copy come from?

  • If it’s a copy of a spell already on the stack, it’s not cast.
  • If the effect says “you may cast the copy”, then yes, it’s cast.

If you only remember one thing, remember this: MTG almost never implies casting. It says it.

Scroll to Top