Documentation
Player and Studio reference, from public video to editable backups.
Introduction
What is PATH?
PATH is two connected tools for interactive video. In PATH Player, viewers watch and choose. In PATH Studio, creators build the choices.
PATH Player vs. PATH Studio
The Player is for watching. Studio is for making. You don’t need Studio to watch a story.
How interactive branching stories work
A story connects five node types: Start, Video, Decision, automatic Router and Ending.
PATH Player
Playback controls
Play and pause, section-only seek and time, restart, ±10 seconds, speed, mute, volume, captions and fullscreen.
Story sections
Each section plays only its own range, and the timeline only covers that range.
Decisions
At a decision the Player shows the creator’s prompt and available choices; footage may hold or loop behind them.
Paths navigation
Paths is an on-demand map of the viewer’s route. Opening it pauses playback.
Hidden, locked and mystery routes
An unavailable choice can be hidden, locked or shown as a mystery.
Discoveries
A discovery is made by a choice and stays across runs and rewinds, in this browser.
Rewinding decisions
Return to an earlier decision from Paths, with an explicit confirmation.
Loading and running story manifests
Open a versioned Player .json manifest or load one public Mux section.
PATH Studio
Creating projects
Open Studio and create a project straight away. There is no account.
Media library
Add public Mux playback IDs or local video descriptors, then place them on the canvas.
Story graph
A canvas with pan, zoom, Fit, a minimap, multi-select and keyboard shortcuts.
The five node types
Start, Video section, Decision, automatic Router and Ending have different roles in the story graph.
Connecting nodes
Click an output circle, then an input circle. Or choose a destination in the Inspector.
Automatic Routers and fallback
A Router tests rules in priority order and follows the required fallback when none match.
Variables and conditions
Declare run variables, build “Available when” conditions and add ordered effects, without writing JSON.
Preview
Preview runs your current draft in the real PATH Player.
Autosave and browser storage
Studio autosaves to IndexedDB in this browser. That is not a permanent backup.
Working with video
Using public Mux playback IDs
Upload to Mux yourself, use a public playback policy, and copy the playback ID.
Preparing video footage
Plan your sections and decision points before you upload.
Referencing sections and ranges
A section plays the half-open range [in, out) of its media, in seconds.
Media availability and playback limitations
Public IDs can stop working, and browsers differ.
Saving and exporting
Editable .pathproj backups
A portable, editable copy of your project, including unfinished drafts and layout.
Player .json manifests
A validated path-story 1.0.0, 1.1.0 or 1.2.0 file that runs independently in PATH Player.
Differences between the two formats
.pathproj is for editing. .json is for playing.
Import and export behavior
Importing makes a new local copy. A runtime .json import can’t recover your layout.
Validation and troubleshooting
Issues block export and take you to the affected node.
Advanced reference
Story manifest format
Strict path-story 1.0.0, 1.1.0 and 1.2.0 schemas add features without changing earlier formats.
Conditional route behavior
Conditions are declarative and are evaluated again whenever a decision opens.
Accessibility
Keyboard access and visible focus are built in. Manual review is still pending.
Technical limitations
What PATH deliberately doesn’t do in version 1.
Local Studio MCP and AI authoring
A local coding agent can exchange editable Studio project files; the website has no live MCP connection.
Current scope and limitations
Current Player and Studio capabilities, technical limits and work that still needs manual validation.