Export
One screen, three outputs, any combination of them. What comes out is what the preview drew.
The three outputs
| Individual images | One file per card, in cards/ |
| Grid sheet images | Packed sheets for Tabletop Simulator, plus its saved object |
| Cards laid out on printable pages — see Printing and pre-press |
Tick any combination; they are produced in one pass. The pane on the right previews the selected output — an actual page, an actual sheet — with the file it will become named underneath.
Settings that apply to everything
Scale
Draws every card at 1× to 4× the blueprint's pixels. This is the same card at more resolution, not a bigger card: nothing about the layout changes, and a 2× export of a 300 DPI card is a 600 DPI card.
Which decks
A project with several decks exports any selection of them. Merge decks puts decks that share a blueprint out as one — one set of sheets, one saved object — which is what you want for a core set plus its expansions.
Unique backs
Normally every card shares one back. Turn this on and each card's back is rendered from
its own row, which becomes per-card backs in the PDF and UniqueBack in
Tabletop Simulator.
Per-card files
File names
The naming pattern takes {index}, {name}, {deck}
and {face}. Leave it empty for the default. A print shop that wants
front_001.png / back_001.png gets it from a pattern rather than
from a batch rename afterwards.
Format, DPI and bleed
PNG keeps transparency and is free. Pro JPG (with a quality setting) and TIFF are the formats presses ask for, and Pro output DPI resamples the files and writes the number into their metadata, which is what a preflight reads. Bleed draws the print margin into each file.
Warnings are the point
The export reports per deck: cards written, files produced, and every warning the renderer raised — text that overflowed its box, artwork that was missing, a QR code too small to scan, a font weight that does not exist. Read them. They are the difference between finding a problem now and finding it in a box of five hundred printed cards.
The same pipeline, from a script
The GUI and the command line call one renderer, so a deck exported by hand and the same deck built in CI come out byte for byte identical. That is what makes a deck reproducible a year later, when you no longer remember which boxes were ticked.