If you’re here because you want to know how to upload a decklist for mtg proxy printing, you’re already ahead of the people who paste a half-finished list, forget basic lands, and then act surprised when their “99-card Commander deck” shows up as a 76-card vibe. Let’s do this the clean way.
This guide covers decklist prep, mtg proxy cards printed from decklist upload workflows, proofing, and what to do when something goes sideways (because it’s printing, so of course it will, occasionally).
What counts as a “good” decklist upload?
A good decklist upload is boring. It is aggressively uninteresting. It is:
- One card per line
- Quantity first
- Card name next
- Optional set code and collector number if you care about a specific printing
That’s it. Anything beyond that is where “helpful notes” turn into “mystery meat text” and your importer starts guessing.
If you want the best format for decklist upload to proxy printers, aim for the simplest possible plain text list, then select print versions during proofing.
Example (the good, plain, reliable kind):
2 Brainstorm
1 Sol Ring
1 Command Tower
Example (also fine, just more specific):
1 Shock (M21) 159
1 Fabled Passage (ELD) 244
Step 1: Export your list from your deckbuilder (Moxfield, Archidekt, Arena)
Most deck tools can export in a few common flavors:
- Plain text (quantity + card name)
- “MTGO / Arena style” (quantity + name + set code + collector number)
- Categorized lists (Creatures, Instants, Lands, etc.)
For proxy ordering, plain text is usually the least fragile. But if you care about matching specific art, frame, or set symbol, a set-coded export can save time later.
MTG proxy cards decklist formatting for Moxfield
Moxfield can produce clean exports, but the trick is to choose a format that stays importer-friendly. The “safe” pattern is:
AMOUNT Card Name (SETCODE) NUMBER
…and understand that the set code and collector number are optional.
If your export includes extra metadata (foil tags, categories, labels), it might still work, but you’re increasing the odds of your list turning into a guessing game.
Practical Moxfield advice:
- Prefer an export that keeps each card on one line.
- Avoid exports that sprinkle tags or comments after card names.
- If you do include set codes, make sure they’re real set codes, not your personal nickname for “that one printing with the cool lightning.”
Step 2: Clean the decklist before you upload it
This is where you prevent 90% of problems.
Clean names
Use the card’s actual name. Not:
- “Jace TMS”
- “Steve” (yes, we know it’s Sakura-Tribe Elder, you’re very funny)
- “Teferi 5 mana”
Importers can do fuzzy matching, but abbreviations are how you end up with the wrong Teferi and a new personality trait: frustration.
Confirm quantities
This is the most common “obvious” mistake because it’s boring to check. So people don’t.
- Commander: 99 + commander (or 100 including commander, depending on how your tool lists it)
- 60-card formats: confirm main deck count and sideboard count
- Don’t forget basics (your deckbuilder might auto-handle them in a way your export does not)
Decide whether you need set codes
Set codes are helpful when:
- You want a specific art treatment
- You’re matching an aesthetic (old border, retro frame, a specific cycle)
- You’re building a cube and want consistent printings
Set codes are not required when:
- You just want functional playtest pieces
- You’re going to choose print versions during proofing anyway
Strip “notes” from card lines
If your line says:
2 Brainstorm – foil pls – john’s deck version
You have created three problems and none of them are foil-related.
Keep card lines clean. Put notes somewhere else (order notes, proof notes, a sticky note on your monitor, therapy, whatever works).
Use headings carefully (or not at all)
Headings like “Creatures” or “Lands” can confuse some importers because they’re not cards.
If you want headings for readability, use a consistent prefix like:
// Creatures
// Instants
// Lands
Or skip headings entirely and stay in the blessed land of “one less thing to break.”
Step 3: Upload your decklist and do a fast sanity check
Now you’re ready for how to upload a decklist for mtg proxy printing without summoning chaos.
After you paste/upload, do two checks immediately:
- Total card count
Does the importer show the number you expect? - Obvious misses
Scan for:
- “No match found”
- Weird substitutions (split cards can be offenders here)
- Missing basics
- DFCs showing only one face when you expected something else
This is also where decklist conversion tips for proxy orders matter most: if something imported oddly, fix the source list and re-upload. It’s usually faster than trying to patch a broken import one card at a time.
Proofing workflow: auto-generated proofs vs manual checks
If the upload is the engine, proofing is the brakes. Please use the brakes.
Auto-generated proofs
Many services will generate a proof from your list and their best match. This is convenient and also how you get:
- The right card name with the wrong art
- The wrong printing for a card with ten versions
- That one “special guest” frame you did not want in the middle of your otherwise cohesive deck
Auto proofs are a starting point, not a blessing.
Manual checks: what to look for
When reviewing your proof, check:
- Card identity: Is it the correct card, not just a similar name?
- Versions: If you care about set art, verify printings match your intent.
- Text clarity: Small text should be readable, not fuzzy.
- Cropping and borders: No important text clipped, no stretched frames.
- Double-faced cards: Make sure you’re getting what you expect (and how your printer handles backs).
- Sideboard and tokens: Confirm they’re included (and separated correctly).
If you want a related rabbit hole: proxy labeling matters more than people think, especially if you ever lend decks or bring them to a store night.
Turnaround timelines: what’s “typical”?
Turnaround depends on three things:
- How clean your list is (proofing delays are real)
- Order size (a 100-card deck and a 2,000-card cube order do not live in the same universe)
- Production volume (yes, everyone orders right before their big game night, and yes, it shows)
A realistic expectation for many print workflows looks like:
- Proofing: same day to a couple days depending on the system and whether revisions are needed
- Production: a few business days for standard orders, longer for high-volume or custom requests
- Shipping: depends on method and distance, and also the ancient shipping deity you angered this week
If you have a deadline, act like you have a deadline. Order early, proof quickly, and don’t wait until Tuesday to want it by Friday.
What to do if a card is missing or wrong
First: don’t panic. Second: don’t immediately assume the printer hates you personally.
Do this instead:
- Compare counts
Check your original decklist versus the imported list and final proof. Most “missing cards” trace back to an import mismatch or an unrecognized line. - Identify the exact issue
Write down:
- Card name as you intended it
- Card name as it appeared (or failed to appear)
- Where it went wrong (upload, proof, final print)
- Contact support with specifics
“Something is wrong” is emotionally valid, but not actionable.
“Card X is missing, card Y printed instead, here’s the proof screenshot” gets you results.
Also, if your proxies are going anywhere near strangers, store nights, or loaner decks, knowing what format you’re playing matters. Tournament rules and casual expectations are different planets.
A quick checklist before you hit “order”
- Count: Total cards match your format’s rules
- Commander/Sideboard: Clearly separated (or clearly included)
- Basics: Present and in the right quantity
- Names: Full names, no cute abbreviations
- Notes: Removed from card lines
- Proof: Reviewed for identity, versions, and cropping
- Backup: Save the exact list you uploaded (future you will be smug about this)
That’s the whole play. Clean list, clean upload, careful proof, fewer surprises.
And yes, it’s a little work. But it’s less work than explaining to your pod why your “deck tech” is missing seven cards and includes two copies of something you swear you’ve never seen before.