Skip to main content

Use a deck in Tabletop Simulator

The Tabletop Simulator workflow creates a hosted canonical export for a design. Its URL stays stable when you rebuild the deck, making it suitable for an ongoing prototype.

Build the first deck​

  1. Finish the design’s face, back, dataset assignment, and preview checks.
  2. Resolve Export QA errors.
  3. Open Hosted exports.
  4. Create a Tabletop Simulator deck for the design.
  5. Wait for the build to finish, then use the supplied URL in Tabletop Simulator.

Keep the URL private when the game is private. Anyone with access to the tabletop setup may be able to load the hosted artwork.

Rebuild after changes​

A rebuild creates a new retained version while preserving the canonical deck URL. Existing tables can continue to point at the same address.

Changes made after the build starts are not part of that version. Wait for Saved, start the rebuild, then open the generated deck to confirm the expected art and card count.

Version history​

Retained versions help recover a known prototype or compare a playtest. Give the team a simple convention for recording which version was used in each session.

Troubleshooting​

  • Old artwork appears: confirm the rebuild completed and the tabletop client refreshed the asset.
  • Cards are missing: check selected rows/options and Export QA.
  • A face or back is blank: open the source design and check references, images, and data bindings.
  • A hosted deck is no longer needed: check active playtest tables before removing its project or hosted export.

This persistent, versioned workflow is different from the Screentop pack, which is replaced on each successful rebuild.