How Parlance compares
Different tools fit different shapes of game and team, and pretending otherwise helps nobody. This page compares Parlance honestly with the tools we most often get asked about — including where they are the better choice.
At a glance
| Parlance | articy:draft | Twine | ink | Yarn Spinner | |
|---|---|---|---|---|---|
| Source format | ✓ plain JSON, per-entity files, clean diffs | ✗ proprietary project (X exports XML/JSON) | ◑ HTML/Twee archive | ✓ plain-text .ink |
✓ plain-text .yarn |
| Visual node editing | ✓ dialogue, quest, location canvases | ✓ mature flow editor | ✓ passage map | ✗ text-first | ◑ graph view, text-first |
| Structured entities beyond dialogue (quests, factions, items, endings) | ✓ 12 first-class types | ✓ templates & objects | ✗ | ✗ variables only | ✗ variables only |
| State-aware dialogue selection | ✓ dialogue ladders, spec'd + conformance-tested | ◑ via scripting | ◑ via macros | ◑ weave/logic in-script | ◑ via commands |
| Static validation & CI story | ✓ 18 check families on save + ci-check + reference validator |
◑ in-app checks | ✗ | ◑ compiler errors | ◑ compiler errors |
| In-tool playtesting | ✓ seeded, rewindable, forced outcomes, live state | ✓ presentation/simulation | ✓ play in browser | ✓ inky player | ✓ preview |
| Shareable playable build of a scene | ✓ single-file HTML export | ✗ | ✓ whole story is HTML | ◑ export for web via tooling | ✗ |
| Branch-based review workflow | ✓ narrative diffs, comments, suggestions, verdicts — plain git | ✗ (server products exist) | ✗ | ◑ text diffs review fine in PRs | ◑ text diffs review fine in PRs |
| Engine integration model | ✓ engine reads authored files; published contract + conformance vectors | ◑ exporter + official Unity/Unreal plugins | ◑ web-native; engine use is DIY | ✓ excellent Unity runtime; C/C#/others | ✓ first-class Unity |
| Localization & VO tooling | ✓ stable keys, coverage, stale detection | ✓ mature | ✗ | ◑ community tooling | ◑ line-tag based |
| AI / MCP integration | ✓ MCP server, validated writes | ✗ | ✗ | ✗ | ✗ |
| Open spec | ✓ MIT schemas + conformance vectors, published separately (details) | ✗ | ◑ formats documented | ✓ open source | ✓ open source |
| License / price | free, incl. commercial use; not open source | commercial, per-seat | free, open source | free, open source | free, open source (paid add-ons) |
✓ first-class ◑ possible with work or partial ✗ not a goal of the tool
This table is maintained by us, about our competitors — read it with that grain of salt, and tell us if a cell is unfair or out of date.
Choose articy:draft if…
You're a mid-size-or-larger studio that wants a mature, commercial, all-in-one narrative pipeline with official Unity and Unreal plugins, template-driven game objects, and years of shipped-title track record. It's the most feature-complete commercial tool in this space. The trade-offs are the proprietary project format (version control works on binary/opaque data, with server products sold to solve the collaboration problem git would otherwise give you) and per-seat licensing.
Choose Twine if…
You're writing hypertext fiction that ships as a web page, teaching interactive fiction, or jamming — nothing gets you from zero to playable branching story faster, and the output is the delivery format. It's not built for driving a game engine, structured game data, or team review workflows.
Choose ink if…
Your game is prose-first and your writers are comfortable in a lightweight scripting language. ink's writing ergonomics for dense, weave-style branching prose are unmatched, its Unity integration is excellent, and its shipped-game pedigree (80 Days, Heaven's Vault, countless others) speaks for itself. You'll be hand-rolling the structured layer — quests, factions, items, endings — and the static guarantees beyond compiler errors.
Choose Yarn Spinner if…
You're Unity-first and want a friendly, well-supported dialogue system with a strong community, voice-over-oriented line tagging, and a syntax writers pick up in an afternoon. Like ink, it deliberately stays a dialogue tool — the rest of the narrative data model is yours to build.
Choose Parlance if…
- Your team already lives in git and wants narrative to work like code: branches, reviewable diffs, CI gates.
- Your story is structured data as much as prose — quests, factions, reputation, items, endings, codex — and you want one validated model for all of it, not a dialogue tool plus a spreadsheet.
- You want validation as a guarantee, not a vibe: eighteen check families on every save and in CI, so a dangling reference or an unwinnable quest fails the build instead of shipping.
- You want the engine to read the same files the editor writes — a published contract with conformance vectors instead of an export step.
- You playtest constantly and want seeded, rewindable sessions and one-file playable handoffs.
The fastest way to judge: play the demo, then open it in the editor.