Zip the finished folder
Create an archive from the site folder itself. The archive should contain index.html at its top level, with the assets alongside it or in subfolders referenced by the page.
SaveKit use case
A ZIP file is often the handoff format for a static site: a designer exports a page, a builder downloads a template, or a small team passes around a finished build. The useful next step is a public link, not another round of deployment setup.
A good fit for: Exported site folders, static templates, design reviews, client previews, and short-lived campaign pages.
Create an archive from the site folder itself. The archive should contain index.html at its top level, with the assets alongside it or in subfolders referenced by the page.
Use SaveKit's ZIP hosting flow and enter a title that makes the page recognizable. The title becomes useful context when you later manage more than one published page.
Look for broken asset paths, missing fonts, and buttons that still point to localhost. Make the correction in the source folder, upload the updated ZIP, and publish the version you intend to send.
Before you publish
These checks prevent the most common surprises after a folder becomes a public URL.
Common questions
Yes, as long as you upload the generated static output rather than the source project and the output includes its entry HTML file and assets.
No. ZIP hosting serves static files. PHP, Node.js, database calls, and other server-side code need a runtime elsewhere.
A local development server can hide incorrect relative paths. Previewing the uploaded archive tests the files in the environment that visitors will actually use.
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