Start with the output
Use a single HTML file or a ZIP of complete static files. Build framework or tool exports before uploading them.
Limited-time offerPro & Max plans — 20% offSave 20% on monthly and yearly billing.
Save 20% on monthly and yearly billing.
Static output · 6 export paths
Publish a built, exported, or downloaded static artifact as a browser preview. These pages explain the file contract and the limits of each tool-shaped workflow.
Choose an export
Every page includes the audience, the static file workflow, the review boundary, and a link to start publishing.
For a component library
Publish a Storybook static build by uploading the generated storybook-static output as a ZIP for browser review.
Open workflow
For documentation review
Build a Docusaurus documentation site locally, zip the generated build output, upload it, and share a static preview link for review.
Open workflow
For an interactive chart
Share a Plotly HTML export as a browser preview link for data reviews, interactive charts, reports, and presentations.
Open workflow
For an exported site
Create a Webflow export preview by uploading the exported static HTML, CSS, JavaScript, and assets as a browser-ready project.
Open workflow
For an interactive design
Share an HTML design exported from a Figma-to-HTML workflow as a browser preview link for client and team review.
Open workflow
For a complete front-end page
Host a CodePen export as a complete HTML, CSS, JavaScript, and asset preview link for clients, teammates, and reviewers.
Open workflow
Use a single HTML file or a ZIP of complete static files. Build framework or tool exports before uploading them.
Give the recipient one question about the task, artifact, layout, content, or interaction instead of an open-ended request.
A preview is not a production site, native integration, private workspace, or live data service. Keep that next step explicit.