Interactive Film Tools Compared (2026)

Four questions sort the field faster than any feature grid. Where must it play — a web page you can link, a PC or console build, or a cinema screen with a professional playback system? Do you want to write logic, or click logic? What kind of branching — switching between pre-made clips, or an engine computing scenes around video inserts? And who is paying, for how long, and with what distribution plan?

A few heuristics from production. A script that is mostly “the viewer picks a branch” fits a no-code video tool; the moment you want hotspots on stills, inventories, meters, or QTE with timing curves, you are in engine territory. Plan the graph in a cheap design tool before choosing the runtime — the graph survives tool changes, exports do not. And treat pricing pages as snapshots, not contracts: the figures below carry a check date for a reason. The structural questions behind the table are covered in Branching Narrative Structures; the format basics, in What Is an FMV Game.

Six tools, checked 30 September 2026 against their official sites:

The fastest route from a finished script to a clickable film on the web. Stornaway is browser-based and no-code: you upload clips, connect them into islands and paths, and the player switches between pre-made branches. Export targets, per the official site: the web as the standard destination, with Unity and Unreal export paths on the paid tiers — a bridge into engine territory if a project grows. Pricing at check time: a free tier, Indie at £35/month (£350/year), Pro at £80/month (£800/year), enterprise custom.

The company publicizes case studies with interactive-film director Paul Raschid, which tells you the intended altitude: streaming-style interactive video with professional crews. Where it stops: anything beyond video switching. Inventories, spatial puzzles, meters, state that survives across scenes — that is engine work, and Stornaway does not pretend otherwise. For a first interactive film with real footage and a web release, it is the shortest path I know.

The professional end of the market. CtrlMovie is the authoring and playback system behind Late Shift (2016) and The Bunker; its official editor page positions it for real-time branching playback, cinema-grade screenings, and app layers with mobile sync. There is no public price — licensing goes through sales — and that tells you the tier: funded productions with theatrical or platform ambitions, not solo creators.

What you pay for is the invisible part: playback that switches branches in real time at cinema scale, and the operational discipline of screenings where an audience votes or apps steer the film. If your distribution plan includes a cinema with a live audience, start that conversation early. If your plan is a web link or a Steam page, this is not your tier — and no feature list will make it one.

The engine route buys everything video-switching cannot do: hotspots on stills, QTE with timing curves, inventories and meters, state that persists, and export to PC, consoles, and mobile. Unity’s pricing at check time: Personal is free for creators under $200,000 of revenue in the last twelve months; Pro is $2,200 per seat per year. Naninovel — $80 one-time per its official site — is the shortcut for dialogue-heavy projects: a visual-novel framework inside Unity, with branching scripts, speakers, and endings as first-class objects.

My own FMV-01 uses Unity without Naninovel: a custom graph of five node types — dialogue, choice, still, cutscene, ending — authored as ScriptableObject data, because the hotspots-on-stills interaction and the hire-or-walk fork needed tighter control than a VN template. The working stack is documented in the first devlog. The price of the engine route is engineering: C# or visual scripting, asset pipelines, build maintenance. It is the right route when interaction design, not authoring speed, is the project’s centre of gravity.

Neither tool plays your footage — both save you from the mistake that kills FMV projects: shooting before the graph is understood. Arcweave is a branching-story mapper: boards, components, connections, with export for design documentation. Pricing at check time: a free tier, Plus £10/month, Professional £25/month. Twine is free, open-source, and publishes to HTML — the standard first stop for learning branching by writing it.

The division of labour I recommend: Twine for text drafts and learning the shape of a story; Arcweave when the graph outgrows a text outline and needs boards, groups, and shared vocabulary with a crew. Restructuring a graph in either tool costs nothing; restructuring a shot list costs a reshoot. In my teaching I start students on Twine and move them to Arcweave or engine graphs once the fork count stops fitting a screen.

Disclosure first: I build FMV Builder, so this is the least neutral section on the page. What it is: an authoring studio for interactive films and visual novels. Acts, scenes, and episodes live in a bin; each scene is a graph (Enter → Moments → End); the FMV mechanics — dialogue choices, QTE, hold, explore, items, dialogue trees — attach to moments on the scene spine; a timeline with audio tracks and a viewer with inventory, meters, and a diegetic mode complete the room. Projects validate and export to a web ZIP or an offline Electron build.

Status: pre-release, in internal testing — there is no public pricing and no launch date to promise. Who it is for: director-authored projects where one person wants to hold film and interaction in the same room, the workflow my FMV-01 prototype grew out of. The honest comparison: Stornaway will get a web film out faster today; FMV Builder aims at keeping the whole production — video, stills, hotspots, mechanics, novel — in one authored space. Details and screenshots are on the FMV Builder page.

In practice the tools compose rather than compete. On FMV-01 the sequence is: sketch the graph before shooting with hubs marked, so forks stay narrow; write the script branch-aware; shoot for branches — coverage per fork, not per scene; shoot stills with planned hotspots; encode clips with transition speed as the metric, because codec choice is a design decision; assemble the graph as ScriptableObject data with five node types; playtest forks with fresh viewers; keep one source of truth for state.

FMV Builder exists because this process kept reassembling itself across different programs — the tool is the pipeline made explicit. If you are starting today: plan the graph cheap, pick the runtime by distribution target, and shoot only after the forks are narrow. The craft details live in the FMV-01 devlog; the prototype itself is on its project page.