Guides
How to Share Claude Artifacts Professionally
Claude’s built-in publish is great for quick demos. For client work you need versioning, a stable link, and optional protection—here’s a practical workflow.
Published
Why “just publish from Claude” breaks down for real work
Claude’s artifact experience is one of the fastest ways to go from a prompt to a working HTML page. For internal reviews or a quick “look at this” link, that’s often enough.
The gap shows up when the page becomes a deliverable: a sales narrative, a client readout, a proposal, or anything that will be revisited. You need:
- A single URL your buyer or stakeholder can save—without you re-sending the link every time you tweak copy.
- A clear version trail so you (and your team) know what went live and when.
- A surface that looks intentional on mobile and desktop, not like a throwaway file share.
This guide walks through how professional teams close that gap without adding a “website project” to your backlog.
The three ways to get HTML into unfurl
You can think of unfurl as the publishing layer on top of whatever stack you use to generate HTML.
| Method | Best for | How it feels |
|---|---|---|
| Drag and drop | One-off HTML exports from Claude, ChatGPT, or a local file | Fastest path to a live link—no script required |
| HTTP API | Pipelines, CI, or internal tools that already ship HTML | Same permanent document; automate publishing from your build |
| MCP | AI agents that should publish as part of a longer workflow | The agent reuses the same document URL as your content evolves |
In all three cases, the point is the same: your audience opens one link, and you control what “current” means.
A practical client workflow (Claude → review → live)
- Draft in Claude as you already do. Export or copy the final HTML when you are ready to treat it as a published state—not a draft you might replace in ten minutes.
- Publish to unfurl with the method that matches your team. If you are non-technical, start with drag-and-drop; if you are wiring agents, add MCP when you are ready.
- Send the share link instead of an attachment. The page opens in the browser, with no “download this file” friction.
- Iterate with confidence: when the document changes, publish again. Your live link can track the latest version, while the dashboard keeps timestamped history for internal audit and rollbacks.
If you have ever resent proposal-v7-FINAL.html, this is the habit you are building instead: the filename stops mattering because the URL is the contract with your client.
When to invest in a dedicated host (like unfurl) vs. a static file host
“Free static hosting” tools are useful for one-page experiments. The reason teams pick unfurl is what happens after the first upload:
- Versioning is part of the product, not a folder on your desktop.
- A stable customer link you can put in a deck, a signature, or a CRM.
- Optional collaboration and API access as your process matures (see the product docs for what is available on your plan).
If your artifact is a living document in an AI loop, you want a host that matches that reality—not a one-time file drop.
Next step
Publish your first document on unfurl, send the link to a teammate, and update the HTML once. The second time you share the same URL and they see the new version without an email thread is when this workflow clicks.
If you are comparing raw HTML hosting options, read Host AI-generated HTML documents with version control and analytics next for a feature-level view of what “after hosting” should include. And if your current habit is exporting to PDF before sharing, Publish your Claude HTML instead of converting to PDF explains why the HTML is the better deliverable.
Frequently asked questions
- Is Claude’s artifact publish enough for client delivery?
- It’s perfect for ad-hoc sharing. For recurring client links, version history, and a URL that stays the same when you update, you want a dedicated host that treats the document as a product surface—not a one-off file drop.
- Can I update the same link after I change the HTML?
- With unfurl, a live share link can always point at your latest published version, while the dashboard keeps a full version history. Your client keeps one bookmark; you keep control of what they see when they open it.
- What if I use Cursor or another tool instead of Claude?
- The same pattern applies. Generate HTML from any model or editor, then publish the file through drag-and-drop, the API, or MCP. The value is the last mile: a professional URL, not another attachment.
Ready to publish?
Drag and drop HTML, use the API, or connect via MCP—your document gets a permanent link that updates when you publish.
Publish your first document