Interactive video · PATH Player & PATH Studio

Watch a story.
Then change it.

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.

Introducing PATH.
How branching works

One opening. More than one ending.

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.

Interactive illustration · not video
Decision

Choose the next path.

Illustrative paths
  1. 01Opening
  2. 02Decision
  3. 03Outcome
  4. 04Return

An opening leads to a decision. Open the Player below, or enable JavaScript to explore this illustration.

Open PATH Player ↗
PATH Player

Experience the story.

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 ↗
Decision illustration · the real Player uses your media and story state.
Authoring illustration · open Studio to edit a real project.
PATH Studio

Create the possibilities.

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 ↗
Available in the current source

What PATH does today.

  1. 01Branching video sections

    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.

  2. 02Interactive decisions

    The creator’s prompt and available numbered choices appear at the end of a section. Long labels and descriptions wrap.

  3. 03Hidden, locked and mystery paths

    An unavailable choice can be hidden, shown locked, or shown as “Undiscovered”, so a story can hint at what is still to find.

  4. 04Discoveries and story variables

    A choice can set run variables and make discoveries. Variables reset on a new run; discoveries persist in this browser across runs and rewinds.

  5. 05Paths and historical rewind

    Paths opens a map of your route and pauses playback. Explicitly return to an earlier decision; later choices in the run are removed.

  6. 06Visual graph authoring

    Arrange sections, decisions and endings on a canvas, with pan, zoom, multi-select, undo and keyboard shortcuts.

  7. 07Conditional choices

    Build “Available when” rules from choices made, places visited, variables and discoveries. No JSON editing needed.

  8. 08Preview in the real Player

    Run the current draft in the actual PATH Player, from a chosen starting point, with simulated variables and discoveries.

  9. 09Local-first autosave and backups

    Projects autosave to this browser, with clear saving and error states. Download an editable .pathproj backup at any time.

  10. 10Exportable Player manifests

    Export a validated path-story .json that runs independently in PATH Player and streams through public Mux playback IDs.

Feature illustration · not a live Player
Section 2A
0:12 / 0:42
Source video in Mux
in 1:10out 1:52

Branching video sections

The Player’s timeline is section-local, not a preview of the full story.

Browser playback, device behavior and accessibility still need manual review. Public Mux availability depends on the asset.

How PATH works

Footage, story, play.

  1. 1

    Prepare your footage

    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.

  2. 2

    Build it in Studio

    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.

  3. 3

    Preview, export, play

    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

No published stories yet
PATH story library

More paths ahead.

Stories will appear here after their playable routes, editorial details and media rights have been reviewed.

Create a story in Studio ↗
Documentation

Everything PATH does, and how.

  1. 01Introduction
  2. 02PATH Player
  3. 03PATH Studio
  4. 04Working with video
  5. 05Saving and exporting
  6. 06Advanced reference
Read the docs →
Tutorials

Create your first interactive video.

  1. 1Understand the PATH workflow
  2. 2Prepare your video clips
  3. 3Obtain public Mux playback IDs
  4. 4Open PATH Studio
  5. 5Create a new project

Continue through sections, decisions, connections, preview, export and an editable backup.

Explore the tutorials →
Local-first

Your project lives in your browser, and in the files you keep.

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.

IndexedDB
Working copy, autosaved. Not a backup.
.pathproj
Editable backup. Reopen it in Studio.
.json
Runtime manifest. Plays in PATH Player.

Questions

Do I need an account?

No. Neither PATH Player nor PATH Studio has accounts or sign-in. Open Studio and start a project.

How are projects saved?

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.

How do I add my video?

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.

Does PATH host my videos?

No. Video streams from Mux using the public playback IDs in your story. PATH doesn’t store or host footage or published stories.

What is a .pathproj file?

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.

How do story manifests work?

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.

How do I share a story?

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.

Start a story.

Open Studio ↗Follow the tutorialsIn your browser. No account. Best on a desktop.