How to share an HTML file Claude Code generated

To share an HTML file that Claude Code generated, upload it at shareable.page or run shareable publish ./index.html from your terminal. Either way you get a stable, unlisted link like shareable.page/a/abc123 that renders the page in a sandboxed viewer — no zip to send, no broken asset paths, and nothing for the recipient to install.

Claude Code increasingly answers with a polished index.html — a dashboard, a walkthrough, an analysis — instead of a Markdown file. That artifact is great to look at and awkward to hand off. Here are the two reliable ways to share it.

Option 1 — Publish from the terminal (or let the agent do it)

This is the fastest path when the file already lives in your project. Install the CLI once with a single command, which also wires a publish skill into Claude Code so the agent can share the artifact it just built:

curl -fsSL https://www.shareable.page/install/claude | bash

Then publish the file and copy the link it prints:

shareable publish ./index.html --title "Q2 Forecast"

If the page references local assets — CSS, JavaScript, images, fonts, or data files — point the command at the folder so they travel with it:

shareable publish ./index.html --assets ./assets

See the CLI docs for the full set of commands and flags.

Option 2 — Upload in the browser

No terminal required. Sign in at shareable.page, open New artifact, and drop in the HTML file, its loose assets, or a single zip. Shareable picks the entry HTML, rewrites local asset references to private render URLs, and shows you a desktop and mobile preview with any warnings before you publish.

What the recipient sees

They open the link and see the rendered artifact in a clean viewer — not a folder of files, not source code they might edit by accident. The page is private by default: the link is an unlisted secret URL, it is marked noindex, and you can add a password for anything sensitive.

Updating without resending

When the agent revises the artifact, publish again. Each artifact is versioned and the share link always points to the latest version, so the URL you already sent simply shows the new content — no second attachment, no "use this one instead" follow-up.