This comes up constantly. You made a page, or Claude or ChatGPT made one for you, and now it lives in a file called index.html on your desktop. Someone else needs to see it. Not the code, the actual page, in their browser, on their machine.
Sending the file itself almost never works. Gmail flags HTML attachments as a security risk. Slack uploads it as a download, and when your reviewer clicks it they get a wall of markup or a half-broken page opened from their downloads folder. What you actually want is a link. Here are the five real options, ranked by how fast you get one.
1. Paste it into a sharing tool (fastest)
Tools built for exactly this job take your HTML and hand back a URL in seconds. No account gymnastics, no build step, no FTP. We build one of them, commentable, so an example with real numbers: you paste the HTML or drop the file, and about five seconds later you have a private link you can send to anyone.
A few things worth knowing about this category before you pick a tool:
- Privacy varies a lot. Some tools publish your page on an open URL that anyone can find. commentable encrypts the page in your browser before upload, and the decryption key travels in the link itself, after the
#, which never reaches the server. We could not read your page if we wanted to. - Check what happens after 7 days. Several popular tools delete free pages after a week. On commentable, free links live 30 days, and you get an email before one expires.
- Some add feedback. If the reason you are sharing is to get a review, a tool where people can pin comments on the page saves you a whole round of screenshot-annotating. More on that in our guide to client feedback.
2. Netlify Drop (fast, public, permanent)
Netlify has a page where you drag a folder in and get a live site at a random subdomain. No account needed for the first hour, and free with an account after that. It is a genuinely good tool, and the right choice when the page is meant to be public and permanent.
The gaps: the URL is public with no password option on the free plan, there is no way for viewers to leave feedback, and dragging a folder is required (it does not accept a paste). Fine for a portfolio piece, less fine for a client proposal.
3. GitHub Pages (free, permanent, some setup)
If you already live in GitHub, Pages is free hosting straight from a repository. Push your file, flip a setting, and the page appears at username.github.io/repo. Version history comes along for the ride, which is genuinely useful for pages you will keep updating.
The setup cost is real, though. You need a GitHub account, a repository, and a push. The page is public (private repos need a paid plan for Pages), the URL is long, and there is no password protection at all. For a one-off share it is a lot of ceremony. Our full hosting comparison covers this trade-off in more depth.
4. Vercel or Cloudflare Pages (for developers)
Both give you excellent free hosting with a CLI deploy or a git integration. If you are a developer and the HTML file is part of a project, this is probably where it should live anyway. If you are not, the words "CLI deploy" have already answered the question for you.
5. A local tunnel like ngrok (temporary, technical)
Run a local server, point ngrok at it, and your machine is briefly on the internet. The link dies when you close your laptop. Useful for showing a teammate something live during a call, wrong for anything that needs to survive the afternoon.
Which one should you actually use?
| Situation | Best option |
|---|---|
| Client work, proposals, anything private | A paste-and-share tool with encryption and a password option |
| Public page you will keep forever | Netlify Drop or GitHub Pages |
| Part of a real dev project | Vercel or Cloudflare Pages |
| Quick look during a call | Screen share, honestly. Or ngrok. |
| You need feedback, not just eyeballs | A tool with comments built in |
The pattern behind the ranking: hosting platforms optimize for permanence and control, sharing tools optimize for speed and privacy. Pick based on which of those your file needs. And if it needs feedback too, get a link where people can comment on the page itself, because "thoughts?" emails produce feedback about the page from memory, which is worse feedback.