Start with your artifact
If you have one self-contained .html file, use the generic HTML guide. If a framework produces an index.html plus assets, use its packaging guide and check the multi-file requirement before you publish.
Publishing workflows
Start herePublish a single HTML presentationThe fastest path: verify one file, publish without an account, and share the resulting reader URL.Agent workflowPublish an AI-generated HTML deckHand off a finished artifact from Codex, Claude Code, Cursor, or another coding Agent without exposing credentials.Stable linkUpdate a presentation and restore versionsReplace the HTML at one reader URL, inspect immutable history, and restore an earlier version with a reproducible proof deck.FrameworkShare a Reveal.js presentationPackage the Reveal.js build output correctly and preserve its relative assets.FrameworkHost a Slidev deckBuild Slidev for static hosting, zip the contents at the archive root, and publish.ReferenceCompare HTML presentation frameworksChoose the correct artifact and upload path for plain HTML, Reveal.js, Slidev, Marp, and Quarto.FrameworkPublish a Marp presentationExport Markdown as one self-contained HTML deck, inspect it, and use the single-file publishing path.
Current packaging limits
- Anonymous publishing accepts one self-contained HTML file, up to 1 MB, and creates an unlisted deck.
- Free accounts accept one HTML file per deck, up to 5 MB.
- Multi-file zip uploads require a logged-in Pro account and must contain
index.htmlat the archive root. - Remote script references in uploaded deck content are rejected. Bundle framework assets locally instead of relying on CDN scripts.