CubeCobra to Proxies: A Clean Workflow From List to Draft Box
The cleanest CubeCobra proxy workflow is simple: stabilize the list, lock the intended printings, export a production copy, print only the right batch, and give every physical card a predictable place. The mistake is treating “export list” as the finish line. A Cube can contain every correct card and still become miserable to maintain if the art differs from the list, recent swaps disappear into a side pile, or nobody can tell whether a missing card is drafted, misplaced, or never printed.
CubeCobra is well suited to being the digital source of truth. It supports Cube building, imports and exports, visual organization, change tracking, playtesting, drafts, and analytics. Keep that digital record authoritative; make the draft box reflect it rather than maintaining two competing lists.
Decide whether you are testing or building the finished Cube
Before exporting anything, label the project mentally as either a test batch or a settled build. That decision controls how much money, formatting effort, and organizational fuss the next update deserves.
For an active brew, print only the cards you genuinely need to evaluate. If twelve cards are entering the environment this week, there is little value in rebuilding all 360 or 540 cards for perfect visual consistency. Put the new cards in matching opaque sleeves, identify the batch, draft it, and revise again. Once the list stops lurching after every session, then a coordinated full-Cube order makes sense.
This staged approach also prevents a common Cube-owner trap: preserving a beautiful mistake because replacing it feels expensive. Cheap, clearly marked test cards make cuts emotionally easier. A polished final copy should be the reward for surviving drafts, not the admission price for testing an idea.
Lock card versions before you export
A card name identifies the game piece, but it does not necessarily identify the art, frame, set, or collector number you want. CubeCobra distinguishes the Oracle identity of a card from the Scryfall ID associated with a particular printing. Its Card Versions export includes set and collector-number information, which is much more useful than a names-only list when visual selection matters.
Review versions deliberately before creating the production file. I would check signature cards first, then cycles, basic lands, double-faced cards, and anything with several radically different treatments. If one guild uses matching frames while another looks like a yard-sale binder, drafters will notice even when they cannot explain why.
Do not chase uniformity so hard that recognition suffers. Familiar art can help experienced players scan a pack, while readable names, costs, type lines, and rules text help everyone else. Our guide to Cube proxy sleeves, consistency, and draft readability covers the physical side of that balance in more detail.
Choose the output that matches the current stage
| Output route | Best use | What to preserve |
|---|---|---|
| Browser print-and-play PDF | Fast tests and small update batches | Selected art, legible scale, and a batch label |
| Card Versions export | Orders where exact printings matter | Set codes, collector numbers, quantities, and card names |
| Names-only list | Quick searches or vendors where art is selected manually | Quantities and a separate record of special treatments |
| Custom card workflow | Original designs, altered text, or house-rule cards | Final wording, mana costs, frames, art permissions, and revision number |
CubeCobra’s print-and-play PDF uses the selected art for each card and can be printed through a browser. That makes it a practical route for an immediate test, especially when the cards will be placed in front of basic lands or other backing cards inside opaque sleeves.
For a settled list or a substantial update, use an export that preserves versions and then verify what the printer actually recognizes. A list-to-order service for Cube proxy batches can accept pasted card lists and lets users choose printings or art treatments, according to its current ordering page. PrintMTG is the more relevant route when the project involves original MTG-style cards: its Card Maker provides editable fields and a live preview before ordering.
Those are different jobs. Selecting an existing printing for a 540-card environment is not the same as designing a custom conspiracy card for your house Cube. Use ProxyFoundry for a complete or larger conventional Cube order; use PrintMTG when custom card creation is the actual requirement or when a smaller, revisable project benefits from that workflow.
Create a production snapshot
- Finish the current round of cuts and additions in CubeCobra.
- Review selected versions for showcase cards, cycles, lands, and double-faced cards.
- Export the list and save an untouched dated copy.
- Add a status column such as keep, test, replace, or missing.
- Check quantities, tokens, helper cards, and any intentional duplicates.
- Upload or paste the production copy, then inspect every unresolved match.
- Save the final order file beside the CubeCobra snapshot.
That untouched snapshot is boring right up until it saves the project. If a card arrives with unexpected art or the physical count is short, you can determine whether the problem began in CubeCobra, the export, the ordering interface, or the sorting process.
Proof for drafting, not for a gallery wall
Inspect cards at approximately real size. Full-screen previews can make tiny rules text look healthier than it is. Pay special attention to low-contrast frames, borderless treatments, text over busy art, similar-looking basics, and custom cards whose wording changed during development.
Double-faced cards also need a physical plan before printing. Decide whether players will remove cards from sleeves, use helper cards, or keep the reverse face nearby. The least disruptive choice depends on how often the card transforms and how tightly packed the draft area is. See the setup options for double-faced proxies and helper cards before committing a large batch.
Keep the distinction between casual proxies and tournament cards clear. Wizards says sanctioned events require authentic Magic cards, apart from judge-issued replacements for cards damaged during that event. Its policy separately discusses personal, non-commercial playtest cards used outside sanctioned events. Cube proxies belong at the casual table, not in a sanctioned deck. Wizards’ policy on proxies and playtest cards
Sort the delivery in the same order every time
When the cards arrive, resist the urge to sleeve random favorites first. Compare the shipment with the production snapshot, then sort by a stable system: CubeCobra list order, color and mana value, or numbered storage sections. The exact system matters less than using it consistently.
I like three temporary zones: verified and ready, needs correction, and removed from the current list. Sleeve the verified cards, place them into their permanent Cube sections, and keep rejected or superseded versions out of the draft box. A card should never hover in a mysterious fourth state called “I think this is probably current.”
For future updates, keep a small change packet with incoming cards, outgoing cards, and a dated note. CubeCobra’s change tracking and filtering tools can support that digital process, while the packet keeps the physical swap from spreading across a desk for three weeks. A broader proxy project checklist from decklist to first shuffle can help with final counts, sleeving, and table preparation.
Make the next update easier than this one
The best CubeCobra proxies workflow is not the one that produces the prettiest first order. It is the one you can repeat after the next draft exposes six weak cards, an unsupported archetype, and one pet card that has somehow survived another year.
Start today by reviewing the selected versions in CubeCobra and exporting a dated snapshot. If the Cube is still moving, print only the uncertain cards. If the environment is settled, proof the complete list and place a coordinated order. Either way, make CubeCobra the source of truth and make every physical update traceable back to a specific version. That is how a list becomes a draft box without becoming an archaeological dig.
References
- GitHub – dekkerglen/CubeCobra: An open source web application for building, managing, and playtesting Magic the Gathering cubes. · GitHub
- CubeCobra/packages/docs/card-print-decision-making.md at master · dekkerglen/CubeCobra · GitHub
- CubeCobra/CHANGES.md at master · dekkerglen/CubeCobra · GitHub
- Print a Magic Deck
- MTG Card Maker | PrintMTG
- On Proxies, Policy, and Communication | MAGIC: THE GATHERING
