Help Topics
Browse by category and pick the guide that matches what you need to do.
Getting Started
Collection Management
Decks & Decklists
Markets & Alerts
Account & Support
Getting Started
Collection Management
Decks & Decklists
Markets & Alerts
Account & Support
Importing decklists
MythicHub makes it easy to bring decklists from other tools into your Personal Decks. The import dialog supports multiple sources, but each source uses slightly different syntax. Choose the correct source and follow the format rules below for the best results.
This feature is available to logged-in users. Create an account or sign in, then go to Brew > Personal Decks and click the "Import deck" button to open the decklist import dialog.
Simplest format: just the amount and card name on each line. Use the MythicHub source for this format. For example:
4 Snapcaster Mage 4 Lightning Bolt 4 Counterspell
Import process overview
- Select a source: Choose the platform or format you exported from.
- Paste or upload: Most sources are paste-only; the ManaBox file source accepts a .txt upload.
- Set deck details: Name, format, game type, and visibility.
- Commander formats: If prompted, select your commander (and partner/background) so the deck is assigned correctly.
Matching rules and import options
- Game type matters: Paper, Arena, and MTGO use different printings. Pick the game type that matches your decklist.
- Exact printing match: If you include set codes or collector numbers, MythicHub will try to match that specific printing first.
- Fallback to alternate printings: Enable this option to use another printing when the exact one is not found.
- Card limit: Deck imports are limited to 500 total cards.
- Unmatched cards: If any card cannot be matched, the import will stop and show a list of problem lines.
Supported sources and syntax
MythicHub lets you import decklists from several popular tools and text formats. The key is to choose the correct source and follow the matching syntax for that source.
Quick steps
- Go to Brew > Personal Decks.
- Click the "Import deck" button.
- Choose the correct import source.
- Paste the decklist text or upload a .txt file (ManaBox file only).
- Fill in name, format, game type, and visibility.
- For Commander formats, select your commander if prompted.
- Click Import decklist.
Tip: If a decklist fails to match, try removing set codes and collector numbers or enable "Fallback to alternate printings" in the import dialog.
The MythicHub format is the most flexible and supports sections, printings, finishes, languages, tags, and proxies.
Syntax rules
- Section headers (optional):Use exact headers like "== COMMANDER ==", "== MAINBOARD ==", "== SIDEBOARD ==", and "== MAYBEBOARD ==".
- Card line format:"qty Card Name [SET] #NUMBER" with optional "foil" or "etched", optional language token (
lang:xx, for examplelang:ja, for non-English printings), and optional tag in parentheses at the end. - Split cards:Use "Card A // Card B".
- Tags: Only recognized tags are applied; unknown tags are ignored.
- Proxies:Include the word "proxy" anywhere in the line to mark the card as a proxy.
Example
== COMMANDER == 1 Xyris, the Writhing Storm [C20] #18 foil (draw) == MAINBOARD == 1 Arcane Signet [C20] #237 (mana rock) 1 Sol Ring [C20] #252 (mana rock)
Note: Use square brackets for set codes. Parentheses are reserved for tags, not sets.
Paste the decklist text exported from Moxfield. This importer supports both simple and detailed Moxfield lines.
Syntax rules
- Line format:"qty Card Name" or "qty Card Name (SET) NUMBER" with optional "*F*" or "*E*".
- Sideboard:Add a "SIDEBOARD:" line. Everything after it is treated as sideboard.
- Commander formats: Select your commander (and partner or background) in the import dialog. Moxfield exports do not map commander roles automatically.
Example
1 Prosper, Tome-Bound (AFC) 2 *F* 1 Arcane Signet (TDC) 105 SIDEBOARD: 1 Revel in Riches (PLST) XLN-117
Archidekt exports use a "1x" format and can include tags that indicate deck sections. MythicHub reads the first tag token to determine where the card belongs.
Syntax rules
- Line format:"1x Card Name (set) 123 [Tag]" with optional "*F*" or "*E*".
- Sections via tags:Tags like "Commander", "Sideboard", and "Maybeboard" set the card role.
- No-deck tags:Lines tagged with "{noDeck}" are skipped, except Maybeboard entries.
- Metadata: Custom metadata wrapped in ^...^ is ignored.
Example
1x Become Immense (ktk) 130 [Buff]
1x Command Tower (woc) 156 [Land]
1x Xyris, the Writhing Storm (dmc) 175 [Commander{top}]
1x Consign to Memory (mh3) 54 [Sideboard]Arena decklists use section headers like Deck and Sideboard. MythicHub supports both header-based exports and simple lists separated by a blank line.
Syntax rules
- Section headers:Commander, Companion, Deck, Sideboard, and About (case-insensitive). "About" stops parsing.
- Line format:"qty Card Name (SET) NUMBER" or "qty Card Name" (set and number are optional).
- No headers: A blank line separates mainboard and sideboard.
Example
Companion 1 Lurrus of the Dream-Den (IKO) 226 Deck 4 Monastery Swiftspear (KTK) 118 Sideboard 1 Lurrus of the Dream-Den (IKO) 226
ManaBox exports can be imported either by uploading the .txt file or by pasting the decklist text. Both use the same syntax.
Syntax rules
- Section headers:"// COMMANDER", "// SIDEBOARD", and "// MAYBEBOARD".
- Mainboard: A blank line after the commander section starts the mainboard.
- Line format:"qty Card Name (SET) NUMBER" with optional "*F*" or "*E*".
Example
// COMMANDER 1 Niv-Mizzet, Visionary (FDN) 350 1 Counterspell (DSC) 114 1 Jace, Ingenious Mind-Mage (XLN) 280 *F*
Need help?
If your decklist still fails to import, double-check the source you selected and compare your list to the examples above. You can also remove set codes and collector numbers to broaden matching, or turn on fallback to alternate printings.
If your decklist is correct but still fails, contact support at [email protected] and include the error message shown in the import dialog.