How to host an HTML file online for free, in under 60 seconds

You have an HTML file on your computer. You want it on the internet with a link you can share. That is the entire scope of this guide: host an HTML file online, for free, in the time it takes to make coffee.

No Git repository. No CI/CD pipeline. No YAML configuration. If someone (or some AI tool) handed you an index.html and you need it live, start here.

---

Why hosting a single HTML file is harder than it should be

Most hosting guides assume you have a GitHub account, a terminal open, and opinions about build tools. That is fine for developers shipping production apps. It is overkill for someone who has one HTML file and needs a URL.

The gap exists because traditional hosting was built for complex projects. You get 47 settings panels when all you need is “file in, link out.” Drag-and-drop platforms close that gap by removing every step between your file and a live URL.

If you are not sure whether your file counts as a static website, the short answer is: if it is an .html file (with optional CSS and JavaScript), it is static, and it will work with every method in this guide.

---

Step 1: Prepare your file

Before uploading, check two things.

Your file is named index.html. Hosting platforms look for this filename as the homepage. If your file is called portfolio.html or resume.html, rename it to index.html. The platform uses the filename, not the content inside the <title> tag, to decide which page loads first.

Your assets use relative paths. If your HTML references a stylesheet or image, the path should look like ./style.css or ./images/photo.jpg, not C:\Users\you\Desktop\style.css or http://localhost:3000/style.css. Absolute paths to your local machine will break once the file is on a server.

If your project has multiple files (HTML + CSS + JavaScript + images), put them all in one folder with index.html at the root and compress the folder into a ZIP:

my-site/
├── index.html
├── style.css
├── script.js
└── images/
    ├── hero.jpg
    └── logo.png

A single index.html file works too. You do not need to ZIP a lone file.

---

Step 2: Upload and go live

Method A: Drag-and-drop (fastest, no account needed to start)

This is the zero-friction path. You get from file to live URL in under 30 seconds.

1. Open Supadrop in your browser
2. Drag your index.html file (or your .zip archive) onto the upload zone
3. The platform extracts your files, provisions HTTPS, and distributes them to a CDN
4. You get a live URL at yourproject.supadrop.site and a QR code pointing to it

No Git. No terminal. No build step. The file you uploaded is the file visitors see.

Supadrop gives you a 15-day free trial with no credit card. If you need the site to stay up permanently, paid plans start at $5/month with a custom domain, unlimited bandwidth, and up to 20 GB of storage. For a full feature breakdown, see our pricing section.

Method B: Git-based platforms (free, more setup)

If you are comfortable with Git and want a permanently free option, two platforms stand out.

GitHub Pages: Push your HTML file to a GitHub repository, enable Pages in the repo settings, and GitHub serves it at username.github.io/repo-name. The free tier includes 1 GB of storage and 100 GB of monthly bandwidth. You need a GitHub account and basic Git knowledge.

Cloudflare Pages: Connect a GitHub or GitLab repository, and Cloudflare builds and deploys automatically on every push. The free tier has unlimited bandwidth and 500 builds per month. Setup takes about 10 minutes.

Both are excellent for developers. Neither supports drag-and-drop upload. If the reason you searched for “host HTML file” is that you want to avoid Git entirely, Method A is the better fit.

Method C: Cloud storage with public access

Services like Google Drive and Dropbox can technically share HTML files via a link, but they serve them as downloads, not as rendered web pages. The viewer sees raw code (or is prompted to download the file) instead of a functioning website. This is not hosting. Avoid it for anything you want people to actually use.

---

Step 3: Share and verify

Once your site is live, verify it before sharing.

Check the URL in an incognito window. Your regular browser may cache old versions. An incognito window shows exactly what visitors will see.

Test on your phone. Open the URL on a mobile device. If the page looks broken, your HTML may need a viewport meta tag:

<meta name="viewport" content="width=device-width, initial-scale=1">

Most AI-generated HTML includes this automatically. If yours does not, add it inside the <head> section.

Share the URL or the QR code. Supadrop auto-generates a QR code for every hosted site. Useful for printed materials (business cards, restaurant menus, event flyers) where people scan to visit your page. For more on QR code usage, our QR code generator guide covers static vs. dynamic codes and best practices.

---

What to do after your file is live

The URL works. People can see your page. Here is what comes next, depending on your goals.

Make it yours with a custom domain. A .supadrop.site subdomain works for testing and sharing, but a custom domain (yourbrand.com) looks more professional. You add a DNS record at your registrar and the hosting platform handles SSL automatically.

Improve your search rankings. If you want your page to appear in Google, add a proper <title> tag, a meta description, and descriptive headings. Our static site SEO playbook covers the technical fundamentals, from robots.txt to structured data.

Update the content. Made a change to your HTML? Upload the new version and it replaces the old one instantly. No versioning gymnastics, no merge conflicts.

For context on why static hosting is faster, cheaper, and more secure than traditional alternatives, and how to choose the right platform for your long-term needs, those guides cover the bigger picture.

---

Common mistakes and quick fixes

Page shows directory listing instead of your site. Your ZIP does not have index.html at the root level. It might be nested inside a subfolder (my-site/index.html instead of index.html). Re-zip so that index.html sits at the top level of the archive.

CSS and images are missing. Your HTML uses absolute file paths pointing to your local machine. Change C:\Users\... or /Users/... to relative paths like ./style.css. If you are using a subfolder structure, make sure the paths match the actual folder layout inside your ZIP.

Fonts are not loading. Self-hosted fonts referenced with a local path will not transfer. Either switch to Google Fonts (add a <link> tag in your <head>) or include the font files in your ZIP and reference them with relative paths in your CSS.

Page is blank. If you uploaded a framework project (React, Vite, Astro), you need to build it first. Run npm install && npm run build, then upload the contents of the dist/ folder, not the source code. Our guide on deploying Bolt.new sites walks through this build step in detail.

---

Frequently asked questions