Publish and export

Publishing preserves the approved story while work continues on the next draft. A published version should always be traceable to the scenes, choices, media, and languages that were reviewed together.

Publish a playable version

Before publishing, complete the checklist in Preview and test. Give the version a short note describing the creator-visible change.

Publishing should not replace the editable draft. Continue editing after a version is published, then publish another version when the next change is ready.

Export a video

A linear route can be exported as a video for review or sharing. Choose the route and language first, then confirm that voices, music, sound, framing, and timing are correct from beginning to end.

Choices and alternate endings belong in separate video routes. A video export does not replace the interactive project.

Export the editable project

Use .vf when another creator needs the complete editable project or when you want an offline backup.

Read Project files for what is included and how import creates a separate project.

Export a playable Web package

Use Export playable Web package after publishing when the experience should run from a static Web host. The package includes its player, approved media, and a revocable browser launch credential scoped to the project. It does not contain administrator, management, or Provider credentials.

Revoke the package's runtime channel from Publish & API when existing copies should stop launching.

Share the interactive story

A published interactive story can be presented by a web or native player. The player owns its controls and surrounding experience while the published story keeps its scenes, choices, state changes, and endings consistent.