Upload a ZIP file and serve it as a website.
Bundle a multi-file project into one .zip, drop it in, and NudgeHost unpacks the archive and serves it as a live site at a single URL.
or click to browse
Key points
- Upload a .zip and NudgeHost extracts it, finds the index.html, and serves the unpacked files as a site.
- Asset paths resolve relative to the archive root, so CSS, fonts, images, and scripts load the way they do locally.
- Built React, Vue, and plain multi-page sites all work, as long as the entry point is an index.html.
- Free plan archives are up to 25MB. The Pro plan raises the per-file ceiling.
Drop a file here and get a shareable link in seconds.
Try it freeA single HTML file is easy to share. A project that spans an index page, a stylesheet, a folder of images, and a few scripts is the awkward case, because all those files have to travel together and keep their relative paths intact. Zipping them solves that, and NudgeHost takes the archive the rest of the way. When you upload a .zip, it extracts the contents, looks for an index.html at the root, and serves the unpacked files as a live site. A request for /styles.css or /img/logo.png resolves against the archive exactly as it did on your machine.
The choice between zipping and pasting comes down to how many files you have. For a self-contained single page, it is quicker to paste mode for HTML and skip the archive entirely. For anything with separate assets, the ZIP route is the one that keeps everything wired together. Either way the result is a static sites, served as plain files with nothing rebuilding on each visit, which is why it loads fast and never needs a server.
Front-end build tools make this routine. Run your production build, zip the output folder, and you have a deployable archive. The flow to deploy a React build as a link is this exact path, and it applies equally to Vue, Svelte, and any framework that emits static files. Client-side routing keeps working because unmatched paths fall back to the index, so a direct visit to /about does not break.
A couple of details save you a support ticket. If the archive has no index.html at its root, NudgeHost serves a file listing instead of a site, so check that your entry point is not buried one folder deep. ZIPs made on macOS carry a __MACOSX folder and stray .DS_Store files, both filtered out automatically on unpack. You can upload a ZIP for free up to 25MB per archive, and a paid plan lifts that ceiling when a production bundle with vendored libraries runs larger.
Frequently asked questions
What happens if my ZIP has no index.html?
NudgeHost serves a browsable file listing instead of a rendered site. Add an index.html at the archive root, or rename your entry page, and it serves as a site on the next upload.
Can I upload nested folders inside the ZIP?
Yes. The folder structure is preserved and files load at their relative paths. Just make sure the index.html that should load first sits at the top level of the archive.
What is the largest ZIP I can upload?
25MB on the free plan. Most static sites and prototype builds fit comfortably; the Pro plan raises the limit for heavier production bundles.
Do Mac-specific files end up in my hosted site?
No. __MACOSX directories and .DS_Store files are stripped during unpack, so they never appear in your URL structure.
Get file-sharing tips that actually help.
One email a month. No spam, no fluff.
Related tools
Other things you can do on NudgeHost.
Ready to share your file?
Free forever, no credit card needed. The whole thing takes a few seconds.
Get started free