STATIC WEBSITE HOSTING
Static website hosting without the setup
Static website hosting for a site you have already built: upload it as a ZIP or a folder and get a secure public URL in seconds. There is no Git remote to add, no server to configure and no build to wait for, because the files you upload are the files we serve.
Free plan, free SSL, no credit card.
- 96
- file types accepted, in 7 groups
- 23
- framework build guides, with the exact output folder
- 25 MB
- storage on the free plan, no card
- 5,000
- visits a month before you pay anything
How it works
Three steps, start to live link
-
Upload your finished files
Drop a ZIP of your built site, a whole folder, or a single HTML file. Your CSS, JavaScript, images and fonts stay together and keep their relative paths.
-
Pick a name and publish
Choose the subdomain and press publish. The site is live on its own HTTPS address in seconds, with the certificate issued and renewed for you.
-
Update the same address
Upload a new build when the work changes. The URL does not move, so links you already sent, bookmarks and printed QR codes all keep working.
The plain answer
What is static website hosting?
Static website hosting means a server sends your files to a browser exactly as you wrote them, with no code running in between. The HTML, CSS, JavaScript, images and fonts are the whole product; there is no application on the server assembling a page per visitor.
That is why it is fast and why it is cheap: every visitor gets the same bytes, so they can be cached aggressively and served from disk. It is also why the setup is short. A dynamic host has to know your language, your dependencies, your environment variables and your database. A static host only has to know which folder to serve, so the entire configuration is the folder you hand it.
The catch is what the word "static" excludes. Anything your site does at request time on the server, a login, a form that writes to a database, a page rendered per user, is not part of the deal. Modern front-end frameworks are still welcome here, because they build down to static files: you run the build on your own machine and upload what it produces. The framework deploy guides list the exact command and output folder for each one.
Who it is for
The people who reach for this
-
Designers
A finished layout or a coded comp goes up as a real page, at a real address, instead of a screenshot in a thread.
-
Developers
Somewhere to put the built output of a side project without adding a pipeline you will have to maintain.
-
Marketing teams
A campaign or event page that has to be live today, on its own address, without waiting for a release train.
-
People with no tech team
Somebody sent you a folder of website files. This is the shortest honest path from that folder to a link.
In detail
What you actually get
Upload the shape you already have
Most static hosts accept exactly one shape and reject everything else, which turns a two-minute job into a repackaging exercise. Droply takes the artefact you are actually holding.
- A single .html file, dropped on its own, with nothing to zip first.
- A ZIP of a built site, extracted with its folder structure preserved.
- A whole folder, dragged straight from the desktop.
- A single .jsx or .tsx file, which runs in the visitor browser with no build step.
- 96 file extensions in total, across 7 groups, including PDFs, images, media and documents.
One address, every version
Each upload becomes a new immutable version, and publishing swaps which version the address points at. Nothing is edited in place, so a publish either fully happens or does not happen at all.
- The URL never changes, so anything you already shared keeps resolving.
- A visitor mid-page-load never sees half the old build and half the new one.
- Rollback to an earlier version is one click, from Pro upward.
- The free plan keeps the current version only, which is enough to publish but not to roll back.
A security check on every publish, on every plan
The most common way a static site leaks something is a whole project folder getting zipped instead of the build output. We read what you actually published and say what a stranger can now read.
- A committed .env file, a .git directory, a private key, an API key left in a JavaScript bundle.
- It runs after the site goes live and reports in plain language, not as a severity score.
- Included on the free plan. See how the security check works.
Your own domain, with the certificate handled
A subdomain is fine for a preview and wrong for a launch. From Pro you point a domain you own at the site and it is served from your address.
- HTTPS certificates are issued and renewed automatically, on the Droply address and on yours.
- Step-by-step DNS guides for the common registrars, with the exact records.
- Free sites are served noindex, so search engines will not list them. Indexing starts on Starter.
No card required
What the free plan includes
Everything below is on the free plan, with no card and no trial period to run out.
- 1 live site on a real free plan, not a trial of a paid one, and no card to start.
- Up to 25 MB per upload and 25 MB of storage across the account.
- 5,000 visits and 5 GB of traffic a month.
- HTTPS with a real certificate, issued and renewed for you.
- Up to 15 publishes a day, so you can iterate without asking permission.
- The deploy-time security check, which reads what you published and warns about a stray .env file, a .git folder, a private key or an API key left in your JavaScript.
- A small Droply badge in the corner of the page. Removing it starts on Starter.
- Free sites are served noindex, so search engines do not list them. Search visibility starts on Starter.
Droply vs Tiiny Host
How this compares with the closest competitor
Tiiny Host is the incumbent in this category and does the same core job well. These are the rows that actually differ for someone with a finished static site.
| Droply | Tiiny Host | |
|---|---|---|
| Free plan | 1 site, 25 MB storage, 5,000 visits and 5 GB a month, no card. | 1 site, 5,000 visits and 5 GB bandwidth a month, 3 MB per project (0.5 MB for a PDF). |
| Single HTML file, no ZIP | Yes, drop the .html on its own. | Yes, HTML is accepted. |
| Single .jsx or .tsx, no build | Yes. It is transformed in the visitor browser at the published URL. | Not offered. |
| Security check on deploy | Every publish, on every plan, including free. | Not offered. |
| Custom domain | From Pro, $15 a month. | From Solo, $18 a month or $13 billed annually, up to 5 domains per account. |
| Entry paid price | $5 a month for Starter. | $9 a month for Tiny, or $5 billed annually. |
| Free trial behaviour | No trial to cancel. The free plan is the free plan. | Every paid plan carries a 7-day money-back guarantee. |
Tiiny Host figures come from its own help center, checked 8 September 2026: the pricing-plans article (updated 1 September 2026), the visitor, upload and bandwidth limits article (updated 2 September 2026), the free-plan link duration article (updated 21 August 2026), the password-protection article (updated 3 September 2026) and the custom-domains guide (updated 7 September 2026). Product plans can change.
When Droply is the wrong choice
Static hosting is a narrow tool and it is the wrong one more often than most hosts admit. If any of the following is true of your project, something else will serve you better and you will find that out faster here than after an afternoon of uploads.
- Your site needs a contact form that stores submissions itself, a members area, or a shopping cart with server-side checkout.
- You are shipping a Next.js or Nuxt app that uses server rendering or API routes. A fully static export works; the server half does not.
- You need a database, a login system, or code that runs on the server. Droply serves files; it does not execute your application.
- You want a build to run on every push to a repository. Droply has no Git integration and no CI: you build locally and upload the result.
- You are running WordPress or another PHP application. A static export of it can be hosted here, but the application itself cannot.