Skip to content

SlideStage ecosystem · what-is-slidestage

What is SlideStage?

Mirrored docs keep the language used by their source repo. Site chrome stays in your selected language.

SlideStage is a small ecosystem for turning HTML presentations into portable .stage files, then playing or hosting those files in a consistent runtime.

It is built around one idea: keep the fidelity of HTML/CSS/JavaScript slides, but ship them as a single file that can be opened, archived, uploaded, and verified.

Who it is for

SlideStage is useful for designers, developers, product teams, researchers, and internal teams that already create presentations as HTML.

If you only need local playback, use SlideStage Lite.

If you need to package an existing HTML deck, use slidestage-pack.

If you need a team library with accounts, uploads, notes, and annotations, use SlideStage Pro.

Product surfaces

SlideStage Lite

SlideStage Lite is the local-first player and converter. It opens .stage files in the browser or desktop app without accounts, uploads, or a backend.

Lite handles playback, presenter tools, annotations, speaker notes, trust prompts, and browser-side conversion.

SlideStage Pro

SlideStage Pro is the self-hosted team platform. It uses the Lite runtime packages, then adds server-side storage, accounts, invitations, notes, annotations, and Docker deployment.

slidestage-pack

slidestage-pack is the packer CLI and agent skill. It detects common HTML presentation frameworks and emits a strict .stage package.

The .stage contract

A .stage file is a zip container with a root manifest.json and the slide HTML/assets it references.

The format is defined by @slidestage/spec. Lite, Pro, and Pack all rely on that shared contract so the same file can be played and validated consistently.

Typical workflow

  1. Create an HTML deck.
  2. Pack it into .stage.
  3. Open it in Lite for local playback.
  4. Upload it to Pro when the team needs a shared library.