TLDR
To rebuild old commander deck from decklist files, archive the untouched original before changing anything. Then choose one of three goals: an exact historical restoration, a faithful refresh, or a full modernization. Audit the list for current deck-construction rules, Oracle text, banned cards, missing entries, and obsolete interactions. Review functional packages only after that audit, inventory tokens and other play aids separately, and lock one final 100-card version before ordering or gathering cards.
An old decklist is a historical snapshot, not an automatic disaster. Some cards may work differently now, some familiar technology may have aged poorly, and a previously questionable card may even be legal again. The trick is to avoid quietly turning a beloved old deck into a completely different list while fixing it.
Choose what kind of restoration you want
Decide the project’s purpose before making substitutions. Otherwise, every new staple looks tempting, and three hours later your restored deck has a new mana base, a compact combo, and no remaining connection to the list you meant to save.
| Restoration path | What you preserve | What you change | Best for |
|---|---|---|---|
| Strict restoration | The original card choices and historical play experience | Only errors or cards that prevent the deck from functioning under current rules | A time capsule, retired playgroup, or personal collection project |
| Faithful refresh | Commander, theme, memorable cards, and original game plan | Illegal cards, broken interactions, weak support pieces, and major consistency problems | Bringing an old favorite back to regular casual games |
| Full modernization | The commander and broad archetype | Most packages may be rebuilt around current options and expectations | Players who want a current deck inspired by the old list |
Strict restoration does not mean ignoring current rules. It means preserving the historical list as closely as possible while documenting anything that no longer works. A faithful refresh is usually the best default: retain the cards that create the deck’s identity, but repair the pieces that stop it from producing satisfying games.
Archive the original list before editing
Create a read-only copy of the saved decklist. Add the approximate date, original deck platform or source, commander, intended theme, and any remembered play context. Record whether it was a low-pressure theme deck, an upgraded precon, a tuned local-meta list, or something built for a particularly enthusiastic arms race.
Keep notes about signature cards even when they look inefficient today. A seven-mana enchantment that generated the deck’s best stories may deserve more protection than an interchangeable ramp spell. Restoration is partly about function and partly about preserving why the deck existed.
- Save the original file without correcting names or quantities.
- Duplicate it into a working restoration list.
- Record the list’s date or best estimate.
- Write one sentence describing how the deck was supposed to win.
- Mark cards remembered as essential, funny, thematic, or socially important.
- Note any missing side notes, maybeboard cards, or physical cards not represented in the file.
Run a current Commander construction audit
Commander normally uses 100 cards including the commander, follows color identity, and permits only one copy of a card other than basic lands unless a card specifically creates an exception. Start by comparing the old file with the current official Commander format overview.
Count the command zone and library separately. A conventional single-commander deck normally leaves 99 cards in the library, but an old list using partners or another multi-card command-zone arrangement needs a closer audit. Verify that the saved list did not count tokens, a maybeboard, or a companion incorrectly as part of the core deck.
- Confirm the intended commander or command-zone configuration.
- Count the complete deck and identify duplicates.
- Check every card against the commander’s color identity.
- Separate maybeboard suggestions from actual deck cards.
- Resolve misspellings, shorthand, set labels, and ambiguous card names.
- Flag entries that cannot be confidently identified rather than guessing.
Do not start replacing cards until the count is trustworthy. A mysterious 98-card list is often a data problem, not a request for two exciting new finishers.
Check current Oracle text and legality
The wording printed on an old card—or copied into an old deck file—is not necessarily its current rules text. The Magic Tournament Rules identify Oracle as the official text associated with a card name. Check current wording for cards central to the deck’s engine, unusual card types, old legends, and anything relying on a precise interaction.
Record what each questionable card was supposed to do, then compare that purpose with its current text. If the interaction no longer works, you can preserve the card as a historical choice, replace it with a functional equivalent, or redesign that package. The correct answer depends on the restoration path you chose.
Next, check the live Wizards Banned & Restricted list. Commander legality changes over time, so memory is not reliable enough for an old list. A card that was legal when the deck was saved may now be banned, while a card remembered as banned may have returned. For example, Wizards announced several Commander unbans in April 2025 and additional changes in February 2026. Always use the current list rather than treating those dated announcements as the final word.
Sort old cards before cutting them
A dated inclusion is not automatically a bad inclusion. Classify each suspicious card before deciding its fate.
| Classification | How to recognize it | Recommended treatment |
|---|---|---|
| Identity-defining | It expresses the theme, creates memorable plays, or supports the commander in a distinctive way | Keep unless it is illegal or no longer functions |
| Legal but awkward | It still works, but its cost or timing creates friction | Keep in a strict restoration; compare alternatives in a refresh |
| Meta-retired | It answered threats or play patterns common in the original group | Replace if those targets are no longer relevant |
| Functionally broken | Current text, rules, or surrounding cards no longer support the intended interaction | Document and replace |
| Generic support | It fills a role such as ramp, draw, removal, or fixing without defining the deck | Update when the replacement materially improves play |
This approach protects the deck’s personality. Replace generic infrastructure before cutting the oddball card everyone remembers. A restored deck does not need to become a museum, but it should not emerge from the process as a stock list wearing the old commander’s name tag.
Review the deck by functional package
For a faithful refresh or modernization, evaluate groups of cards rather than chasing individual upgrades. Start with the deck’s plan, then ask whether each package still supports it.
- Lands and fixing: Can the deck cast its early plays and commander on time?
- Ramp: Does the acceleration fit the colors, curve, and intended pace?
- Card advantage: Can the deck recover after spending its opening hand?
- Interaction: Can it answer the permanent types and engines common at the intended table?
- Protection and recursion: Which pieces must survive or return for the deck to function?
- Engines and payoffs: Do the cards actually advance the stated theme?
- Win conditions: Can the deck close a game without accidentally adopting a much stronger plan than intended?
Change one package at a time and maintain a swap log. Write the outgoing card, incoming card, and reason for the change. That makes it easy to reverse an update after playtesting and reveals when modernization is drifting beyond the project’s goal. A complete physical test build can help you playtest the restored Commander deck with proxies before locking expensive or difficult-to-source choices.
Build the support kit outside the 100 cards
Old files often preserve the deck but forget everything the deck creates. Search the current card text for tokens, emblems, dungeons, initiative, monarch, day/night, counters, and double-faced-card requirements. Inventory these separately from the playable 100.
Tokens and similar game aids do not occupy deck slots. Tournament rules also permit tokens and other game aids to be represented in any clear way both players understand. For a polished restoration, however, matching and readable helpers make the deck easier to operate—especially when one engine produces several token types or variable power and toughness.
- List every token name, color, type, and relevant ability.
- Estimate how many copies might appear simultaneously.
- Include distinct versions when tapped, attacking, copied, or transformed states matter.
- Add counters, monarch, initiative, day/night, dungeon, or emblem aids as required.
- Plan clear representations for double-faced cards.
- Keep all helper pieces physically separate from the shuffled deck.
Use the Commander proxy order checklist to catch token, double-faced-card, commander, and extra-card problems before finalizing the physical project.
Write a current table brief
An old deck’s reputation may not match its current performance. Write a two- or three-sentence brief explaining the commander, restoration approach, expected pace, notable win conditions, and any intentionally retained nostalgia cards. Wizards presents Commander Brackets and Game Changers as optional ways to discuss expected games, not replacements for an actual pregame conversation.
Describe what the deck does rather than assigning it a heroic but unhelpful number. “Faithfully refreshed graveyard deck with an old mana base, no fast combo, and several sentimental seven-drops” gives a new pod more useful information than “probably a six.”
Lock the final list and finish the physical deck
Keep the archived original and final restoration as separate files. Give the final version a date and clear name, then export a clean quantity-and-card-name list. Confirm that it contains exactly the intended deck, not the tokens, maybeboard, alternate art, or three speculative swaps you forgot were still attached.
If you are producing a complete proxy build, prioritize legible names, mana costs, type lines, and rules text over decorative consistency. A cohesive look is useful only when the deck remains easy to play across a table. The broader decklist-to-finished-deck workflow covers readability, list locking, and physical completion in more detail.
Different production routes suit different projects. Complete-deck ordering reduces the nuisance of assembling 100 separate pieces, while realistic proxy cards may suit players replacing selected entries in an existing physical collection. Whichever route you choose, keep the cards clearly intended for transparent proxy or playtest use.
When the deck arrives or the collection is assembled, compare it line by line with the locked file before sleeving. Check card names, quantities, fronts and backs, commander selection, and helper pieces. It is much easier to find a duplicate land on a sorted table than halfway through game night.
Can a rebuilt proxy deck be used at a store or event?
Ask the playgroup, store, or organizer. Casual policies vary. For sanctioned events, the Magic Tournament Rules generally require genuine Wizards-released Magic cards and limit proxies to specific judge-issued circumstances. A player-made proxy deck should therefore not be treated as universally legal for sanctioned play. Legality within the Commander format and permission to use a particular physical game piece are separate questions.
Restore the deck without erasing its history
The best restoration begins with restraint. Archive the source, choose the goal, verify current construction rules and card text, and only then update the functional packages. Preserve the cards that explain why the deck mattered; replace the pieces that keep it from working at the table.
Your final next step is simple: make two files. Label one “original” and never edit it. Label the other “restoration,” run the legality and package audits, add the support-kit checklist, and test that version before committing to the finished 100-card deck.