Stories
No published stories yetMore paths ahead.
Stories will appear here after their playable routes, editorial details and media rights have been reviewed.
Create a story in Studio ↗In PATH Player, viewers decide where a video goes next. In PATH Studio, you build those decisions on a visual map in your browser. No account needed.
Follow an opening, make a choice and see where it leads. Then return to the decision and try the other way. In this illustration, following the light unlocks a third path.
An opening leads to a decision. Open the Player below, or enable JavaScript to explore this illustration.
Open PATH Player ↗A custom Video.js v10 player for public Mux video. Viewers watch a section, choose, and continue down their route. Paths shows where they’ve been and lets them return to an earlier decision.
It works on its own: open a Player manifest, or play an ordinary video with no branches. You don’t need Studio to watch.
Open PATH Player ↗A desktop authoring workspace that runs in your browser. Arrange sections, decisions and endings on a canvas, write prompts and choices, add conditions, and preview in the real Player.
No account and no required backend. Projects autosave to this browser, and you can download an editable backup at any time.
Open PATH Studio ↗Each section plays one range of a public Mux video. The seek bar and time belong to that section only, so viewers never see what’s ahead.
The creator’s prompt and available numbered choices appear at the end of a section. Long labels and descriptions wrap.
An unavailable choice can be hidden, shown locked, or shown as “Undiscovered”, so a story can hint at what is still to find.
A choice can set run variables and make discoveries. Variables reset on a new run; discoveries persist in this browser across runs and rewinds.
Paths opens a map of your route and pauses playback. Explicitly return to an earlier decision; later choices in the run are removed.
Arrange sections, decisions and endings on a canvas, with pan, zoom, multi-select, undo and keyboard shortcuts.
Build “Available when” rules from choices made, places visited, variables and discoveries. No JSON editing needed.
Run the current draft in the actual PATH Player, from a chosen starting point, with simulated variables and discoveries.
Projects autosave to this browser, with clear saving and error states. Download an editable .pathproj backup at any time.
Export a validated path-story .json that runs independently in PATH Player and streams through public Mux playback IDs.
The Player’s timeline is section-local, not a preview of the full story.
Hold the last frame or loop a chosen media range while the viewer decides. An optional countdown can wait, select a choice, or continue to a destination.
Hidden choices don’t appear until their condition is met.
Hidden choices are omitted. Locked choices retain their labels. Mystery choices conceal their labels. This is presentation, not content protection.
litLantern = truesecretVariable changed
Secret found
Variable restored
Secret kept
Variable reset
Secret kept
Run state can be restored. Discoveries remain, when browser storage is available. There is no cross-device sync.
You chose: Follow the light
Returning removes later choices in this run. Discoveries remain.
Rewind restores the run to just before the selected decision. Discoveries remain. Closing Paths without travel keeps your position, paused.
Build the graph in Studio rather than editing JSON. The Inspector provides timing, prompts, choices and destinations.
secretlitLantern = trueCombine all, any and not conditions, and choose how an unavailable route appears.
This static illustration does not run footage. Studio embeds the actual PATH Player here after validating the draft.
Preview uses the same validated runtime data as export. Editing the draft stops the preview; run it again to refresh.
IndexedDB autosave. Can be cleared or evicted.
Your editable backup file. Keep it.
IndexedDB holds the working copy. Keep a downloaded .pathproj somewhere safe: browser storage can be cleared or evicted.
{
"format": "path-story",
"version": "1.0.0",
"id": "my-story",
"title": "A Sample Route",
"entry": "start",
"navigation": { "map": "enabled" },
"media": {
"clip": { "playbackId": "PUBLIC_MUX_PLAYBACK_ID" }
},
"nodes": { "…": "story nodes" }
}.json is the runtime story. .pathproj is the editable Studio backup. Neither download includes video files.
Browser playback, device behavior and accessibility still need manual review. Public Mux availability depends on the asset.
Edit your clips and upload them to your own Mux account with a public playback policy. Copy the public playback ID for each video.
PATH doesn’t upload or host video.
Paste playback IDs into the media library. Place sections, decisions and endings on the canvas and connect the choices.
Autosaves to this browser. Keep a backup.
Preview in the real Player inside Studio. Export a Player .json and open it in PATH Player. Download a .pathproj to keep editing later.
Sharing means sharing the file; PATH doesn’t publish.
Stories will appear here after their playable routes, editorial details and media rights have been reviewed.
Create a story in Studio ↗Continue through sections, decisions, connections, preview, export and an editable backup.
Explore the tutorials →Studio autosaves to IndexedDB in this browser profile and site origin. There is no cloud copy. Browsers can clear or evict that storage, so download a .pathproj backup and keep it somewhere safe.
No. Neither PATH Player nor PATH Studio has accounts or sign-in. Open Studio and start a project.
Studio autosaves to IndexedDB in your browser, for the same browser profile and site origin. It is not a cloud backup: browser storage can be cleared or evicted. Download a .pathproj regularly and check that the file was saved. This editable backup does not contain video files; local media needs relinking after reopening.
Upload your footage to your own Mux account with a public playback policy, then paste each public playback ID into Studio’s media library. Studio doesn’t upload video. You can add local files to plan with, but they must be replaced with public Mux IDs before export.
No. Video streams from Mux using the public playback IDs in your story. PATH doesn’t store or host footage or published stories.
An editable backup of a Studio project: the story, layout, media references, variables and settings. Open it in Studio to keep editing. It doesn’t contain video.
Export Player .json writes a validated path-story manifest. Version 1.0.0 covers ordinary held decisions; version 1.1.0 adds loop and countdown playback. It contains public Mux IDs and runtime story data, not editor settings, and plays independently of Studio.
PATH doesn’t publish stories. You can share the exported .json for others to open in PATH Player, or include it with a PATH Player build you host yourself. Stories on this site are curated by the PATH project.