A writing tool should be a room you can leave with your manuscript. StorySplice exports to two standard interactive fiction formats — Twee, the plain-text notation the Twine ecosystem shares, and Twine 2 HTML, a file you import straight into the Twine editor — plus JSON, which is free on every plan and contains the complete story as structured data. Twine and Twee export are Pro features ($6/mo or $48/yr); the point of this page is that even the paid door is a real door, and you should know exactly what walks through it.
Why leave? Usually to gain what StorySplice deliberately omits: story-format scripting. A structure drafted visually here — perhaps with AI assistance — can pick up SugarCube inventory logic or custom CSS in Twine. Or you simply prefer owning a local file. Both are good reasons, and the export is built to make them cheap.
Open the export picker. In the Library, find your story and choose Export. Three formats are offered: JSON (free, the native format), Twee, and Twine HTML — the latter two marked Pro. Every scene and choice in the story is included regardless of format; export never truncates.
Choose Twee for text workflows. Twee export downloads a .tw file in standard Twee 3 notation: a StoryTitle passage, a StoryData passage carrying a generated IFID and a Harlowe 3 format declaration, then one passage per scene. It is the right choice for tweego pipelines, version control, or any editor — it is readable plain text.
Choose Twine HTML to open in Twine directly. Twine HTML export downloads a complete Twine 2 story file. In Twine, use Library, then Import, and the story appears ready to edit — no intermediate steps. The file declares the Harlowe 3 format and includes empty stylesheet and script sections for you to fill.
Know how your story is translated. Scene labels become passage names; unlabeled scenes get names derived from their internal IDs, title-cased with underscores and hyphens turned to spaces (this avoids Harlowe misreading names that start with an underscore as temporary variables), and duplicates are numbered. Each choice becomes a standard link — [[choice text->Target Name]], or the short [[Target Name]] form where the display text matches. Passage content is your prose followed by its links: no macros, no generated code, playable in Harlowe as-is.
Arrange the map in Twine. One thing does not carry: your visual layout. The HTML export places passages on a simple generated grid, so expect to spend a few minutes arranging the graph in Twine to taste. Structure, names, prose, and links are all exactly as you wrote them.
Mind the IFID if you keep maintaining in Twine. Each export generates a fresh IFID — the identifier IF archives use to recognize a story across versions. If Twine becomes the story’s long-term home, keep the IFID from your first export stable there rather than re-exporting over it repeatedly.
Keep a JSON copy either way. JSON export is free, lossless, and instant — scenes, labels, choices, and structure as clean data. Whatever happens in your Twine adventure, the canonical backup costs nothing.
Why interop is the honest policy
Export-to-competitor is a strange feature to build, so here is the reasoning. Interactive fiction has a healthy shared ecosystem with Twee as its plain-text lingua franca, and tools that participate in it deserve more trust than tools that don’t. StorySplice imports Twine formats too, so the relationship is symmetric: draft here and script there, or draft there and restructure here, or move a story out entirely because your needs changed. A subscription should be renewed because the map and the AI tools keep earning it — not because your manuscript is being held.
Frequently asked questions
Is Twine export free?
Twee and Twine HTML export are Pro features ($6/mo or $48/yr). JSON export — the complete story as structured data — is free on every plan, so your work is never locked in behind a paywall.
Will the exported file open in Twine without fixes?
Yes. The HTML export imports directly into Twine 2 and declares the Harlowe 3 format; since the content is prose and standard links with no macros, it plays immediately. The layout is a generated grid you will want to rearrange.
Can I export to SugarCube instead of Harlowe?
The file declares Harlowe 3, but the content is format-neutral — plain prose and standard links work identically in SugarCube. Change the story format in Twine after importing and nothing breaks.
Does the export include AI-generated scenes?
The export includes every scene in the story, however it was written. Accepted AI drafts are ordinary scenes — there is no watermark or distinction in the file.
What is lost in a round trip — export to Twine, then import back?
Almost nothing, because both halves speak prose-and-links: scenes, labels, choices, and structure survive. Anything you added in Twine that is code — macros, styles, scripts — is stripped on the way back in, as the import guide details.