How to Import a Moxfield Deck: Every Format Explained
August 13, 2026
What you're actually exporting when you hit "Export" on Moxfield
If you want to import a Moxfield deck somewhere else, the first thing to understand is that Moxfield doesn't give you one file. It gives you a choice, and the choice matters more than most guides admit. A deck URL, a plain text list, and an MTG Arena export all describe the same 100 cards, but they carry different amounts of information and they fail in different ways when another app tries to read them.
This guide covers Moxfield specifically: where the export options live, what each one actually contains, the blank-line convention that trips people up on Commander decks, and how to bring the result into Grimoria or anywhere else. For general text, CSV, and Arena format questions that apply beyond Moxfield, see the full MTG deck import guide.
Step 1: Export your deck from Moxfield
Open the deck on Moxfield and click the three-dot More menu near the top of the page. From there you have three practical ways to get a deck out. New to Moxfield itself? EDHREC's overview covers the basics of building a list before you worry about exporting it.
Copy the deck URL (fastest, nothing to format)
If the tool you're importing into accepts a link, this is the easiest path. Just copy the address bar URL for the deck, for example moxfield.com/decks/<deck-id>, and paste it wherever the target app asks for a deck link. There's no export step and no formatting to get wrong, because the importer reads the deck straight from Moxfield's public page. Grimoria, TableCommander, and several other builders accept a Moxfield URL directly.
Export as plain text
Choose Export > Plain Text for a bare list: one card per line, quantity first, card name second, nothing else. There's no header row, no "Deck" or "Sideboard" label, and no explicit tag marking the commander. It's the most universally readable format because almost every deckbuilder can parse "1 Sol Ring", but that simplicity is also where the commander problem below comes from.
Export as MTG Arena format
Choose Export > MTG Arena if the destination expects the Arena-style layout, which adds the set code and collector number to each line (something like 1 Sol Ring (C21) 263). Grouped headers separate the deck from the sideboard. This format is worth using when the printing matters, since it tells the importer exactly which set and collector number to match instead of leaving it to pick whatever's cheapest or first alphabetically.
A note on CSV: Moxfield's CSV export lives under your collection, not under an individual deck (see Moxfield's own collection import documentation). It pulls Count, Name, Edition, Collector Number, Condition, Language, Foil, and Tags for everything in your binder, which is great for moving a whole collection but overkill (and unavailable) for a single 100-card list. If that's what you're after, jump to the collection section below.
The headerless, blank-line-before-commander convention
Here's the detail that causes the most support tickets. Moxfield's plain text export for a Commander deck has no "Commander:" label anywhere in the file. Instead, the commander card (or cards, for partners) sits on its own line at the very top, followed by one blank line, and then the remaining 99 cards follow with no further separator.
It looks like this:
1 Krenko, Mob Boss 1 Sol Ring 1 Arcane Signet 1 Goblin Bombardment ...
An importer that doesn't specifically look for "line(s) before the first blank line" will treat your commander as just another card in the 99, and you'll end up building a 101-card deck with no commander assigned, or the wrong card sitting in the command zone. This isn't a Moxfield bug. It's a deliberate, minimal format, and any tool that wants a clean round trip has to know the convention exists. If a text import keeps eating your commander, this blank line is almost always why.
Importing a Moxfield deck into Grimoria
Grimoria reads Moxfield decks two ways, and both live in the deckbuilder's import flow described in the deck sharing and export help guide:
- Paste the deck URL. Drop the Moxfield link straight into the import box and Grimoria pulls the list, including the commander, without you touching the export menu at all.
- Paste the exported text. If you'd rather export first, either the Plain Text or MTG Arena format works. Grimoria's parser is built to recognize the blank-line-before-commander pattern, so a Commander deck lands in the command zone correctly instead of getting dumped into the mainboard.
Once the list is in, the synergy graph flags weak links, budget swaps cover anything outside your price range, and a power level check tells you if the deck is ready for the table.
If you're moving more than one deck, or you want your whole Moxfield binder rather than a single list, that's a collection import instead of a deck import. Grimoria supports importing directly from Moxfield collection exports, with options to set a default condition and language for cards that don't specify one and to choose which binder the cards land in. Details are in the collection import and export guide.
Importing a Moxfield deck into other tools
The same export choices carry over almost everywhere else. Most deckbuilders, including Archidekt and TappedOut-style importers, accept either the Moxfield URL or a pasted plain text list, and the commander convention above applies no matter which tool is reading the file. If you're comparing where else to build or manage that list once it's imported, the roundup of MTG deck building tools covers how the major options differ.
Fixing common Moxfield import errors
| What you see | Likely cause | Fix |
|---|---|---|
| Deck imports at 101 cards, no commander set | Importer ignored the blank-line-before-commander convention | Re-import using the deck URL instead of pasted text, or manually set the commander after import |
| Wrong printing, foil, or art shows up | Plain Text export doesn't carry set or collector number | Re-export as MTG Arena format, which includes set code and collector number per line |
| Custom categories or tags are missing | Categories and tags are a Moxfield-side feature and don't travel in any export format | Rebuild categories manually in the destination app, or keep the Moxfield tab open as reference |
| Sideboard or maybeboard cards end up in the mainboard | Importer doesn't recognize Moxfield's board separators | Check the destination app's import notes for how it splits sections, or export boards separately |
| Card names with accents or apostrophes fail to match | Encoding mismatch between the exported text and the importer's card database | Re-copy the text directly from the browser rather than a forwarded message or spreadsheet, which can mangle special characters |
Frequently asked questions
How do I export a deck from Moxfield?
Open the deck, click the three-dot More menu, and choose Export. You can pick Plain Text for a simple quantity-and-name list, or MTG Arena format to include set code and collector number. You can also just copy the deck's URL if the app you're importing into accepts links directly.
Can I import a Moxfield deck by just pasting the URL?
Yes, in most modern deckbuilders, including Grimoria. Pasting the URL is usually more reliable than pasting exported text, because the importer reads the deck's actual data straight from Moxfield, including the commander and any partner or background, rather than trying to parse a text file that might be missing details.
Why did my commander disappear when I imported a Moxfield deck?
Moxfield's plain text export marks the commander only by position: it's the line (or lines) before the first blank line in the file, with no explicit label. If the importer doesn't check for that blank line, the commander gets treated as a regular card and the deck imports without one set.
Does a Moxfield import bring over foils and exact set printings?
Only if you export in a format that includes them. Plain Text exports card names and quantities only. MTG Arena format adds the set code and collector number, which is what you want if the exact printing matters to you.
Can I import my whole Moxfield collection instead of one deck?
Yes, but it's a separate flow from a deck import. Moxfield's collection CSV export includes count, set, collector number, condition, language, and foil status for every card in your binder, and tools that support collection import, including Grimoria, read that file to rebuild your binder rather than a single decklist.
Export whichever format matches what you need, a URL for a clean pull with the commander intact, Plain Text for a quick pasteable list, or MTG Arena format when the exact printing matters, and you'll get a Moxfield deck into Grimoria in under a minute.