When your decklist import fails, it’s almost never “the site is broken,” it’s usually one weird export choice, one extra section, or one spicy double-faced card name ruining your day.
TLDR
- The safest import format is boring on purpose:
quantity + card name, one card per line. - Most failures come from extra stuff (categories, maybeboard, labels, set numbers, emojis, headers).
- Fixes are simple: export plain text, clean it, then re-import.
The “universal” decklist format that almost always works
When in doubt, your decklist should look like this:
1 Sol Ring
1 Arcane Signet
1 Swords to Plowshares
10 Plains
10 Island
That’s it. No headers. No “Creatures (12)”. No “Commander:”. No tags. No set codes. No collector numbers. No vibes.
Most import tools are happiest when they’re reading a list that looks like it was typed by a tired goblin accountant.
Clean export (do this once, save yourself three re-uploads)
This is the step that separates “smooth order” from “why does it say 14 cards not found.”
Clean export checklist:
- Export in plain text (the simplest export option your deckbuilder offers).
- Paste into a plain text editor (Notepad works) so formatting gets stripped.
- Delete everything that isn’t a card line (headers, blank sections, maybeboard, labels).
Once your list stops fighting you, you can print magic proxies straight from the cleaned decklist.
Troubleshooting matrix: symptom → likely cause → fix
| Symptom | Likely cause | Fix |
|---|---|---|
| 1) Cards are missing after import | You exported in a format that filters cards (common with “Arena” exports), or your list includes lines the importer can’t parse | Re-export in plain text, remove headers, keep only qty + name |
| 2) “Card not found” errors | Typos, weird punctuation, special characters, or extra metadata on the line | Copy list into plain text editor, remove everything except qty + exact name |
| 3) Wrong version/art got chosen | Importers often default to a printing unless you specify | Either accept the default and change printings later, or use a supported set-code format (and only if your importer supports it) |
| 4) Split / Adventure cards fail | Wrong separator or partial naming | Use the exact card name (split cards often need the // format); avoid custom shorthand |
| 5) Double-faced/MDFC looks wrong | You listed the back face, or listed both faces in a way the importer hates | List the front face name only (or use the exact combined name if your importer supports it) |
| 6) Basics are missing or counted wrong | Basics written in a weird way (or mixed naming for snow basics) | Use consistent lines like 10 Plains and exact names like Snow-Covered Forest |
| 7) Your maybeboard/sideboard got imported | Export included “out of deck” piles, categories, or labels | Re-export with “include out of deck” disabled, or delete those sections manually |
1) Missing cards after import
What it looks like
You import a 100-card Commander list and it comes out as 86 cards. Or it says “X cards were skipped.”
Why it happens
Two usual suspects:
- You exported in a format meant for a restricted card pool (some “Arena” style exports do this).
- Your export includes extra lines the importer skips (headers, categories, empty lines with symbols).
The fix
Make your list aggressively plain:
- Re-export with the most basic text export option.
- Delete anything that isn’t a card line.
- Re-import.
Sanity check: Count lines. If it’s Commander, you want 100 total cards (including commander) unless your workflow separates the commander.
2) “Card not found” errors
What it looks like
The importer throws a list of cards it “can’t find,” even though you can obviously find them with your eyes.
Why it happens
Importers can be fragile about:
- smart quotes vs regular quotes (
’vs') - extra notes like
*F*,#123,[Category], or “(Commander)” - non-card lines like
Creatures (27)
The fix
Paste your export into plain text and make every line follow this pattern:
<number> <Card Name>
If you want to be extra-safe, remove:
xcharacters (1x)- commas and semicolons
- anything in brackets or after a dash
3) Wrong version/art got chosen
What it looks like
You wanted the clean modern frame, you got the weird promo version with the comic font. Or you got a Secret Lair you didn’t ask for. Fun.
Why it happens
Many importers choose a default printing when you only provide card names. That’s not “wrong,” it’s just not what you pictured.
The fix (pick your pain)
- Fastest: Import by name, then adjust printings after import (if your tool supports it).
- Most specific: Use a format that includes set code like:
1 Sol Ring (CMM)Only do this if your importer explicitly supports set codes. Otherwise you’ll turn “wrong art” into “card not found.”
4) Split cards and Adventure cards failing
What it looks like
Split cards don’t import, or import as something bizarre. Adventures sometimes import fine, sometimes don’t, depending on how the name is written.
Why it happens
Split cards often require the exact naming with the // separator. People also shorten names or replace separators with slashes.
The fix
Use the exact full card name as printed. For split cards, that usually means:
1 Fire // Ice
If your export tool “helpfully” rewrites it, rewrite it back.
5) Double-faced cards / MDFCs causing weirdness
What it looks like
You import an MDFC and it shows the “wrong side,” or it errors out.
Why it happens
Some lists include both faces. Some importers want only the front face. Some accept either, but only in a specific format.
The fix
Default to front face only:
1 Valakut Awakening
If your list shows Valakut Awakening // Valakut Stoneforge and that triggers errors, delete everything after the first name.
6) Basics missing or counted wrong
What it looks like
Your import says you have 87 cards because basics got dropped, or basics show up as duplicates you didn’t mean.
Why it happens
Basics get written in odd formats: Plains x10, 10x Plains, Plains (10), or they’re split across categories that get filtered.
The fix
Write basics in the simplest form:
10 Plains
10 Island
For snow basics, use the exact names:
8 Snow-Covered Forest
7) Maybeboard/sideboard/categories got imported (aka “why is my deck 143 cards?”)
What it looks like
Your importer grabs your “Considering” pile, your sideboard, your tokens, your hopes, your dreams.
Why it happens
Some exports include “out of deck” cards by default. Others include category headers and labels that confuse the importer into thinking those lines are real entries.
The fix
- If your export tool has an option like “Include out of deck cards”, turn it off.
- If not: export anyway, then delete those sections manually.
Rule of thumb: If it’s not a card you shuffle into the deck, it should not be in the import list.
FAQs
What export option should I pick from Moxfield or Archidekt?
Pick the one that produces the most boring plain-text list. If the export includes categories/labels or pulls in your maybeboard, it’s the wrong export for importing.
Should I include set codes to control versions?
Only if your importer explicitly supports it. Otherwise, keep it name-only and change printings later (when available).
Do I include tokens in the decklist?
Usually no. Tokens often cause “card not found” errors or get ignored. Keep them in a separate list.
Do I list my commander separately?
Some tools support a commander section, some don’t. The universal-safe move is to include your commander as a normal 1 Card Name line unless the importer tells you otherwise.
Why does “1x Card Name” sometimes fail?
Some importers parse it fine. Others only want 1 Card Name. If you’re getting weird errors, remove the x and try again.
