How it works

From folder to live URL in three steps

Drag a folder or zip in

Drop it onto the upload area in the browser, or click through to pick it from your computer.

We check it, then it queues

We look for an index.html and confirm the upload is within the file size and count guardrails, then it joins the deploy queue.

It's live — update anytime

The upload publishes in order. To update later, zip the folder again and drop it in — the new version replaces the old one.

What to include

See it before you drop it

Zip the folder that already holds your finished site, not your whole project. If your tool builds into a subfolder such as dist, public, or build, zip the contents of that folder, with index.html at the top level rather than one folder down.

lemonadehost.com/upload

Drop your folder hereor click to browse your computer

lemonadehost.com/upload

42 files, 1.8 MBchecked, and queued to publish

What people upload

If it's a folder of finished files, it belongs here

Builder exportsWhatever "download code" produces

Static site generatorsHugo, Eleventy, or similar, already built

Hand-written HTMLHTML, CSS and JS you wrote yourself

Generated docsA documentation build, zipped up

Portfolios & résumésA single finished page

Design tool exportsPrototypes, exported as static files

Room to work with

The limits, framed the honest way

What's actually in bounds: 25 MB per file — comfortable for a photo, a video clip, or a font. About 20,000 files a site, enough for a large gallery or a generated documentation set without counting them twice. Roughly 100 deploys a day, plenty to fix a typo five times before lunch — it keeps the queue moving for everyone, not you specifically.

Prefer a different route?

The other three ways in

GIT

Drag a folder in and it's live

See what's included on the static hosting page, or check pricing.

Join the list

Drag the folder in. That's the whole process.