Prepare the static build
Keep index.html at the root of the folder and make sure asset paths are relative to that file. Open the folder locally once so you can catch missing images or scripts before uploading.
SaveKit use case
If you already have index.html, CSS, JavaScript, and a few images, you do not need a full application deployment just to share the page. SaveKit is designed for this small but common job: take a static build, preview it, and publish it as a link.
A good fit for: Landing pages, prototypes, documentation, portfolios, event pages, and small client handoffs.
Keep index.html at the root of the folder and make sure asset paths are relative to that file. Open the folder locally once so you can catch missing images or scripts before uploading.
Start a new SaveKit page, upload the HTML or ZIP build, and review the preview on the same screen. This lets you check the real page before you send the link to anyone.
Publish when the page looks right. SaveKit gives the page a clean public URL that you can put in a message, issue, profile, or launch post.
Before you publish
These checks prevent the most common surprises after a folder becomes a public URL.
Common questions
No. SaveKit handles the hosting path for a static page, so you can publish a prepared HTML build without setting up a VPS or deployment pipeline.
Yes. Package the folder as a ZIP when it contains multiple assets, keeping index.html at the root of the archive.
SaveKit is for static pages and static builds. A page that requires a server runtime, database, or private backend should stay on an application hosting platform.
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