Export, delivery, and sharing
First decide whether the goal is reading, further work in another tool, or future recovery of the entire project.
| Product | Main delivery | Check before delivery |
|---|---|---|
| Longform | Markdown/TXT prose, JSON backup | Chapter order and actual prose |
| Short fiction | Markdown/TXT/JSON | Completion, prose, review, and version |
| Screenplay | Fountain/FDX/print | Scenes, formatting, sources, and dual review |
| Comic | PNG/WebP/CBZ/PDF, subject to version conditions | Storyboard or visual edition, images, and lettering |
| Motion-comic materials | Prompt/reference tool-adaptation package | Shots, asset versions, target-tool constraints |
| World | World sharing package | Semantic scope, provenance, attribution, license |
| Interactive work | Product releases and saves | Production completeness and actual play state |
Recommended delivery sequence
- Check the selected work and version.
- Handle unconfirmed candidates, missing content, and blockers.
- Save the required release or history record.
- Open the exported file and spot-check its beginning, end, and key content.
- Keep a separate complete backup.
“Publish” usually preserves a local immutable version; it does not automatically post the work to a public website.
Short-fiction release JSON stores a frozen delivery manifest. It is neither the complete project JSON exported by data management nor a .storyforge.json workspace package. For formats, media inclusion, and recovery entries, see Saving, backup, and recovery.
Before sharing
Check rights to source text, images, audio, and references. Full backups may contain private manuscripts, candidates, and run records; a recovery file is not necessarily suitable for public sharing.
Motion-comic packages still require an external video tool. Finished comic storyboards do not mean all visual-edition images are present.
Continue: Version meanings · Privacy.