The Import / Export button in the top action bar is the door in and out of ShuffleKit: spreadsheets and Illustrator files in, print files and virtual-tabletop packs out.

Importing

From CSV or Excel

Upload File takes a drag-and-drop or a file picker, and accepts CSV, Excel and JSON.

Paste Data is the faster route for a quick batch:

Copy cells straight out of Excel or Google Sheets, paste into the box, and click Parse Data. The field expects tab-separated data, which is exactly what a spreadsheet puts on your clipboard.

For example, a small CSV can look like this:

title,Type,ability
Moonlit Scout,living,Reveal the top card of your deck.
Void Cartographer,space,Look at the top three cards.

The first row is the header. Each following row becomes a new card. An entirely empty row is skipped.

Getting an import right

1. Put a header row first. Column headers are matched to your property names, and the matching is forgiving: case and punctuation don't matter, near-misses surface as one-click suggestions in the Map Columns step, and you can remap anything by hand there. Headers that match nothing become new properties.
2. Create the properties first. Define columns in ShuffleKit before importing, so types are right. One thing to know about Select properties: values their options list hasn't seen before are added to it rather than rejected, so scan the options for typos after a big import.
3. Test with five rows. Import a small slice, check it landed correctly, then do the rest.

The import is additive: importing into the current project appends new card rows. It does not match rows by title or update existing cards. In the Map Columns step, each source column can be mapped to an existing property, turned into a new property, or skipped. The final target step lets you add the cards to the current project or create a new project. The summary tells you how many cards and new properties will be created.

This is the regular Cards-page import. Onboarding has a separate first-run import preview with controls for delimiter, header row and smart parsing; use that when you are creating a new project from the onboarding wizard. Either way, keep a small test file handy before importing a full set.

Images can come in through a spreadsheet too, as long as the cells hold image URLs; bare filenames won't display. You can always add artwork after the data lands instead.

ShuffleKit also snapshots your existing cards automatically before every import, so a bad import is recoverable. See Notes & Version History.

From Adobe Illustrator

From Adobe Illustrator... does more than seed a layout: it builds a whole new project from the .ai file, extracting properties, a layout, cards and artwork. Use it when you're migrating an existing card design into ShuffleKit. The layout editor has a separate Import from PSD… option in its LAYOUT dropdown for bringing a Photoshop file in as a layout. See Layouts & the Template Editor.

Exporting

Card images

Import / Export → Card Images (PNG / SVG)... opens the main export dialog:

Render cards as images, spritesheets, or a PDF print sheet.

Format

Cards to export scopes the run. From a deck tab you can export that deck; from All cards you get everything.

Corner radius is a slider from 0%. For the image formats, the help text is worth reading:

Transparent rounded corners for digital/VTT use. For physical cards, Print & Ship die-cuts rounded corners automatically.

So: raise it for digital, leave it at 0 for physical. Rounding corners on a file destined for a printer removes bleed the die-cut needs.

The card grid shows every card that will be exported, rendered. Click a card to exclude/include it. Excluded cards grey out. This is how you export "everything except the three cards that aren't finished" without touching your data.

Export N cards confirms and runs.

Visual exports (PNG, SVG, PDF and virtual-tabletop spritesheets) require a plan that includes visual export. If the dialog lets you configure an export but the preview is blurred or the action says Upgrade to Export, your card data is safe; the export is simply unavailable on the current plan. CSV and JSON data exports are separate and remain useful as card-data backups.

Before a print run

• Check the count on the button matches what you expect.
• Set Corner radius to 0 for physical printing.
• Export a PDF Print Sheet and print one page at 100% scale first. Proof it in hand.
• Remember deck quantities: with Include deck quantities on (the default), a card with QTY 3 lays out three times on the print sheet.

Data exports

All as CSV gives you flat data, one row per card with its property values. Good for spreadsheets, balance analysis, and sharing with someone who doesn't use ShuffleKit.

All as JSON carries the same card data in JSON, which keeps value types intact for scripts and tools. Neither export includes layouts, decks or notes, so treat them as card-data backups rather than full project backups.

Both download immediately without a dialog.

Tabletop Simulator

Tabletop Simulator... produces the spritesheet TTS expects for a deck. The same output is available as a format inside the Card Images dialog, alongside Roll20 Spritesheet.

Clear all cards

Deletes every card in the project. It's in red at the bottom of the menu for a reason, and there's no undo: take a data export and a version snapshot first. Inside a deck tab the same item reads Clear deck... and offers the gentler option of just removing the cards from that deck.