How to convert HTML to a link

An HTML file on your computer is only visible to you. A link (a URL) is an address on the internet that any browser can fetch. Converting one into the other always means the same thing under the hood: copying the HTML to a web server and giving it an address. The methods differ in how much of that work you do yourself.

Method 1: an online HTML to link converter (fastest)

Online converters host the HTML for you. There is no repository, build step or DNS to configure — you paste, publish and copy the link.

1. Open the converter.
2. Paste your HTML into the editor, or switch to Upload and drop an .html file, a .zip, or a whole folder.
3. Optionally type a custom address (for example spring-quiz becomes spring-quiz.htmltolink.dev), choose how long it stays online, and add a password.
4. Press Get my link. Copy the URL, scan the QR code, or share it straight from your phone.

The link is saved to your account, so you can update the page at the same URL or delete it later from My links on any device. Free links last 24 hours; paid plans keep them online for good.

Method 2: GitHub Pages (free, permanent, needs Git)

GitHub Pages serves any repository's files as a website. It is free for public repositories and suits pages you will keep for years.

1. Create a GitHub account and a new repository.
2. Upload index.html (and any CSS, JS and images) with Add file → Upload files.
3. Open Settings → Pages, choose the branch, and save.
4. After a minute or two, the site is live at username.github.io/repository.

Trade-offs: you need an account and a little Git vocabulary, the page is public and can be indexed by search engines, and a project site lives in a sub-folder — so absolute paths like /style.css break. The GitHub Pages guide has every click and fix.

Method 3: Netlify Drop

Netlify's drag-and-drop deploy accepts a folder in the browser and publishes it to a *.netlify.app address. It is quick and handles whole sites well. Expect to sign up to keep the site and to manage it afterwards; a drop without an account is temporary.

Method 4: Vercel, Cloudflare Pages and similar

Developer platforms deploy from Git or a command-line tool and add build pipelines, serverless functions and custom domains. They are excellent for applications and overkill for "please look at this page". Expect an account, a CLI or a connected repository, and a few minutes of setup the first time.

Method 5 (does not work any more): Google Drive or Dropbox

Both used to render HTML files as web pages. Google Drive ended web hosting in 2016 and Dropbox stopped rendering HTML in shared links in 2017. Today a shared .html file opens as source code or downloads, so the recipient still has to open it locally — and many will not. If you have been sent here because "the link shows code", that is why.

Which method should you use?

Before you publish: a 30-second checklist

• Viewport tag — without <meta name="viewport" content="width=device-width, initial-scale=1"> the page looks tiny on phones.
• Relative paths — images/logo.png, never C:\Users\….
• HTTPS resources — anything loaded over http:// is blocked on an HTTPS page.
• All files included — upload the folder or ZIP, not only the .html file.

If the page still misbehaves once it is online, the troubleshooting guide lists every common cause and fix.