Exporting

When your sheet is ready to use on your target VTT, you export it. The export process takes everything you have built -- your layout, logic, styles, design tokens, and roll templates -- and converts it into the file format your target VTT expects. The result is a set of files you can deploy to the platform.

Supported Export Targets

Platform	Status	Output Format
Roll20	Supported	HTML + CSS + JSON (sheet workers)

Support for additional VTTs is planned. The export details below describe the Roll20 output.

The Export Process

Click the Export button in the editor toolbar
Sheet Architect runs validation on your sheet, checking for errors and potential issues
Review any validation results -- errors must be fixed before you can proceed, warnings are recommendations you should review
Choose your export options
Download the generated files

What Gets Exported

The export produces three files:

File	What It Contains	Where It Goes on Roll20
`sheet.html`	Your layout as Roll20-compatible HTML, including attribute bindings, repeating sections, roll buttons, and sheet worker scripts generated from your logic graphs	The HTML Layout tab in game settings
`sheet.css`	Your design tokens as CSS custom properties, all styles from the Style Editor, and scoping rules	The CSS Styling tab in game settings
`sheet.json`	Translation keys for internationalization and sheet metadata	The translation file (for community repo submissions)

info

If your sheet does not use translation keys, the sheet.json file will contain minimal metadata. You still need it if you plan to submit your sheet to the Roll20 community repository.

What Happens During Export

Behind the scenes, the export process does several things. For Roll20 exports:

Converts layout components to Roll20-compatible HTML elements with the correct attribute name bindings (like name="attr_strength")
Generates repeating section markup following Roll20's <fieldset class="repeating_..."> format
Compiles logic graphs into sheet worker JavaScript that runs on Roll20
Merges design tokens into CSS custom properties in a :root block
Scopes your CSS so it does not interfere with Roll20's own interface
Embeds roll template HTML into the sheet output
Validates everything against Roll20's requirements

You do not need to understand these steps in detail -- Sheet Architect handles them automatically. But knowing what happens can help you debug issues if something does not look right after upload.

Section Pages

Validation -- Understanding errors and warnings before export
Export Output -- Detailed look at each generated file and how to use them on Roll20