Host a reveal.js deck with controlled sharing

To host a reveal.js presentation in Lumdeck, upload its static HTML and local assets as a ZIP. Lumdeck supplies the share link and access controls; you continue editing the deck in reveal.js.

Package the deck

1. Put the presentation entry point at index.html.
2. Include the local dist, plugin and asset folders actually referenced by the deck.
3. Use relative paths and include images, fonts and scripts needed at runtime.
4. ZIP those files with index.html at the root, or within one top-level folder.
5. Upload the ZIP and read any validation report before sharing.

Do not upload node_modules, source-control folders, credentials or the development server. The hosted bundle cannot run server-side code. Remote dependencies may be restricted by the viewer's network policy; local assets are the most predictable choice.

Check the result

Open the deck, advance horizontally and vertically, test fragments and inspect its slide indicator. Lumdeck detects reveal.js slide changes automatically. Test embedded demos separately, especially on mobile, and keep a lightweight fallback for heavy scenes.

Choose an anyone-with-the-link, password or email-code link; configure expiry and revoke it when no longer needed. Upload a new version to the same presentation to preserve links that follow the current version. Retention still follows your plan.

Framework documentation checked 7 October 2026: reveal.js installation ↗ (opens in a new tab). Its basic setup is static HTML; features such as external Markdown need a web server. Lumdeck serves the uploaded files, subject to its bundle rules. For another hosting approach, read Lumdeck and static hosting.

Last updated: 7 October 2026. See current plans and product scope and limits.