The best narrative design tools in 2026
A narrative design tool has to do three jobs: let writers build branching stories, let the team test them before the game is ready, and hand the result to a game engine. Here are the tools game studios use for that in 2026, what each one is good at, and who it fits.
Written by the LoreHub team. Facts about other tools come from their own websites and docs, checked in November 2026. Spotted something out of date? Tell us on Discord.
At a glance
| How you write | Engines | Localisation | Price | |
|---|---|---|---|---|
| LoreHub | Browser, visual canvas + wiki | JSON/YAML/OSF for any engine | Built in, no language cap | Free plan; per world |
| articy:draft X | Desktop (Windows, macOS) | Official Unity and Unreal | Built in, DeepL, Excel | Free edition; subscriptions |
| Arcweave | Browser, visual boards | Official Unity, Unreal, Godot | Team plan | Free Basic; Pro, Team |
| Yarn Spinner | Script, VS Code + browser | Runtime for Unity, Godot, Unreal | Line IDs, string tables | Open source |
| ink + Inky | Script, desktop editor | JSON + C#/JS runtimes, Unity | Not built in | Open source |
| Twine | Linked passages | HTML or Twee source | Not for stories | Open source |
| Dialogic | Inside the Godot editor | Godot only | CSV workflow | Open source |
| Pixel Crushers Dialogue System | Inside the Unity editor | Unity only | Localized text tables | Paid Unity asset |
We make LoreHub, so it is on this list; we have tried to be as fair to the others as to ourselves. Facts about other tools come from their own sites and documentation.
1. LoreHub: dialogue and lore for the whole team
LoreHub is a browser-based dialogue builder and worldbuilder. Writers build branching dialogue on a visual canvas with variables and conditions, play it in a player under the canvas, and translate every line in the Translate tab. The Route Planner checks what each dialogue requires and produces across a story. Stories are plain-text OSF files you can keep in Git or Perforce, and the export is a documented JSON schema for any engine.
Fits: narrative teams that want writers, designers, translators and programmers in the same story. Keep in mind: there is no engine plugin; you load the JSON with your own code, as the Unity tutorial shows. Free plan available.
2. articy:draft X: the established desktop tool
articy:draft is desktop narrative-design software for Windows and macOS. It covers characters, dialogues and branching stories with scripting, has official Unity and Unreal integrations, and a mature localisation and voice-over toolset with DeepL and Excel round-trip. The free edition has the full toolset, capped at 700 objects per project; multi-user work is a separate offer.
Fits: studios that want a proven desktop tool with engine importers. Read our articy:draft comparison.
3. Arcweave: visual boards in the browser
Arcweave is a browser-based, collaborative narrative design and prototyping platform built on boards, items and components, with Play Mode for testing. It has official Unity, Unreal and Godot integrations. The free Basic plan allows 3 projects and 200 items per project without commercial use; localisation, project history and the API are on the Team plan.
Fits: teams that want visual prototyping in the browser with engine plugins.
4. Yarn Spinner: dialogue as a script language
Yarn Spinner is an open-source dialogue language and runtime. Writers write .yarn scripts, with a VS Code extension for graph view, preview and debugging, and the runtime plays them in Unity, Godot or Unreal. Game code implements the commands and functions a script calls.
Fits: script-comfortable writers working closely with programmers. Read Yarn Spinner vs LoreHub.
5. ink and Inky: a narrative scripting language
ink is inkle's open-source narrative language: knots, stitches, choices and diverts in plain text, edited in the Inky desktop editor with live preview. It compiles to JSON with C# and JavaScript runtimes and a Unity integration. Localisation is not built in.
Fits: text-heavy, choice-driven games written by script-first writers.
6. Twine: the fastest way to prototype
Twine is free and open source. You link passages, choose a story format such as Harlowe or SugarCube, and publish standalone HTML or export Twee source. Game engine export and story localisation are not part of it.
Fits: prototypes, game jams and web interactive fiction. Read our Twine alternative guide.
7. Dialogic: dialogue inside Godot
Dialogic is an open-source Godot plugin with a timeline editor of events such as text, conditions, animations and signals, variables for branching, and a CSV translation workflow. It is tied to Godot.
Fits: Godot teams that want dialogue and visual-novel tools inside the engine.
8. Pixel Crushers Dialogue System for Unity
A paid Unity asset with a dialogue database and editor inside Unity, plus quests, dialogue UI and localized text tables, extended by add-ons. It is Unity-only and its vendor notes it takes time to learn.
Fits: Unity teams that want dialogue, quests and UI in one in-engine package.
Worldbuilding tools
If your team needs a lore bible more than a dialogue editor, World Anvil (articles, maps, timelines and manuscripts, with paid Guild tiers) and LegendKeeper (a collaborative wiki with maps, timelines and whiteboards, still in beta) are made for writers and game masters. Neither exports game dialogue. LoreHub's Worldbuilder keeps the lore in the same world as the dialogue; our environmental storytelling guide is a good place to start.
How to choose
- Who writes? Script-comfortable writers do well with Yarn Spinner or ink; writers who think in flows prefer a canvas such as LoreHub, articy:draft or Arcweave.
- Which engine? One engine for good: in-engine tools like Dialogic or Pixel Crushers are simplest. Several engines or your own: pick a tool with an open export.
- How many people? For a team that edits the same story every day, browser tools with live collaboration save the most time.
- How many languages? Check where translation lives and what it costs on each plan.