Export the production build
Zip the generated output rather than the source project. Keep index.html at the archive root, preserve relative asset paths, and remove caches, credentials, and development-only files.
SaveKit use case
When an AI builder, design tool, or frontend workflow gives you a ZIP, the next job is often simply to let someone else open it. SaveKit turns a valid static build into a URL without asking you to recreate the project in a new hosting stack.
A good fit for: AI-generated site exports, Vite or Astro builds, design handoffs, event pages, portfolio drafts, and temporary campaigns.
Zip the generated output rather than the source project. Keep index.html at the archive root, preserve relative asset paths, and remove caches, credentials, and development-only files.
Upload the ZIP and inspect the actual hosted preview. If images, fonts, or JavaScript are missing, correct the source build and upload a new archive before sharing the link.
Name the page clearly, state whether it is a prototype or production page, and send one specific feedback request with the URL. Use a campaign parameter for each channel you want to compare.
Before you publish
These checks prevent the most common surprises after a folder becomes a public URL.
Common questions
Yes, when the export is a static build with an index.html at its root. The page must not depend on a private development server.
No. SaveKit serves the generated static files. Server-side code, databases, and private API calls need a separate secured runtime.
No. Treat generated output as untrusted until you check links, scripts, accessibility, data handling, and licenses.
Upload the HTML or ZIP build, preview it, and get a link you can send to the next person who needs to see it.
Start publishing