Skip to main content

Export cards to Screentop.gg

The Screentop export is a downloadable upload pack. Screentop stores the sheet images after you upload them; it does not load artwork from Game Piece Studio during play.

Screentop export is available on Lite and Pro plans. A pack supports up to 500 saved dataset rows.

Screentop.gg export settings with sheet columns and rows, maximum image size, rotation, and image format

Build and inspect the pack​

  1. Save the design, dataset, and image changes you want to include.
  2. Review the full collection in Export QA.
  3. In Export settings, enable Screentop.gg.
  4. Choose the number of sheet columns and rows. A larger grid makes fewer files; a smaller grid can make individual sheets easier to replace. Keep the longest image edge at or below 4096 pixels.
  5. Choose rotation and PNG or JPG. PNG is lossless; JPG makes smaller lossy uploads.
  6. Choose Build Screentop pack (the button reads Start exports or Export batch when other formats are also enabled) and wait for the build to become ready.
  7. Download the ZIP from the export tray. It also remains under Hosted exports → Screentop downloads until it is rebuilt or deleted.
  8. Extract the ZIP and read README.txt before uploading anything.

The pack contains:

  • face sheet images and either one shared-back image or matching back sheets;
  • README.txt, with the exact asset names, row/column grids, variant coverage, and recommended Tile size;
  • variants.js, ready to paste into Screentop's bulk variant update function;
  • manifest.json, with the same mapping in machine-readable form.

Set up the component in Screentop​

  1. Open the Screentop game in edit mode and open Assets.
  2. For every image listed in README.txt, create an asset with the exact listed name.
  3. Upload the matching image and enter its exact Rows and Columns. Do not infer the grid from the image dimensions.
  4. Create a Blank Tile component with a rectangular shape and the width and height recommended in README.txt.
  5. Create the stated number of variants.
  6. Select all variants, choose Update, and paste the contents of variants.js into the update function.
  7. Save the update, create Tile objects from the Chest, and check the first and last variant on every sheet.

Exact asset names matter because variants.js refers to them. The script maps each variant to the correct sheet cell and uses either the shared back or its matching unique-back cell.

Rebuild after artwork or data changes​

Studio keeps only the latest successful Screentop pack for a design. A successful rebuild replaces the retained download; it does not update assets already stored in Screentop and it does not keep a five-version history like Tabletop Simulator.

After rebuilding:

  1. Download and extract the new ZIP.
  2. Compare its README.txt and manifest.json with the pack used by the current table.
  3. If only pixels changed and the asset names and grids are unchanged, replace the corresponding images in Screentop Assets.
  4. If card count, sheet count, grids, asset names, back mode, or variant ranges changed, create or replace the affected assets and run the new variants.js across all variants.
  5. Check the first and last variant on each sheet again.

Keep the ZIP used for an important playtest outside Studio. The next successful rebuild removes the previous retained pack.

Troubleshooting​

  • A variant shows the wrong card: confirm the asset name, Rows, Columns, and variant count match the new README.txt, then rerun the complete variants.js update.
  • Cards are transposed or rotated: check the export rotation and the Screentop asset grid. Rebuild after changing rotation.
  • A back is wrong: confirm whether the design now uses one shared back or unique backs, upload every listed back asset, and rerun the mapping script.
  • The final sheet has blank cells: unused cells on a partly filled sheet are expected. Use the variant range in README.txt; do not create variants for blank cells.
  • Screentop still shows old art: replacing the file in Studio is not enough. Upload the new image to the corresponding Screentop asset and confirm the update was saved.
  • A build fails: open the failed export for its error, then fix unresolved data, inaccessible images, font loading, or invalid source content before rebuilding.
  • The old ZIP is gone: Studio retains only the latest successful pack. Recover the earlier file from the copy kept with that playtest, or rebuild from the matching game state.

For Screentop controls, see its beginner tutorial and bulk updating guide.