TLDR
Build an MTG proxy Commander deck from one locked version of your digital list. Print the commander and all 99 library cards, keep tokens and replacement candidates separate, choose a clear plan for double-faced cards, and use consistent backs or fully opaque sleeves. After every session, record swaps before updating the digital list. That prevents the paper deck, online brew, and your memory of what you tested from becoming three different decks.
The difficult part is not producing 100 pieces of cardboard. It is creating one coherent physical test kit from a Commander list that changes every time you stare at it for six minutes. A reliable workflow gives you a known starting point, a complete accessory package, and a record of what changed.
Start with a complete-deck checklist
Commander’s standard construction baseline is a 100-card deck comprising 99 cards plus a commander. Except for basic lands and cards whose rules permit otherwise, it is singleton, and the cards must comply with the commander’s color identity. The official Commander format overview covers that foundation.
Your production checklist should include more than the formal 100 cards:
- One clearly identified commander
- A 99-card library with checked quantities
- A separate stack of tokens, emblems, markers, and copy representations
- A representation plan for every double-faced card
- Consistent card backs or fully opaque sleeves
- A separate packet of cards being considered as replacements
- A dated copy of the exact decklist being printed
- A simple swap and playtest log
Tokens and emblems are game accessories rather than part of the 100-card deck. Replacement candidates also stay outside the locked deck until you deliberately make a swap. Keeping those groups physically separate makes recounting much less exciting, which is exactly what recounting should be.
Lock one source-of-truth list before printing
Choose one authoritative version of the brew: a deck-builder page, a text export, or a local file. Do not simultaneously treat a public list, an unsaved browser tab, and a notes app as equally current. Give the chosen version a date or simple number such as “v0.4 — June 22.”
Separate the contents into commander, main deck, tokens, and candidates before sending anything to print. Then check exact card names, quantities, basic-land totals, unintended duplicates, accidental maybeboard lines, and the selected commander. LetsProxy’s ordering guidance specifically identifies missed names, duplicate pastes, maybeboard imports, omitted tokens, and incorrect commanders as preflight problems worth catching.
If you are producing the cards at home, the guide to printing cards for Commander and deck testing provides the broader print workflow. If you prefer a finished print run, clean and lock the list before using an MTG proxy printing service. Import behavior and accepted list formatting can vary, so review every matched card rather than assuming a successful paste means a correct deck.
Treat the mana base as its own test module
A full proxy deck lets you test the mana base attached to the actual spell suite, not a generic pile of lands. Avoid starting from a supposedly universal land count. Curve, color intensity, ramp, card selection, land-based synergies, and the number of expensive spells all change what the deck needs.
During games, record observable failures rather than merely writing “mana bad.” Useful notes include:
- The turn on which a required color was unavailable
- A tapped land that delayed the intended play
- A hand with enough lands but the wrong color distribution
- A fetch effect without a useful remaining target
- A utility land whose colorless production caused a problem
- A basic land or fetchable basic you repeatedly wanted
- A land drawn late that lacked a relevant secondary use
For each change, log both sides and the reason: “Swamp out, untapped blue source in; missed second blue on turns four and five twice.” That is actionable. “Mana felt weird” is how cardboard acquires folklore.
Build a separate token and emblem stack
Review every card in the locked list for tokens, copies, emblems, Roles, and named game pieces. Do not rely on memory or assume a printing interface will detect them automatically. LetsProxy’s guidance recommends accounting for created tokens and selecting the intended version when token names vary.
Keep the token package outside the 100 cards in a different sleeve color, deck box compartment, or labeled band. If several game pieces share similar art, mark their characteristics clearly enough to distinguish them across the table or on webcam. Recheck this packet whenever a token-producing card enters or leaves the deck.
Choose a DFC plan before sleeving
Double-faced cards need to remain indistinguishable from other cards while in hidden zones. The Comprehensive Rules identify opaque sleeves and substitute cards as ways to manage double-faced cards within that framework. The current Comprehensive Rules also distinguish modal double-faced cards, where a face is chosen when the card is played or cast, from transforming double-faced cards.
Three practical playtest approaches work:
- Print both faces and use a fully opaque sleeve, turning the card over when required.
- Place a substitute or checklist-style card in the library and keep the full double-faced reference nearby.
- Use a clearly labeled casual placeholder in the deck with a readable reference copy outside it.
Whichever method you choose, apply it consistently. Check the special-card proxy preflight guide when the list also contains Battles, split cards, Adventures, meld cards, or unusual layouts.
Make the deck shuffle-safe
Back variation can reveal card identity even when every front is readable. Use one consistent back throughout the library or sleeves that are genuinely opaque under normal room lighting. LetsProxy’s guidance recommends consistent backs or fully opaque sleeves to avoid marked-card problems.
Before playing, fan the face-down deck and look for transparent sleeves, uneven insert thickness, distinctive wear, curled cards, or pieces cut to noticeably different sizes. A separate sleeve for the commander is practical only while that card stays outside the library. If an effect can put it into the library and you allow that to happen, move it into a matching sleeve first.
Home-printed inserts should also be checked at final size. The MTG proxy card size guide explains the sizing problem, while the decklist-to-PDF workflow recommends using 100% or Actual Size, calibrating with a test page, and accounting for Letter-versus-A4 differences. “Fit to page” is convenient right up until it quietly changes every card’s dimensions.
Add a replacement packet, not a sideboard
Keep the tested 100 intact at the start of each session. Put active replacement candidates in a separate labeled packet organized by role: removal, ramp, card advantage, lands, protection, finishers, or theme pieces. This is a brewing tool, not an implied Commander sideboard.
Give each candidate a proposed cut. “Try this someday” creates a growing stack but no experiment. “Test this two-mana removal spell over the current four-mana option” defines a comparison. A reusable Commander proxy playtest binder can hold a larger pool, while the session packet should contain only the changes you are realistically evaluating that day.
Keep the physical deck and online brew synchronized
Use the same loop for every revision:
- Lock and date the source list.
- Print or assemble that exact version.
- Play games without silently changing the baseline.
- Record every swap and important observation.
- Update the source list after the session.
- Archive the tested version before creating the next lock.
A useful session log needs only the date, version, pod context, cards swapped, mana observations, missing tokens or DFC references, and next actions. Record between-game swaps immediately. If you wait until the following morning, the deck builder will contain the version you meant to test rather than the version you actually shuffled.
Have the Rule 0 conversation before playing
Proxy acceptance varies among playgroups, stores, organizers, and venues. A concise disclosure is enough: “This is a readable, consistently sleeved proxy test deck. I’m evaluating a few replacement slots, which are kept separately.” Then ask whether the table is comfortable playing against it.
Personal playtesting and sanctioned tournament policy are separate questions. Wizards’ published proxy-policy explanation distinguishes personal, non-commercial playtest cards from counterfeits and says cards used in sanctioned events must be authentic, apart from limited circumstances involving judge-issued proxies. Read Wizards’ proxy-policy explanation before assuming a casual arrangement applies to an organized event.
Final pregame audit
- Count 99 library cards plus the commander.
- Confirm that every library card has a consistent back or opaque sleeve.
- Pack all tokens, emblems, counters, and DFC references.
- Keep replacement candidates outside the deck.
- Save or export the exact version being tested.
- Bring a readable list for tabletop or webcam reference.
- Tell the pod that the deck is proxied before the game begins.
Common questions about proxy Commander decks
Can I use a fully proxied Commander deck?
You can propose one for casual, unsanctioned play, but acceptance depends on the playgroup, store, organizer, or venue. Make the cards readable, keep the library shuffle-safe, and ask before playing. Do not assume casual permission extends to sanctioned events.
Can I proxy basic and expensive lands?
For a transparent playtest deck, proxying the complete intended mana base gives you better evidence than replacing expensive lands with unrelated cards. The key social question is whether the pod accepts the test configuration, not the market price of one particular slot.
Do tokens count among the 100 cards?
No. The constructed deck is the commander plus the 99-card library. Keep tokens, emblems, and similar game pieces in a separate accessory packet.
How do I synchronize the deck with Moxfield or Archidekt?
Treat one deck-builder list as the source of truth, save a dated version before printing, and log all physical swaps. Update the online list only from that log, then archive the tested version before starting the next revision.
Build the version you can actually test
A useful MTG proxy Commander deck is not merely 100 printed card faces. It is a controlled version of the brew with a complete mana base, the required tokens and DFC references, a shuffle-safe library, and an honest record of every experiment. Before printing, freeze the list, audit all 100 cards, and write the version number on the deck box. Future you will still make questionable swaps, but at least future you will know which deck made them.