Features

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 its own link on nudgehost.site.

Drop your file here
ZIPMulti-file siteReact buildVite buildUp to 25MB free

Key points

  • Upload a .zip and NudgeHost extracts it and serves it as a site at its own subdomain, like your-name.nudgehost.site.
  • The site is served from the root of that link, so CSS, fonts, images, and scripts load the way they do locally.
  • Built React, Vue, and plain multi-page sites all work, and client-side routes survive a direct visit.
  • Up to 200 files per served site; a ZIP with no index.html inside shares as a one-click download instead.

A 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, finds your index.html (a single wrapper folder like dist is stripped automatically), and serves the unpacked files as a live site at a subdomain of its own. A request for /styles.css or /img/logo.png resolves against the archive root 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 site, served as plain files with nothing rebuilding on each visit, which is why it loads fast and never needs a server. The glossary entry on static sites covers the model.

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. AI builders emit the same shape of bundle; the guide to sharing a Lovable site follows one through this exact pipeline. Client-side routing keeps working because unmatched paths fall back to the index, so a direct visit to /about does not break, while requests for files that genuinely do not exist still 404.

A couple of details save you a support ticket. An archive with an index.html somewhere inside it becomes a site; without one, the ZIP shares as a plain one-click download, so a bundle of documents or photos still travels as one link. A served site can hold up to 200 files. 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 unpacked, and the Pro plan lifts that ceiling when a production bundle with vendored libraries runs larger.

Drop a file here and get a shareable link in seconds.

Try it free

Frequently asked questions

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