ZIP to website: one live URL, no account

From archive to live folder in three steps

1. 1

   Drop your .zip

   Drag the archive of your folder or project onto the box above, or browse to pick it. Nested subfolders are fine; the internal structure travels with the file.

2. 2

   We extract and serve it

   The archive is unpacked on our side, so nobody downstream ever has to run an unzip tool. The entry page sits at the root and every asset keeps its relative path.

3. 3

   Hand over a single URL

   Copy the address or scan the QR code and the entire bundle is reachable at once, on any device, exactly as you organised it.

How hosting a ZIP as a website works

The entry page is found for you

Put index.html at the top level of the ZIP and it opens first. A single wrapping folder is removed, so a zipped project folder works as is. Without an index.html, the HTML page nearest the top is used; a ZIP with no HTML page cannot be hosted as a site.

Relative paths resolve as you built them

Every file keeps its path, so css/style.css linked from index.html loads as it did on your computer. Use relative paths: a root-absolute path like /css/style.css does not resolve. A link to a folder, like docs/, opens that folder's index.html, and a link like menu opens menu.html.

Each file gets its own content type

The type comes from the file extension, so stylesheets, scripts, images and JSON reach the browser as it expects. File types a static site does not need, such as server scripts, are skipped when the ZIP is unpacked, and no code runs on the server.

Short caching, clean expiry

Files are cached for a few minutes at most and never past the link's expiry, so an expired link and every file under it stop resolving instead of lingering in a cache.

Its own address, with a clear lifetime

Each site gets its own subdomain on upload.tf, apart from every other upload. Without an account you can share a ZIP up to 10 MB for 30 days; sign in and it stays online until you go 3 months without signing in.

What people host from a ZIP

• Project handoff to a client

  Freelancers zip the finished microsite or banner set and send a single URL for sign-off. The client reviews the real thing in a browser instead of guessing at a pile of loose files, and nobody has to explain what an archive extractor is.

• Course material and documentation bundles

  A docs export from a generator, a slide deck exported to HTML, or a folder of exercise files becomes one address students can open from the syllabus. Every internal cross-reference keeps working because the directory layout is untouched.

• Design mockups with real assets

  Zip the prototype together with its fonts, icons, and images and reviewers see it pixel-accurate, served over HTTP the way a browser expects, instead of broken file:// paths from a locally extracted copy.