Supported Inputs
The import flow is designed for pasted deck exports, not file uploads. The current UI explicitly supports Arena, MTGO, TappedOut, ManaBox, and plain-text list styles.
- Single-line card lists like `1 Card Name` or `1x Card Name`
- Arena-style exports with set code and collector number
- Lists with explicit sideboard or commander sections when the source format includes them
Choose the Right Game Type
- Limited: use this for draft or sealed deck imports and record tracking.
- Standard: use this for ladder or metagame-oriented deck analysis.
- Commander: use this for 100-card singleton commander lists.
Picking the correct game type matters because Adria uses different validation and analysis logic for each path.
Record and Notes
Match record fields are optional, but they help keep imported sessions useful later. Notes are also optional and are best used for context: what went wrong, which matchup felt bad, or what you want reviewed.
What Happens After Import
- Adria parses the pasted list and normalizes it into an internal deck representation.
- The app stores the imported session and redirects you to an analysis page.
- The exact analysis depends on the game type you selected before submit.
Workflow Differences
- Limited imports: best for draft/deck review and result tracking.
- Standard imports: best for meta-positioning and deck critique.
- Commander imports: best for legality, color identity, bracket context, and saved deck follow-up.
Storage and Privacy
Imported decks become part of your saved product data. For account, retention, and third-party details, see Privacy. If you are importing sensitive notes alongside a decklist, treat them as data stored with the import record.
Next Steps
- Open Import when you are ready to paste a list.
- Help if you are not sure which guide you need next.
- FAQ for shorter answers about imports, accounts, and AI setup.
