Claude artifact sharing
Turn Claude’s HTML into a link people can actually review.
Claude often produces richer work in HTML than in a chat response: visual reports, prototypes, calculators, and complete explainers. Downloading the file solves storage, but not review. HTML Docs gives that output a stable URL, then keeps the human feedback and agent revisions connected to it.
“Can you send me the link?” should have a simple answer.
A local Claude artifact is invisible to everyone else. Attaching the file creates security hesitation and makes each revision a new attachment. A generic host creates a URL but leaves feedback in Slack or email. HTML Docs is designed for the full loop: publish, comment, revise, and keep the same link.
How it works
From local output to a reviewed artifact.
Ask for complete HTML
Have Claude produce a self-contained page with its styles and scripts included.
Publish from Claude Code
Install the HTML Docs skill or run the CLI publish command on the generated file.
Invite reviewers
Share the returned URL and collect comments directly around the live content.
Send feedback back to Claude
Use the API or skill to read comments and update the affected regions.
What changes when review is built into the page
One Claude workflow
The same agent that creates the artifact can publish and revise it.
One current URL
Reviewers do not have to guess which downloaded version is current.
Structured feedback
Comments can be read by an agent instead of copied manually from chat.
HTML Docs vs. Sending the .html file
Choose for the job you actually need to finish. This comparison focuses on workflow, not a blanket claim that one tool replaces another.
| Criterion | HTML Docs | Sending the .html file |
|---|---|---|
| Opening | Normal HTTPS link | Download and open a local attachment |
| Versions | History behind the same page | Multiple files with similar names |
| Feedback | Attached to the rendered work | Separate messages and screenshots |
Frequently asked questions
Can Claude Code publish directly to HTML Docs?
Yes. Install the HTML Docs skill or use the CLI from the project directory.
Can Claude update the page after someone comments?
Yes. The API exposes the document, editable regions, comments, and versions so an agent can revise the same artifact.
Can I share a private Claude artifact?
Use a private or unlisted share workflow when the artifact should not be discoverable. Published pages are noindex by default unless you explicitly list them publicly.
Will reviewers see Claude or the HTML source?
Reviewers see the rendered page. The artifact can be discussed and edited without asking them to inspect source code.
Publish the next artifact from where it was created.
npx @html-docs/cli publish page.html