Claude just built you a dashboard, a report, a landing page mockup. It looks right in the chat window. Then you try to send it to someone and everything falls apart.
You download the file. You email it. It arrives as a wall of code, or Gmail flags it, or your client opens it on their phone and sees nothing. You drop it in Google Drive and the link shows raw markup instead of the page.
An HTML file is a web page. Web pages need to be served, not passed around like documents. Here are the three real ways to do that, ranked by how well they hold up when the person on the other end is a client rather than a colleague.
Option 1: Publish it as a Claude artifact
If Claude made the page inside a signed-in session, you can publish the artifact directly and copy the link. This is the fastest path and it costs nothing.
Where it gets awkward: published artifacts are public to anyone with the URL, they carry Claude branding, and on Team or Enterprise plans they often cannot be published outside your organization at all. There is also nowhere for your reviewer to leave feedback other than replying to you separately.
Good for: showing a colleague something quickly.
Not good for: client work, anything confidential, anything you need notes back on.
We wrote a longer breakdown of the privacy side in are Claude artifacts private.
Option 2: Drag it onto a static host
Netlify Drop, Tiiny.host, and similar services take a file and give you a URL in under a minute. No account needed on some of them.
This works. It also gives you a public page on someone else's domain with no access control, no expiry, and no way to collect feedback. If the page contains a client's numbers or an unreleased design, you have just put it on the open web and hoped nobody guesses the URL.
Good for: throwaway public demos.
Not good for: anything with a name, a number, or a price in it.
Option 3: A link built for review
This is the gap. There is no Google Docs equivalent for a standalone HTML file, which is why people keep reaching for hosting tools that were never meant for review.
Commentable is that missing piece. You give it HTML, it gives you a private link, and whoever opens it can click any element on the live page to pin a comment there. No account for them. No download. No email thread trying to describe which button you meant.
Two ways to get your Claude output into it.
The fast path: the MCP connector
Connect commentable to Claude once from the connector page. After that you stay in the chat:
Publish this as a commentable link.
Claude sends the HTML straight over and hands you back a link. When you ask for a revision, Claude updates the same link, so nobody has to be re-sent anything. The people who already have the URL just see the new version next time they open it.
The no-setup path: paste it
Copy the HTML out of the artifact, open commentable, paste, done. Same link, same result, nothing to install.
What the encryption actually does
Your HTML is encrypted in your browser before it leaves your device. The decryption key lives in the fragment of the link, after the #, which browsers never send to a server. So the key never reaches us, and we cannot read your page even if we wanted to.
This matters more with AI-generated pages than most people expect. Claude output tends to be exactly the sensitive stuff: a client's revenue pulled into a chart, an internal roadmap, a pricing model you have not announced, a design nobody outside the company should see yet. A public static host asks you to trust an unguessable URL. Encryption means you do not have to.
You can also set a password and an expiry on top of that.
What your reviewer sees
They click the link. The page loads, fully interactive, exactly as Claude built it. There is no sign-up wall, no app to install, no "request access" screen.
They click a chart, a headline, a broken button. A comment box opens pinned to that element. They type. You see it.
The pin stays anchored to the actual element rather than to a screenshot, so when you fix the thing and republish, the conversation stays attached to the version it was made on and you can still read it back in the version history.
Try it before you sign up for anything
Every page on this site has a live example on it, including this one. Open it, click something, leave a comment. Nothing is asked of you.
Free links stay live for 30 days and are fully branded. Pro makes them permanent, puts them on your own domain, and removes the badge, at $7.99/mo or $72/yr. Full detail on the pricing page.