archidekt.com No paid content found

Archidekt includes a collection-tracking feature that lets you record the cards you own and then build decks using only those cards. According to Archidekt's own description, you can "track your collection of cards and build with only cards that you own." The practical value is straightforward: instead of building a deck list and then discovering you're missing half the cards, you can constrain your deckbuilding to your actual physical library. This is most useful for paper players who want realistic deck lists, budget-conscious builders, and anyone organizing a large collection.

What Collection Tracking Actually Does

At its core, the feature serves two connected purposes:

• Inventory: A record of which cards you own and, presumably, how many copies.
• Constraint: A filter you can apply during deckbuilding so the editor only offers cards you already have.

This matters because Magic deckbuilding has a physical bottleneck. A 100-card Commander deck or a 60-card constructed deck is only playable if you can actually assemble it. Collection-aware building closes the gap between the digital list and the physical binder.

How to Enter and Manage Your Cards

The source material confirms the feature exists but does not document the exact menu path or field names. Rather than invent steps, here is the general workflow you should expect, along with what to verify as you go:

1. Open your collection area in your Archidekt account. Look for a collection or inventory section separate from the deck editor.
2. Add cards — typically by searching for each card and setting a quantity, or by importing a list. Archidekt supports text input and imports from Arena, MTGO, and other deck list formats, so a bulk paste is the efficient route for large collections.
3. Confirm quantities. Set how many copies you own, since deckbuilding legality depends on having enough copies of a given card.
4. Verify the result by checking that a card you know you own appears in your collection with the correct count.

If you already maintain a list elsewhere (a spreadsheet, another deck site, or an export from a digital client), importing is far faster than manual entry.

Building With Only Cards You Own

Once your collection is recorded, the goal is to make the deck editor respect it. The expected behavior is a toggle or filter that restricts card suggestions and searches to your owned cards. When active:

• Cards you don't own should be excluded or clearly flagged.
• Cards you own should remain selectable normally.
• Your deck's card count and legality checks continue to work as usual.

A sensible way to test this: build a small deck with the filter on, then search for a card you know you don't own. If it doesn't appear as an option, the constraint is working.

How Collection Data Connects to Prices and Analysis

Archidekt's description notes that you can "analyze your stats and compare prices" and browse "with prices from TCGPlayer, Card Kingdom, Cardhoarder and Cardmarket." Collection tracking and pricing reinforce each other:

The combined picture: build within your collection to avoid purchases, or build freely and use price data to estimate what completing the deck would cost across multiple vendors.

Common Friction Points

• Quantities matter. Owning one copy of a card you need four of still leaves you short in constructed formats.
• Collection drift. If you trade, sell, or buy cards without updating Archidekt, the "owned only" view becomes inaccurate.
• Import accuracy. Bulk imports can misread set codes or quantities, so spot-check after importing.
• Feature location may change. Archidekt is actively developed (the page shows new set previews and frequent deck activity), so exact labels and placement can shift.

Who This Is For

Collection-aware deckbuilding suits players who want deck lists they can physically assemble, players managing a growing library, and anyone deciding whether to buy missing pieces. If you only brew digitally and proxy or play online, the constraint is less relevant — but the price comparison still helps you judge a deck's cost before committing.

Archidekt's playtester is a built-in "fishbowl" or solitaire mode: it lets you draw and play out a deck by yourself, without an opponent, to check how the mana, curve, and card flow actually feel. It's the right tool when you want to know whether a deck "runs" — whether you hit your land drops, find your key pieces, and have something to do each turn. It is not a rules engine and not a substitute for playing against a real opponent, so treat it as a consistency check rather than a test of whether your deck wins.

What the playtester is for

Archidekt describes it as a way to "Playtest / Fishbowl / Solitaire your deck with a modern playtester." In practice that means:

• Goldfishing — playing your deck alone to see how fast it develops.
• Checking land and ramp counts — do you reliably have the colors and amounts of mana you need?
• Testing curve and sequencing — can you use your mana efficiently turn after turn?
• Spotting dead cards — cards that sit in hand because you never have the setup for them.

Because there's no opponent, it won't tell you how the deck fares against interaction, removal, or a faster clock. Use it to validate the deck's internal machinery, then take it to real games for the rest.

Starting a playtest

The playtester lives inside the deck editor, so you don't leave the page to use it. The general flow:

1. Open the deck you want to test in the Archidekt editor.
2. Start the playtest from within the editor (the site advertises playtesting as something you do "without leaving the editor").
3. The playtester presents your deck as a library you draw from, with your hand and the battlefield laid out.

Expected result: you're looking at your own 99/100 (or 60) cards, ready to draw and play them one at a time.

Common snag: if the deck list is incomplete or contains cards the tool can't resolve, the playtest won't reflect the real deck. Fix the list first — the same editor supports importing from Arena, MTGO, and other deck lists, and adding cards by drag-and-drop or text input.

What you can do during a test

The playtester is built around the actions you'd take in a solitaire game:

• Draw cards from your library into your hand.
• Shuffle the library so each test starts from a fresh order.
• Look at your library to see what's coming.
• Move cards between hand, battlefield, graveyard, and other zones as you play them.
• Track your board state turn by turn as lands and spells come down.

This is enough to answer the questions that matter for consistency: Did I keep a hand I can actually play? Did I hit my first four land drops? Did I have a play on turn two and three? Did I find my commander or key spell by the turn I need it?

A concrete way to use it

Say you've built a Commander deck and you're unsure whether 36 lands is enough. Run the playtester several times:

1. Shuffle, draw an opening hand, and decide whether you'd keep it.
2. Play out the first five or six turns, making the land drops and casting what you can.
3. Note where it stalls — missed land drops, uncastable spells, or turns with nothing to do.
4. Shuffle and repeat a handful of times to see whether the problem is consistent or just one bad draw.

If the same failure shows up across multiple runs, that's a signal to adjust the mana base or curve. If the deck flows smoothly most of the time, the list is probably sound on its internal consistency.

Where it fits in your workflow

The playtester pairs naturally with the rest of Archidekt's editor. You can build or import a list, check its stats and prices from TCGPlayer, Card Kingdom, Cardhoarder, and Cardmarket, pull in recommendation data from Archidekt and EDHREC, and then fishbowl the result — all in one place. It's also useful before you ask for help: the site's deck help requests show lists with card counts, tags, and comments, so testing first lets you describe the specific problem ("stalls on turn four") rather than a vague one.

Bottom line: use the Archidekt playtester to check that your deck functions on its own — mana, curve, and card flow — before you spend time testing it against opponents. It won't judge your matchups, but it will quickly expose a deck that doesn't run.

You build a deck on Archidekt by adding cards to a new deck in the editor, then saving and naming it. The editor lets you search for cards, add them by drag-and-drop or text input, and see stats, prices, and recommendations without leaving the page. This works for any format you want to build, and you can import an existing list from Arena, MTGO, or another deck list if you already have one.

Before you start

You don't need to install anything — Archidekt runs in the browser. Decide two things first:

• What you're building. A Commander deck (100 cards, one commander) behaves differently from a 60-card constructed deck, so pick your format before adding cards.
• Whether you're starting fresh or importing. If you already have a list in Arena or MTGO, importing saves you the manual entry.

Step 1: Start a new deck

Create a new deck in the editor. From there you can add cards in two ways, and you can mix them freely.

Search and add cards

Use the card search to find cards by name. As you add cards, they appear in the deck list in the editor. This is the normal path when you're building from scratch and want to browse.

Drag and drop, or text input

• Drag and drop: drag cards into the deck area to place them.
• Text input mode: paste or type a deck list directly into the text deck editor. This is the faster route when you already know your list.

Import an existing list

Archidekt imports from Arena, MTGO, and other deck list formats into the text deck editor. If your list lives somewhere else, import it rather than retyping it.

Step 2: Use the editor's built-in tools while you build

The editor is where Archidekt differs from a plain list. While you're adding cards, you can:

The recommendation data is useful when you're short on cuts or want a second opinion on a theme. The price display is useful when you're deciding between similar cards at different costs.

Step 3: Save, name, and manage your deck

Give the deck a name and save it. Once saved, it's a deck you can return to, edit, and share. Deck names, card names, and usernames are all searchable on the site, so a clear name helps if you want others to find it.

If you want feedback, Archidekt has a Deck help requests section where builders post decks and ask for input. Recent examples show the format: a deck title, the creator, when it was updated, when help was requested, view count, card count, comment count, and tags. For instance, a Commander deck listed as "Bracket: Upgraded (3)" with tags like Mill, Self-Mill, and Reanimator, or a Standard deck tagged Tokens, Ramp, and Midrange. Posting there is how you turn a finished list into one that gets reviewed.

Step 4: Test the deck before you commit

Archidekt includes a playtester (also described as Fishbowl or Solitaire). Use it to draw hands and run through your deck's early turns. This catches problems that look fine on a list — too few lands, a curve that stalls, or a theme that doesn't actually come together.

Common snags

• Format mismatch. A Commander deck and a 60-card deck have different rules for deck size and copies. Set the format before you build, or you'll redo work.
• Importing the wrong format. If an import looks wrong, check that the source list matches the format you selected.
• Building past your collection. If you want to build only from cards you own, turn on collection tracking first; otherwise the editor will happily suggest cards you don't have.
• Ads. The site notes that supporting their Patreon removes ads. If ads bother you during long build sessions, that's the stated option.

What you end up with

A saved, named deck you can keep editing, export back out to Arena, MTGO, or other formats, and share for feedback. The build itself is the same loop throughout: add cards by search, drag-and-drop, text input, or import; watch stats, prices, and recommendations as you go; then playtest and revise.

Archidekt supports importing deck lists from Arena, MTGO, and other deck list formats through its text deck editor, and exporting decks back out to Arena, MTGO, and many other formats. The import/export workflow lives inside the deck editor, so you don't need separate tools — but the results depend on how cleanly your source list matches card names Archidekt recognizes.

Importing a Deck List into Archidekt

What you need before starting

• A deck list in text form (copied from Arena, MTGO, a forum post, a spreadsheet, etc.)
• An Archidekt account if you want to save the deck (browsing and building are available, but saving requires being logged in)
• Card names spelled as they appear in the source platform — Archidekt matches against its card database, so misspellings or set-specific naming quirks can cause cards to be skipped

Step-by-step import

1. Open the Archidekt deck editor and create a new deck (or open an existing one you want to add cards to).
2. Switch to the text input mode of the editor. Archidekt describes this as a "text deck editor" that accepts pasted lists.
3. Paste your deck list into the text field. The format Archidekt expects is the standard one line per card, typically quantity card name, which is what Arena and MTGO exports produce.
4. Confirm the import. Archidekt parses the list and places recognized cards into the appropriate categories (creatures, lands, etc.) in the visual editor.
5. Review the result. Any lines Archidekt couldn't match will not appear as cards — check the total count against your source list to spot missing entries.

Common import problems

Exporting a Deck from Archidekt

Step-by-step export

1. Open the deck you want to export in the Archidekt editor.
2. Use the export function and choose your target format — Archidekt lists Arena, MTGO, and "many other formats" as export destinations.
3. Copy the generated text.
4. Paste it into the destination platform's import field (Arena's deck import, MTGO's deck editor, or another site's list importer).

What to check after exporting

• Format compatibility: Arena and MTGO each expect their own text conventions. Exporting to the wrong target can produce a list the destination rejects.
• Card availability: A card legal in your Archidekt deck may not exist in the target platform's card pool (this is most common when moving between paper-oriented lists and Arena, which has a narrower card set).
• Printings and basics: Basic lands and specific printings may need to be re-added manually on the destination side.

Practical Tips for Clean Round-Trips

• Keep a plain-text copy of your list outside Archidekt. If an import partially fails, you can fix the source text and re-import rather than rebuilding card by card.
• Import first, then edit visually. The text editor is fastest for bulk entry; the drag-and-drop visual editor is better for fine-tuning categories and counts afterward.
• Use Archidekt's price sources (TCGPlayer, Card Kingdom, Cardhoarder, Cardmarket) after import if you want to compare the cost of the list across vendors — this is a separate step from import/export and doesn't affect the list itself.
• If you're building around cards you already own, Archidekt's collection tracking lets you filter to owned cards, which is useful after importing a list you want to trim down.

When This Workflow Fits

Import/export on Archidekt is the right approach when you already have a list somewhere else (Arena, MTGO, a friend's text file) and want to analyze, price, or playtest it in Archidekt's editor — or when you've built in Archidekt and need to move the finished list into a platform that actually plays the games. It's less useful if your source list uses non-standard formatting or card names that don't exist in Archidekt's database, since you'll spend more time fixing mismatches than the import saves.

Archidekt is a browser-based deck-building site for Magic: The Gathering. You use it to search cards, assemble a deck visually or by pasting a list, check stats and prices, test the deck, and publish it for others to view or comment on. It fits anyone who wants a free-to-access editor with import/export support for Arena, MTGO, and other formats — the site is supported through Patreon, which the homepage says removes ads.

Core deck-building tools

The editor is the center of the site. Two input methods are described on the page:

• Drag and drop cards into the deck.
• Text input mode to add cards as a list.

While building, you can search for cards and see deck stats and prices without leaving the editor. Prices come from TCGPlayer, Card Kingdom, Cardhoarder, and Cardmarket, so you can compare the same deck across vendors.

Import, export, and format support

Archidekt accepts deck lists from Arena, MTGO, and "any other deck list" through its text deck editor. Export works the same way: Arena, MTGO, and many other formats. This matters if you build on one platform and want to move the list elsewhere without retyping it.

Testing and playtesting

A built-in playtester lets you goldfish, fishbowl, or solitaire a deck. This is for checking how a deck draws and sequences before you commit to buying cards or taking it to a table — not for playing against opponents.

Collection tracking

You can track your card collection and restrict building to only cards you own. That makes it practical to see whether a deck idea is actually buildable from your current binder before adding anything to a buy list.

Recommendations and community decks

• Recommendation data comes from Archidekt itself and from EDHREC, which is useful for Commander players looking at common inclusions.
• Browse and edit decks from other users. The homepage shows a live feed of recent decks with view counts, tags, and formats, plus a "Deck help requests" section where creators ask for feedback and list details like card count, tags, and comments.

What the homepage shows you

The public feed is a quick way to see what the community is doing. Recent decks list format (Commander, Standard), tags (Lifegain, Tokens, Mill, Landfall, Aristocrats), and sometimes a bracket, such as "Bracket: Optimized (4)" or "Bracket: Upgraded (3)". Deck help requests add the deck's age, when help was requested, views, card count, and comment count — for example, a 100-card Commander deck with 431 views and 0 comments.

Practical notes

• The site is ad-supported with a Patreon option to remove ads; no pricing tiers or account requirements are stated on the page.
• Deck names, card names, and usernames are all searchable, so you can look up a specific list or builder.
• If you only want to test an idea, you can build and playtest without exporting anything.

If your goal is to move a list between Arena, MTGO, and paper, or to get EDHREC-informed suggestions while you build, Archidekt covers that in one editor. If you mainly want community feedback, the help-request queue is the place to post.