TLDR
Use clearly marked, table-approved MTG playtest cards to answer specific deckbuilding questions before buying or permanently sleeving new cards. Test a package of three to six changes, not twenty unrelated swaps. Make every stand-in readable, tell the table what you are testing, and log whether the cards improved ordinary games rather than one spectacular high roll. Player-made test cards, tournament-authorized proxies, counterfeits, and official Mystery Booster Playtest cards are different things with different rules.
The most valuable playtest card is not necessarily the expensive card you avoided buying. It is the card that proves your deck needs another mana source, cheaper crew support, greater artifact density, or a better recovery plan. Repeated testing should expose the engine around a card, not merely demonstrate that the card is powerful when everything goes right.
What are MTG playtest cards?
In ordinary deckbuilding conversation, MTG playtest cards are temporary stand-ins used to evaluate cards before committing to a list. A basic land with a different card’s name written across it is the classic version. Wizards has previously described this sort of clearly non-authentic personal test card while distinguishing it from cards intended to pass as genuine.
The word “proxy” is often used casually for the same object, but that creates avoidable confusion. It can refer to a player-made stand-in, a professionally printed casual-use card, or a proxy issued by a tournament official under narrowly defined circumstances. Those categories are not interchangeable.
There is also a completely separate product category: official cards labeled “Playtest” from Mystery Booster. Mystery Booster 2 includes 121 of them. Its release notes describe unusual frames, limited rules scrutiny, and limited balance testing, and state that these cards are not tournament legal outside Mystery Booster Limited events. They are real Wizards-produced collectibles, but the word on the card does not give them ordinary Constructed legality.
Where can you use playtest cards?
| Setting | Practical expectation | What to do |
|---|---|---|
| Home Commander | Player-made stand-ins depend on pod consent. | Ask before the game and make every test card obvious and readable. |
| Casual store Commander | Store and event expectations vary. | Contact the organizer and discuss the cards with your pod. |
| Sanctioned Constructed event | Players cannot create their own tournament proxies; Playtest cards are not permitted in Constructed events. | Bring legal, authentic cards and consult the event staff if a card is damaged. |
| Mystery Booster Limited | The designated Playtest cards can be used as part of that Limited environment. | Follow the rules for the specific event. |
| Ordinary Commander with Mystery Booster Playtest cards | Do not assume their official printing makes them part of normal Commander. | Check the current Commander rules and get the table’s agreement before playing. |
The Magic Tournament Rules say players may not create their own proxies for tournament use. Tournament officials can authorize proxies only in defined circumstances, such as replacing a card damaged during an event. The rules also distinguish those judge-authorized replacements from cards labeled “Playtest,” which are not permitted in Constructed events.
Commander is socially different from a sanctioned Constructed tournament, but “casual” does not mean consent is automatic. The Official Commander FAQ says normal games should use official Wizards-produced cards and emphasizes that a good experience involves more than narrow technical compliance. If your pod welcomes stand-ins, excellent. If a store or player does not, respect that boundary without turning deck night into a legal seminar.
Make a test card that opponents can actually use
A playtest card fails when its controller understands it but everyone else must repeatedly ask what it does. Commander already creates crowded boards and long decision trees. Your temporary card should reduce friction, not add another memory game.
- Write the full card name and mana cost prominently.
- Include the type line and the rules text relevant to actual decisions.
- Add power and toughness, loyalty, defense, or crew value when applicable.
- Use a normal card behind the stand-in so the sleeve has the same physical feel as the rest of the deck.
- Avoid a back, thickness, or sleeve treatment that makes the card identifiable in the library.
- Mark it clearly as a test card rather than trying to imitate an authentic printing.
- Tell the table which cards are being tested before shuffling.
A handwritten slip is enough for an initial experiment. For a package you expect to test through many games, a clean and durable version can reduce reading errors. Our guide to printing proxy MTG cards for casual playtesting covers the practical setup. For a smaller customized batch intended for repeated casual testing, custom-printed MTG test cards may be a convenient navigation option, but the same table-consent and event-policy limits still apply.
Use a hypothesis instead of a wish
“I want to see whether this card is good” is too vague. Almost every splashy Commander card looks good in the game where it resolves on curve, survives, and receives two untaps. A useful test begins with a claim that can fail.
Try statements such as: “This Vehicle will attack by turn four without consuming a mana creature I needed for acceleration,” or, “This seven-mana artifact is castable before turn seven often enough to justify being weak in my opening hand.” Now the games can tell you something specific.
Change three to six cards at once when they belong to one package. A Vehicle may need the Vehicle itself, two cheap creatures that crew it, and an artifact-synergy card. A big-mana payoff may need an additional land and two early ramp pieces. Testing only the glamorous card can produce the wrong verdict because Commander cards live inside systems.
A repeatable Commander testing workflow
- Write one question. Define the turn, board state, or role that would make the card successful.
- Build one package. Swap a small group of connected cards and record exactly what left the deck.
- Play ordinary games. Do not take reckless mulligans merely to find the new card.
- Record opportunities as well as casts. A card stranded in hand is evidence; so is a tutor that always finds something else.
- Name the failure mode. Separate mana trouble, missing support, poor timing, vulnerability, and low impact.
- Revise one layer. Change the payoff, its support package, or the deck structure rather than rebuilding everything.
- Retest under the same question. Keep, cut, or continue testing only after the pattern is understandable.
Your baseline matters. If the deck already misses early land drops, it cannot fairly evaluate an eight-mana finisher. Start with a functional structure for mana, card flow, interaction, engines, and payoffs; this practical Commander deck skeleton provides a role-based starting point rather than a rigid formula.
What to record after each game
- Was the card in the opening hand, drawn naturally, or searched for?
- Did it affect the mulligan decision?
- Did the deck make its expected early land drops?
- How much usable mana was available on the important turns?
- When could the test card first be cast without abandoning necessary interaction?
- Was it stranded by color, cost, crew requirements, or missing artifact support?
- Did it matter while ahead, at parity, and behind?
- What happened after removal or a board wipe?
- Would the previous card in that slot have been better in this game?
- Is the current verdict keep, cut, or retest?
Do not turn game night into a spreadsheet competition. Two minutes of notes after each game is enough. The goal is to preserve information that Commander’s most dramatic moments tend to erase.
Diagnose the deck around the card
Artifact engines: density versus payoff quality
Suppose an artifact payoff triggers only once before being removed. That does not immediately make it weak. Count how many cheap artifacts entered before and after it, how many artifacts remained following a wipe, and whether your setup cards replaced themselves. If the payoff regularly waits for fuel, the deck may lack density. If you have abundant artifacts and the payoff still produces little mana, material, or pressure, then the payoff itself is suspect.
I care especially about the floor. A card that is brilliant with six artifacts but blank after the first removal spell is asking the rest of the deck to protect its reputation.
Vehicles: crew cost is a deckbuilding cost
A Vehicle’s mana value is only half its price. Track which creature crews it, what that creature would otherwise have done, and whether removal leaves the Vehicle idle. A three-mana Vehicle with crew 3 can be functionally more demanding than a five-mana creature when your early bodies are utility creatures with low power.
Test Vehicles with realistic openings. If they attack only when your commander survives or when you draw one particular token maker, you do not have reliable crew support. You have a combo with an inconvenient combat step.
Big mana: identify the actual bottleneck
When a ten-mana spell sits in hand, ask why. Missing land drops points toward more lands or card selection. Drawing plenty of mana that enters too slowly points toward cheaper acceleration. Dying while ramping points toward early interaction or blockers. Drawing only mana after stabilizing points toward card advantage or mana sinks.
Do not solve every loss by adding another rock. The distinction between launch ramp and late-game amplification matters, especially when tuning a deck against faster pods. Our discussion of how much ramp a big-mana Commander deck needs is useful when your test log shows mana-development problems rather than weak payoffs.
Cube: test the environment, not just the card
A Cube card can be powerful and still be a bad inclusion. Record when it is drafted, whether it makes the final deck, which archetypes want it, and whether those decks have enough enablers. If an artifact build-around wheels through every draft, the problem may be inadequate support or competition for key pieces rather than the card’s raw rate.
For Cube, test packages across multiple seats and drafts. One designer forcing the intended archetype proves very little. The real question is whether drafters can recognize the lane, assemble it without perfect information, and produce a deck that competes with the environment’s simpler strategies.
Do not let one memorable game decide
Commander produces noisy evidence. A new card can look unbeatable because nobody drew removal, or terrible because one opponent happened to hold the perfect answer. Neither game should be ignored, but neither deserves the whole verdict.
Look for repeated failure modes instead of demanding a magic sample size. Three games may reveal that a Vehicle is impossible to crew. Ten may still leave a narrow late-game card unresolved because it was drawn only once. Continue until you understand what the card needs, when it is useful, and what opportunity cost it imposes.
The best conclusion is often not “good” or “bad.” It may be “good only with two more cheap artifacts,” “excellent from the command zone but redundant in the 99,” or “strong in slower games and miserable against early pressure.” Those are actionable deckbuilding conclusions.
Test the engine, then make the purchase decision
MTG playtest cards work best as temporary measurement tools. Make them clear, secure your table’s consent, choose one narrow question, and test the support cards alongside the exciting payoff. Then use the log to decide whether to keep the package, revise the engine, or walk away from a card that never earns its setup cost.
For your next session, pick one questionable package and write a single success condition before shuffling. If it is a Vehicle, track every realistic crew opportunity. If it is a giant artifact, track the first turn you could cast it responsibly. If it is a Cube build-around, track whether anyone besides its designer wants it. That small discipline turns temporary cardboard into useful evidence.