Guide
Host an HTML file and share a link
An .html file sent as an attachment is a file to download, not a page to open. A host puts it at a link that opens in any browser. Here are four common ways, and what each one does at the other end.
Updated
By Angle Labs GmbH. What each service says on its own pages, read on 22 October 2026. Their names are shown as text because this site links to no third-party pages. Plans and limits change, so check each one before you rely on it.
The short answer
- A file on your computer, one link, no setup: an upload host such as Tiiny Host, or Netlify Drop.
- A site you will keep building, on your own domain: GitHub Pages or Netlify with an account.
- A page your coding agent made, which the agent should publish itself and whose feedback it should read back, without a browser upload in between: let the agent publish it over MCP, for example to Artifact Publisher.
Side by side
| Way | How you publish | Who can open it | Worth knowing |
|---|---|---|---|
| Tiiny Host | Upload an HTML file, or a zip of a static site, in the browser, or publish through its API or MCP server | Anyone with the link. Password protection is on the Solo plan and above, and Email protect (only the addresses you list, confirmed with a one-time code, no account needed) on Pro and above. | Free plan: one active project, uploads up to 3 MB, 5,000 visits a month, a Tiiny Host banner. Links stay online as long as you log in once every three months. The Tiny plan and above add Feedback mode, where reviewers comment on the page without an account, and version history. |
| Netlify Drop | Drag a folder or a zip onto the drop page | Dropped while signed out: behind a temporary password until you claim it by logging in or signing up. After that it depends on your plan and settings. | Deploys under 50 MB work best. Signed in, Netlify can also run a build step for you. |
| GitHub Pages | Push the files to a GitHub repository, with index.html as the entry file | Public by default, even from a private repository. Private Pages need GitHub Enterprise Cloud. | On GitHub Free the repository must be public. Sites up to 1 GB, a soft limit of 100 GB of traffic a month, and not for running an online business or store. A change can take up to 10 minutes to show. |
| Artifact Publisher | Your coding agent or MCP client sends one self-contained HTML document | public (anyone with the link, the default for a personal workspace), private (you only) or allowlist (named email addresses, each signed in) | One document up to 10 MiB (25 MiB on the Max plan), with no network access. The agent publishes it and reads the readers' comments back over MCP. New versions keep the same link, and you can revoke it. |
Upload hosts: Tiiny Host and Netlify Drop
Both take a file or folder from your computer and give back a link in a few seconds, which suits a page you made once and want to show. Tiiny Host's pricing page says everything you upload is public at its link, and lists password protection on the Solo plan and above. Its help center describes Email protect on Pro and above: only the email addresses you list can open the project, each confirmed with a one-time code, and visitors don't need a Tiiny Host account. On the Tiny plan and above, Tiiny Host also has Feedback mode, where reviewers comment on the page without signing up, and version history: you swap the file, the link stays the same and earlier versions are kept. Netlify's Drop quickstart says a drop made while signed out is protected with a temporary password until someone claims it. Tiiny Host also has an API and an MCP server, so a coding agent can publish there as well. Tiiny Host (as a zip), Netlify Drop and GitHub Pages also take more than one file, so a page with separate CSS, script and image files works as it is.
A repository: GitHub Pages
GitHub Pages serves the static files in a repository. It is the better fit for a site you keep changing with Git, or one that should live on your own domain. GitHub's docs say Pages sites are public by default, even when the repository is private; publishing privately needs GitHub Enterprise Cloud. So on most plans it does not suit a page meant only for a few people.
Let the agent publish it
If Claude Code, Codex, Cursor or another MCP client made the page, it can publish it without a detour through your browser. Other hosts offer agent publishing too: Tiiny Host, for example, has an MCP server and an API. What differs here is that the agent reads the comments back over MCP with get_feedback and can reply to them with reply_to_feedback. Connect it to Artifact Publisher at https://app.artifactpublisher.com/mcp with a publisher key from your account, then ask it to publish the file. The file has to be one document with all CSS, scripts, images and data inline:
Publish ./report.html with the artifact-publisher MCP server as a public artifact titled "Q3 report", and reply with the share link.The agent calls publish_artifact and replies with a link in the formhttps://app.artifactpublisher.com/artifact/<slug>. What the reader gets:
- The page in any browser. A
publiclink needs no account and is not listed or searchable. - Comments on the page. No account needed to comment on a
publiclink. The agent reads them withget_feedbackand answers withreply_to_feedback. - The same link after a change:
update_artifactadds a new version behind it. - Nothing once you call
revoke_artifact: the page stops being served. A copy someone already saved stays with them.
Free plan available.
It is not a general web host. There is no upload form: an MCP client publishes. Each version is one HTML document with everything inline, because the page runs in a sandbox with no network access, so CDN scripts, web fonts and remote images do not load. For a multi-file site or your own domain, use one of the hosts above.
Claude Code can also share its own artifacts at a public link. How that compares, and when it is enough, is inShare a Claude Code artifact for review.
Before you share any HTML file
- A link that opens for anyone also opens for whoever it is forwarded to. Leave secrets and keys out of the page.
- Open the link in a private window first, to see it the way a reader without your sign-in will.
- A React or other framework project usually needs a build step first; the built output is what you host.
Next
- Share a Claude Code artifact for review
- Publish HTML from Claude Code, step by step
- Publish HTML from Codex, step by step
- Publish HTML over MCP from Cursor, VS Code and other clients
- Share a Claude artifact without a Claude account
- All guides
- Quickstart, MCP integration, FAQ and privacy