Lite, Pro, and Pack: which one should you use?

Choose by task.

• Use SlideStage Lite to open, present, and locally convert .stage decks.
• Use slidestage-pack to turn an HTML deck into .stage.
• Use SlideStage Pro to host a team deck library.

SlideStage Lite

Lite is the local-first runtime. It needs no account, backend, or database.

Use Lite when you want to:

• Open a .stage file.
• Present with speaker tools.
• Validate a deck locally.
• Convert HTML into .stage in the browser.
• Deploy a static player to Cloudflare Workers.

Lite is not a team library. It does not manage server-side accounts, permissions, or shared storage.

SlideStage Pro

Pro is the self-hosted team platform. It consumes Lite packages and adds server-side capabilities.

Use Pro when you need:

• Login and invite-based registration.
• .stage upload and storage.
• Team deck browsing.
• Server-side notes and annotations.
• Docker Compose deployment.

Pro should not copy or patch Lite source. Shared runtime behavior belongs upstream in Lite packages.

slidestage-pack

Pack is the packaging tool.

Use Pack when you need to:

• Convert reveal.js, impress.js, huashu-design, html-ppt-skill, or plain HTML.
• Detect the source framework.
• Pick the right conversion mode.
• Verify the generated .stage.
• Produce stable zip bytes for repeatable fingerprints.

Pack does not play or host decks. It produces files for Lite and Pro.

Common combinations

Personal authoring:

HTML deck -> slidestage-pack -> deck.stage -> SlideStage Lite

Team library:

HTML deck -> .stage -> SlideStage Pro

Static self-hosting without accounts: deploy Lite.

Self-hosting with accounts and uploads: deploy Pro.