Choose the page you already have
Use an HTML file for a single-file page or a ZIP for a folder with styles, scripts, and images. You can start with an existing build instead of rewriting it into a new framework.
SaveKit use case
Sometimes the page already exists. The missing piece is a reliable URL that someone else can open without installing your tools or receiving a folder attachment. SaveKit closes that gap between a finished HTML folder and a page that is ready to share.
A good fit for: Client approvals, portfolio drafts, side-project demos, internal reviews, and feedback requests.
Use an HTML file for a single-file page or a ZIP for a folder with styles, scripts, and images. You can start with an existing build instead of rewriting it into a new framework.
Preview the page and send the URL to one person who can give useful feedback. A link is easier to review than a ZIP attachment because everyone sees the same published version.
When the page needs a correction, publish the updated version and share the resulting link. Keep a short note with the version or review date so feedback stays tied to the right build.
Before you publish
These checks prevent the most common surprises after a folder becomes a public URL.
Common questions
No. SaveKit accepts a prepared HTML page or static ZIP build, so the page can stay in the tools you already use.
Yes. A previewable public URL is useful for design review, copy review, and early audience feedback before the final announcement.
Do not put secrets, private credentials, payment details, or server-only files in a public static build. Treat everything in the published folder as potentially visible.
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