ZIP root matters
Place index.html and 404.html at the ZIP output root, not inside an extra nested build folder.
Features
Upload ZIP archives to create static websites
Import a ZIP archive that contains a static website and let StaticX unpack, validate, and publish it as a versioned site.
Works with build systems
Most static generators can produce a dist or build folder. Zip the contents of that folder and upload it to StaticX.
Version one starts at import
In StaticX, importing or creating a site starts the first version. Later explicit publishes create the next immutable versions.
Prepare a ZIP that deploys cleanly
Most ZIP deployment problems come from the wrong root folder. StaticX expects the website files at the archive root.
Build or collect files
Prepare the final HTML, CSS, JavaScript, images, PDFs, and 404.html that should be hosted.
Zip the contents
Compress the contents of dist, build, out, or your site folder, not the parent folder itself.
Upload and publish
StaticX imports the files, starts version 1 when the site is created, and later publishes create new immutable versions.
ZIP upload is simple, but the root matters.
If index.html is trapped inside an extra folder, the site can look empty or fail to route correctly. StaticX surfaces files through the dashboard so humans and agents can confirm what was imported.
Once imported, the files belong to the same versioning model as every other deploy path. Dashboard, CLI, API, MCP, manual ZIP, and link imports should all produce a clear release history.
ZIP deployment checks
No nested output folder
The ZIP root should contain index.html directly.
Include 404.html
A custom 404 page keeps missing routes professional and helps agents satisfy deploy rules.
Exclude source-only weight
Do not upload node_modules, caches, local config secrets, or source files that are not served.
Questions about Free Zip File Hosting
Short, practical answers for using this page safely.
Should I ZIP the folder or the folder contents?
Zip the contents of the output folder so index.html is at the archive root.
Does the first import create a version?
Yes in the StaticX product model. Creating or importing a site starts version 1, and explicit publish/deploy actions create later immutable versions.
Can CLI and MCP uploads follow the same rule?
Yes. Every deploy path should send the output root and produce consistent version history.