How Fast Can You Turn Raw Notes and Spreadsheets Into a Playable Card Prototype?
For many tabletop designers the bottleneck isn't creativity, it's translation. Here's how to get from scattered notes, spreadsheets and old card files to testable cards in an evening, without days of manual formatting.
· 5 min read
In this post
- When your design files slow the game down
- What to remember
- Common questions
- How do I go from a spreadsheet or notes to a prototype quickly?
- What source material works best?
- What should a good import include, end to end?
- How do I avoid errors in big card sets?
- Want to try it right now?
- A format that makes every import faster
- Print it the same evening
- The real advantage is faster playtesting
Most designers don't start from nothing. They start from a mess: a spreadsheet of card stats, a notes app full of effects, a document of rules, maybe a folder of cards from an older version made in a different tool. The game is in there somewhere. Getting it onto printable cards is what takes the time.
How fast can it go? With the material in reasonable shape, an evening. Here's how.
When your design files slow the game down
The trouble with scattered source material isn't the mess itself. It's that every change has to be made in several places. You rebalance in the spreadsheet, then remember to update the card file, then forget the rules document. After a few rounds, the three disagree and you're not sure which is right.
The fix is to pick one source of truth for your cards (a table) and make everything else come from it.
What to remember
- One row per card. Every card's words and numbers in one table.
- Columns are fields. Name, type, cost, effect, flavour, quantity, image.
- Layout comes from a template, not from the data.
- Images match by file name, so you never place art by hand.
Common questions
How do I go from a spreadsheet or notes to a prototype quickly?
Get everything into one table, then point a template at it. If your stats are already in a spreadsheet, you're halfway done. If your effects are in notes, paste them into a column next to the stats. Don't format anything yet.
In Decklab AI, Data mode is that table: a spreadsheet beside your card. Paste cells straight in from Excel or Google Sheets, or import a CSV or Excel file, and each row becomes a card. Link the template's text and numbers to the columns and the whole deck appears.
What source material works best?
Anything that's already in rows and columns. Spreadsheets are ideal. Lists in a notes app work if every card follows the same pattern ("Name, cost: effect"), because you can split them into columns in a spreadsheet first. Old card images can't be read as data, but you can still use them: lay them out on a print sheet as they are while you rebuild the data alongside.
Print-and-play PDF maker
Turn your card images into a print-and-play PDF: pick the card size and paper, add cut marks and backs for double-sided or fold-and-glue printing, and set how many of each card. Free, in your browser, with no sign-up.
If what you have is a rules document rather than card data, Decklab AI can read pasted rules into the game's pieces and rules (its resources, keywords and card types), as a proposal you check before accepting.
What should a good import include, end to end?
- Clean headers. One header row, one name per column, no merged cells.
- A quantity column (Qty or Copies), so the print file has the right number of each card.
- An image column with file names (dragon.png), so art finds its card.
- Consistent wording, so the same keyword is written the same way everywhere.
Then: import, link the template, check, print.
How do I avoid errors in big card sets?
Let the tool check for you. Decklab AI's Preview shows every card at once, and the Problems panel flags text that overflows its box and keywords that no one defined, which catches most typos in keyword names. Fix them in the grid; the card follows. For a final check, export the data back to CSV and skim it in your spreadsheet.
Want to try it right now?
The free quick card maker does the core of this in your browser, with no account: pick a starter template, paste or import your spreadsheet, tweak the design, and download a print-and-play PDF or a PNG of each card. Its sample CSV shows the exact column layout to start from.
Quick card maker
Make a deck of printable cards from a spreadsheet: pick a starter template, paste or import a CSV, tweak the design, and download a print-and-play PDF or a PNG of each card. Free, in your browser, with no sign-up.
When you outgrow it (rules, variants for different card types, several decks, a rulebook, a board), the same approach scales up in the full editor.
A format that makes every import faster
Keep your source file in this shape and every future import is painless:
| Name | Type | Cost | Effect | Flavour | Qty | Image |
|---|---|---|---|---|---|---|
| Ember Drake | Creature | 5 | Flying. When played, deal 2 damage. | It remembers the old fires. | 2 | ember-drake.png |
| Ancient Grove | Location | 3 | Your creatures cost 1 less. | 1 | ancient-grove.png |
- Put keywords at the start of the effect, the same way every time.
- Use whole numbers in number columns: no "3?" or "2-3".
- Name image files after the card, in lower case with hyphens.
Print it the same evening
Once the cards are on screen, deal a few hands on the playtest table to see whether the game reads, then export a print-and-play PDF with cut marks and backs. Every export is free. Check your printer's scale before you print a full run:
Printer calibration page
Print one Letter or A4 page with a 50 mm square, a poker card outline and rulers to check your printer prints cards at the right size, and learn how to fix it when it doesn’t. Free, in your browser, with no sign-up.
The real advantage is faster playtesting
Importing data isn't the goal. The goal is that next week's rebalance is a few cell edits and a reprint, not another day of formatting. Get your notes into one table once, and every playtest after that gets cheaper.