inklewriter deserves its affection. Built by inkle — the studio behind 80 Days and Sorcery!, and the ink narrative language that much of the games industry uses — it made branching stories feel like writing rather than engineering: type, offer choices, let the tool worry about joining paths back together. Its handling of converging branches remains some of the most elegant UX the form has seen. It is free, and it runs in the browser with nothing to install.
It is also deliberately minimal, and inkle’s development energy has long been directed at their games and at the ink ecosystem rather than at inklewriter, which has stayed essentially the simple tool it set out to be. Writers tend to leave it not in frustration but by outgrowing it: wanting to see the whole structure at once rather than thread by thread, wanting drafting help, analytics, or a path to larger work. StorySplice is built for exactly that next size up — while keeping the no-code, browser-based, writing-first character that made inklewriter lovable.
For a first branching story, inklewriter’s radical simplicity is a feature no fuller tool can copy: there is nothing to learn, and the writing-first flow keeps beginners writing instead of diagramming. Its automatic rejoining of paths quietly teaches the single most important structural habit in the form. And inkle’s wider ecosystem — the ink language, the inky editor, Unity integration — is the professional path for studio narrative work, a lineage inklewriter connects to and StorySplice does not attempt. For game-studio pipelines, ink is the standard and inkle’s tools are the way in.
The map is the biggest difference in daily writing: a story of eighty scenes is a shape you can see, drag, and reason about structurally, not a thread you scroll. Drafting help is the second — Splinter, Branch Wizard, and Expand attack the blank-branch problem inklewriter leaves entirely to you, always as accept-or-reject suggestions. And finished work has somewhere to go: a hosted library or unlisted links, automatic reader progress saves, Pro analytics on reader paths, and standard-format export so the manuscript is never stranded.
| Feature | StorySplice | inklewriter |
|---|---|---|
| Price | Free plan; Pro $6/mo or $48/yr for AI capacity, export, analytics | Free |
| Structure view | Full zoomable story map showing every scene and connection at once | Writing-first threaded view; elegant automatic handling of rejoining paths |
| AI writing tools | Splinter, Branch Wizard, Expand, write/rewrite/continue with accept-or-reject | None |
| State and markers | None — consequence lives in structure and prose | Simple markers and conditional text for remembering choices |
| Publishing | Community library or unlisted link; readers need no account; progress saves | Share a link to the story hosted on inklewriter |
| Reader analytics | Built in on Pro | None |
| Export and interop | JSON free; Twee and Twine 2 HTML on Pro; imports Twine and Twee | Limited; inkle’s broader ecosystem centers on the ink language and its tools |
| Active development | Actively developed | Kept available by inkle; development has long been quiet |
inklewriter is a product of inkle Ltd, and ink and inklewriter are associated with inkle’s trademarks. StorySplice is an independent product and is not affiliated with or endorsed by inkle Ltd. Comparison based on publicly available information as of July 2026 — spotted an inaccuracy? Email info@threadlimit.co and we will fix it.
There is no direct inklewriter or ink import. The practical route is to paste a story’s prose into Splinter, which rebuilds branching structure from linear text with AI-proposed fork points — imperfect, but it turns migration into an afternoon rather than a retype.
As of mid-2026 inklewriter remains online as a free tool, though inkle’s active development has for years focused on the ink language and their games. Check inkle’s own site for current status — and note our comparison is only as current as its date.
No — no ink import or export. Interop here is with the Twine ecosystem: Twine HTML and Twee import free, Twee and Twine HTML export on Pro, JSON always free.
Nearly, with a different flavor: you write scenes and drag connections rather than following a thread. There is no code or markup either way. The map costs a few minutes of orientation and pays for itself the first time a story grows past a dozen scenes.
Nothing to try — creating, publishing, and 10 daily AI calls are free, and there is no lock-in on the way out either, with JSON export free and standard Twee/Twine export on Pro.