Share an HTML file as a link

Why a page that works on your computer breaks online

It's almost always one of these. The checker looks for all of them when you drop the file, and names the file and line.

• No index.html at the top. A folder's link opens its index.html, so a folder without one won't publish — rename your main page to index.html. A lone HTML file is fine — it's served at the root of the link.
• Paths to your own disk. file:///C:/Users/… or /Users/you/Desktop/… only exist on your machine. Copy the file into the folder and use a relative path like images/logo.png.
• Missing files and wrong case. Every image, script and stylesheet the page loads must be uploaded with it, spelled exactly — web servers treat Logo.png and logo.png as different files.
• http:// assets. Fonts and libraries loaded from https:// URLs keep working anywhere; plain http:// ones get blocked on an HTTPS page.
• Source code instead of a built site. Browsers can't run .tsx, .vue or .svelte files — run the build and drop the output folder (dist/, build/ or out/).
• API keys. A key in the HTML or JS is readable by anyone who opens the link. If the checker finds one, revoke it with the provider first, then remove it.

Who can open it

A new link is public: anyone you send it to can open it, and search engines are told not to index it, so it isn't listed anywhere. It isn't secret, though — a link can be forwarded. A new link gets a random address like k3x9q2m7ta.host0.app; rename it to something readable in your dashboard, keeping in mind that a readable name can be guessed. If the page holds anything sensitive — client data, salaries, an internal report — make it private with the switch on the card that appears after you publish (or on the app's page in your dashboard) and invite people by email. Everyone else is stopped at a sign-in page, and removing someone ends their access immediately.

Limits

• 1,000 files, 25 MB per file, 100 MB per publish. Anything over is stopped before it uploads.
• Free during the beta. No card. Free pages show a small “Hosted on host0” badge in the bottom-right corner.

Made it in a chat with Claude, ChatGPT or Gemini?

Chat apps hand you code, not a file. To get one you can drop here:

1. 1Save it as a real file. Use the download option if your chat app shows one; otherwise copy the whole code block into a plain-text editor and save it as index.html. On a Mac, TextEdit needs Format → Make Plain Text first, or it saves rich text that won't open as a page.
2. 2Make it one file if you can. If the code mentions images or files you don't have, ask the assistant: "Put everything into one self-contained HTML file — inline the CSS and JavaScript, load libraries from a CDN, and embed small images as data URLs."
3. 3Watch for API keys. If the app calls an AI API straight from the browser, the key ships with the page. Don't publish it that way.

Publishing from a coding agent

If you work in Claude Code, Cursor or Codex, the files are already on your disk and the agent can publish them. With the host0 skill installed, ask it:

you:    publish this folder to host0
agent:  ./scripts/publish.sh ./my-site
        → https://k3x9q2m7ta.host0.app/
you:    rename it to team-report
agent:  → https://team-report.host0.app/

The first time, the agent shows a sign-in link and a short code; you approve it in your own browser, so you don't paste anything into the chat. Saying "make it private and share it with ana@example.com" limits it to the people you name. Details in the docs.

Why a Google Drive, Dropbox or OneDrive link shows code instead of the page

Cloud drives share an HTML file as a file — to download, or as source code — not as a page. Dropbox says its shared links don't render HTML, and adding raw=1 doesn't change that (Dropbox Help). Google Drive stopped hosting web pages in 2016 (Google Workspace Updates). A shared index.html on OneDrive shows the raw code (Microsoft Q&A). A drive link is still fine if the other person just needs the file to open on their own computer.

Frequently asked questions