CSV to Card Game

Standard CSV with headers in the first row, one card per row, UTF-8 encoded. Commas as delimiters, quotes around fields containing commas. Google Sheets, Excel, Numbers, and Airtable all export to this format by default, and Excel .xlsx and JSON files import directly too.

Yes. Share the sheet with Anyone with the link, or publish it to the web as CSV, and paste its link into the import dialog. ShuffleKit keeps the link for that collection, so after you edit the sheet, Sync reads it again and shows what changed before it updates the cards. You can also paste cells straight from the sheet, or download it as a CSV and upload that.

No. ShuffleKit matches your headers against the columns you already have, suggests a match for near-miss names, and shows you a mapping screen where you can override anything. You can also define your own card properties to match your CSV columns exactly.

Keep the CSV to text and numbers, then add art inside ShuffleKit: upload pictures and pick one per card, or have Shufflo generate art for every row from its own columns.

Yes. ShuffleKit handles large imports cleanly. Most decks are 30–200 cards, but full TCG sets of 500–1000 cards work fine on paid plans.

You choose. Add every row as a new card leaves the existing cards as they are and reuses the columns the file shares with the deck, so the bindings in your designs keep working. Update matching cards matches each row to a card by the ShuffleKit ID column that CSV export writes, or by a column you pick, such as Name. A changed row updates its card in place, so its decks, notes and layout stay attached, and a new row becomes a new card. Cards the file no longer lists are left alone unless you choose to archive or delete them. You see every change before it is saved. Columns the file doesn't carry are never touched, and each card's version history keeps how it looked before the import.