How to Host an HTML File (and Get a Link in Minutes)
To host an HTML file you need a server that sends it to browsers at a public address. For one page, the quickest route is a paste-and-share tool such as HTMLpad: you paste the HTML and get a link. For a site you will keep growing, a static host like GitHub Pages or Cloudflare Pages is the better home.
That is the short answer. The rest of this guide is the longer one, because "host an HTML file" covers very different needs. Some people want a link for the next ten minutes so a colleague can look at a mockup. Others want a page that will still be online in three years with their own domain on it. The right tool depends on which of those you are, and picking the wrong one is how people end up with a dead link or a monthly bill they did not need.
I have built websites for clients for a long time, and a surprising number of them started life as a single HTML file someone emailed me. These days that file often comes out of an AI assistant. The question is always the same: how do I put this online?
What hosting an HTML file actually means
Hosting means three things happen. The file lives on a computer that is always on, that computer answers requests from browsers, and there is an address people can type or click to reach it.
When you double-click an HTML file on your laptop, your browser opens it from your own disk. The address bar shows something like file:///Users/you/Downloads/page.html. Nobody else can open that address, because it points at your machine. To share the page, the file has to move to a server with a public address, usually one that starts with https://.
Everything below is a different way of getting your file onto such a server. They differ in four things that matter:
- Effort. Some take ten seconds, some need an account, a repository and a few settings.
- How long the page lasts. Some links expire after an hour or a few weeks unless you act.
- What you can upload. One file, a folder, or a whole project with a build step.
- Address. A random address on someone else's domain, a name you choose, or your own domain.
One file or a folder?
Before choosing a host, look at what you have. A single HTML file that contains its own CSS and scripts is the simplest case. Many AI-generated pages are exactly that: one file, styles inside a <style> tag, everything self-contained.
If your page loads separate files, such as style.css, app.js or images in an img folder, you need a host that accepts the whole folder, or you need to fold those files into the HTML first. A page that looks perfect on your laptop and arrives online without styles is almost always a page whose CSS file was left behind.
Option 1: paste it into a pad
A pad is the shortest path from HTML to link. You open the site, paste or drop your file, and save. There is no account, no folder structure and nothing to configure.
On HTMLpad, the editor shows your code on one side and the live page on the other, so you can fix a typo before you share. When you save, you get an address such as HTMLpad.org/your-name/, and you can pick that name yourself. Free pads stay online for 90 days. If you leave your email, we send you the link to edit the pad later and a reminder before it expires.
This route suits a single self-contained page: a mockup, a report, a quick demo, a one-off landing page, or anything an AI assistant handed you as one file. It does not suit a multi-page site or a page with heavy images, because a pad is one HTML file of up to 512 KB.
I wrote a separate guide on how to share an HTML file as a link that walks through this step by step, including what to do with images.
Option 2: a drag-and-drop host
Drag-and-drop hosts let you drop a file or a zipped folder onto a page and publish it. Tiiny Host, Netlify Drop and Static.app all work this way, with different rules.
Netlify Drop publishes without an account, but an unclaimed site is deleted within an hour, so for anything that has to stay up you sign up and claim it. Vercel's comparison of the two drop tools describes it as a try-before-you-sign-up flow rather than permanent hosting. Tiiny Host gives a free account one active project with a 3 MB upload limit and 5,000 visits a month. Static.app starts with a seven-day trial and then needs a paid plan to keep publishing.
These tools are a good middle ground when your page has a few files, or when you want extras such as a custom domain or password protection and are happy to pay a few dollars a month for them. I compare them in detail in free HTML hosting: the options compared, and one by one in HTMLpad vs Tiiny Host, HTMLpad vs Netlify Drop and HTMLpad vs Static.app.
Option 3: GitHub Pages
GitHub Pages serves a website straight from a GitHub repository. You create a repository, upload your index.html and any other files, and switch on Pages in the settings. A few minutes later the site is live at yourname.github.io.
It is free and it lasts as long as the repository exists. It also handles custom domains and HTTPS. The catch is the learning curve: you need a GitHub account and a basic idea of repositories and commits, which is a lot to ask from someone who just wants to share one page.
There are also rules worth knowing. GitHub's documentation sets a 1 GB limit on published sites and a soft bandwidth limit of 100 GB a month, and says Pages is not meant to run an online business or handle sensitive transactions such as passwords or card numbers.
Pick GitHub Pages when the page is the start of something you will keep editing, when you already use GitHub, or when you want a free permanent home and do not mind the setup.
Option 4: Cloudflare Pages and similar static hosts
Cloudflare Pages, Netlify and Vercel are full static hosting platforms. You connect a repository or upload a folder, and they deploy it across a global network. Their free tiers are generous. Cloudflare's limits page lists 500 builds a month and up to 20,000 files per site on the free plan.
For a single file this is more machinery than you need. For a real static site with several pages, a build process, and a team pushing changes, it is the right tool. If you are not sure whether your project is "a page" or "a site", my guide to what a static website is draws that line.
Option 5: traditional web hosting
The old way still works. Rent shared hosting, connect with FTP or the host's file manager, and upload your file into the public folder. Your page is then served from your own domain.
This makes sense if you already pay for hosting, for example because you run a WordPress site there, and you want the HTML page to live on the same domain. It makes little sense to sign up for a hosting plan just to publish one page.
Which one should you pick?
The honest answer depends on how long the page needs to live and how much you will change it.
| Your situation | Best fit |
|---|---|
| One self-contained page, needed today, no account | A pad such as HTMLpad |
| A page with a few files, maybe a custom domain | Tiiny Host, Static.app or Netlify Drop (claimed) |
| A page you will keep editing for months | GitHub Pages or Cloudflare Pages |
| A multi-page site with a build step | Cloudflare Pages, Netlify or Vercel |
| A page on the domain where you already host a site | Your existing web hosting |
Two questions settle most cases. Will anyone need this link in a year? If not, choose the fastest option. Will the page grow into several pages, with a blog or a contact form? If so, you are not hosting a file any more, you are building a site, and I explain when a single HTML page isn't enough.
Common problems after you upload
Most failed uploads come down to a handful of causes.
The page has no styles. The HTML links to a CSS file that did not make it to the server, or the path is wrong. Either upload the CSS too, or paste its contents into a <style> tag in the HTML.
Images are missing. Same cause. Image paths like C:\Users\... or /Users/... point at your own disk. Use images hosted at a public address, or relative paths to images you uploaded alongside the HTML.
The page shows code instead of the page. The host is sending the file as plain text. That happens when the file lacks an .html extension or when you uploaded it to a place that only stores files, such as a cloud drive. Google Drive and Dropbox are for sharing files, not for serving web pages.
Forms do not send anything. A static HTML page cannot process a form on its own; something on a server has to receive the data. You need a form service or a backend.
The link stopped working. Check whether your host expires free pages. Netlify Drop deletes unclaimed sites within an hour, Static.app's trial lasts seven days, and HTMLpad's free pads last 90 days unless you save them again.
Hosting HTML that an AI made for you
A lot of the HTML people want to host today comes from ChatGPT, Claude or Gemini. These pages are usually ideal for quick hosting: one file, styles inside, sometimes a bit of JavaScript.
Two things to check before you publish. First, read what the page says. AI assistants sometimes fill pages with placeholder names, made-up prices or sample email addresses. Second, look for external resources. Some generated pages load fonts or libraries from public CDNs, which is fine, but they occasionally reference images that do not exist.
If the page came from Claude, it may already be an artifact you can publish from Claude itself. I explain the difference in how to share a Claude artifact as a web page.
A note on security
Any host that lets anyone publish HTML has to deal with abuse, mostly fake login pages built to steal passwords. That is why many of these services restrict what you can publish. HTMLpad does not accept password or card fields, and every pad runs isolated from the rest of the site. GitHub's terms say the same about sensitive transactions.
If your page needs to collect passwords or payments, it should not be a static file on a free host. It needs a proper application with its own security.
Frequently asked questions
Can I host an HTML file for free?
Yes. Pads like HTMLpad, GitHub Pages and Cloudflare Pages are free. The differences are in how long the page lasts, how much setup you need and whether you can use your own domain without paying.
Can I host an HTML file on Google Drive?
Not as a web page any more. Google Drive stores and shares files, so people can download your HTML or see its code, but it does not serve it as a working page in the browser. Use a web host instead.
Do I need my own domain?
No. Every option here gives you a working address on the host's domain. A custom domain matters for something permanent and public facing, such as a business page. For a demo, a mockup or a page you share with a few people, the host's address is enough.
How long will my HTML page stay online?
It depends on the host. Netlify Drop removes unclaimed sites within an hour. Static.app's free trial lasts seven days. HTMLpad keeps free pads for 90 days. GitHub Pages and Cloudflare Pages keep your site as long as your account and project exist.
What is the fastest way to share an HTML page?
Paste it into a pad. On HTMLpad you paste the code, see it working, save, and copy the link, with no account and no upload of folders. It takes under a minute for a self-contained page.