HTML HOSTING
HTML hosting: host an HTML file without a server
HTML hosting is one drag: drop a finished .html file and it is live at its own HTTPS address in seconds. If the page pulls in a stylesheet, a script or images, zip the folder instead and every relative path keeps working.
Free plan, free SSL, no credit card.
- 1
- file is enough, with nothing to zip first
- 25 MB
- per upload on the free plan
- 1
- free site with HTTPS, no card
- 5,000
- visits a month included
How it works
Three steps, start to live link
-
Drop the .html file
One finished page goes up on its own. There is no archive to build, no folder to prepare and no template to fill in first.
-
Open it in a browser
The page gets its own HTTPS address, so a reviewer opens a link instead of downloading an attachment and trusting their machine to render it.
-
Keep it, or move it to your domain
The Droply address is yours on the free plan and does not change when you republish. From Pro the same page can be served from a domain you own.
The plain answer
What is HTML hosting?
HTML hosting is putting an .html file somewhere a browser can reach it over the public internet, so that opening a URL shows the page instead of downloading the file. That is the whole job: a public address, a server that returns the file with the right content type, and a certificate so the address works over HTTPS.
It sounds trivial, and the file itself is trivial, which is exactly why it is annoying. A local .html file opens fine by double-clicking it, but you cannot send that to anyone: an email attachment gets stripped or flagged, a chat app renders it as a download, and a colleague on a different operating system may open it in something that is not a browser at all. Hosting the file removes every one of those failure modes at once.
The part that trips people up is assets. A single page with everything inline needs nothing else. A page with <link href="style.css"> or <img src="images/hero.png"> needs those files present at those exact relative paths, which means you upload the folder rather than the page. If you are not sure whether your page is self-contained, the HTML tester renders pasted markup so you can see what is missing.
Who it is for
The people who reach for this
-
Designers
A hand-coded page, an email template preview or an exported comp, live at an address a client can open on a phone.
-
Developers
A single-file demo, a reproduction case for a bug report, or a page you wrote to test one idea.
-
Educators
A lesson page or a worked example that students open by link instead of downloading and losing.
-
Anyone handed an HTML file
Somebody sent you a page and said "put this online". This is that, in about a minute.
In detail
What you actually get
One file really is enough
Several hosts in this category accept a folder or an archive and refuse a loose .html file, which means your first step is packaging something that did not need packaging. Here the file is the upload.
- Drop the .html or .htm and press publish. Nothing else is required.
- The page is served at the root of the site, so the address is the page.
- A page that is a single file with inline CSS and JavaScript needs no further thought.
When the page has assets, upload the folder
A stylesheet, a script bundle, web fonts and images all resolve against the page URL. Preserve the folder layout and every reference resolves exactly as it does on your machine.
- Upload the folder directly, or zip it and upload the archive.
- The entry page must be named index.html and sit at the top of what you upload.
- Relative paths are preserved on extraction; absolute paths that start with a drive letter or file:// will not resolve.
- If the ZIP wraps everything in one extra folder, that folder is unwrapped rather than becoming part of the URL. Hosting a static site from a ZIP covers the shapes that fail.
It tells you what you exposed
Uploading a folder is the moment a stray file becomes public. Every publish is read after it goes live and reported back in plain language.
- Warns about an .env file, a .git directory, a private key or an API key sitting in a script.
- Runs on every plan, free included, and never blocks the publish.
- The detail is on the security check page.
Edit and republish without a new link
HTML files change constantly while a page is being reviewed. Re-uploading replaces what the address serves and leaves the address alone.
- Every version is stored separately, and publishing points the address at the new one.
- From Pro, an earlier version is one click away if the new one is wrong.
- Up to 15 publishes a day on the free plan, which is more than a review round needs.
No card required
What the free plan includes
Hosting one HTML page costs nothing. This is the whole free plan, not a trial of it.
- 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 for a single HTML file
Both products accept HTML and both are aimed at people without a deploy pipeline. These are the differences that show up once the file is up.
| Droply | Tiiny Host | |
|---|---|---|
| Single .html accepted | Yes, on its own. | Yes. |
| 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). |
| Security check on deploy | Every publish, on every plan, including free. | Not offered. |
| React file without a build | A single .jsx or .tsx runs at the URL. | Not offered. |
| Password protection | From Starter, checked at the edge before any file is served. | From Solo, $18 a month or $13 billed annually. |
| 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. |
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
An HTML file is the simplest thing on the web and it still cannot do some of what people expect from it. If your page needs any of the following, hosting the file will not give it to you.
- The page has a form and you expect the submissions to land somewhere. A static page can post to a service you already run, but nothing here stores them for you.
- The HTML is generated per visitor, by a template engine or a CMS. Upload the rendered output, not the template.
- 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.
Frequently asked questions
Can I host a single HTML file?
What if my HTML file uses CSS, images or JavaScript?
Is hosting an HTML file free?
Do I need a server or any configuration?
What should the main page be called?
Can I edit the HTML after publishing?
Can my HTML page call an API?
Will search engines index my hosted HTML page?
Can I upload an HTML file exported from Word, Figma or a page builder?
Related pages
Keep exploring
- HTML tester Paste markup and see it render before you publish it.
- HTML validator Check the structure of a page in the browser, with nothing uploaded.
- Pricing and plan limits Upload size, storage and which tier unlocks what.
- The Fastest Way to Ship an Event Page A worked example: one page, live, in the time it takes to write it.