Publish Your Claude HTML Instead of Converting to PDF

You already did the hard work in Claude

The workflow looks like this: you start a conversation in Claude, describe what you need, and iterate. Five or ten rounds later the artifact is a polished HTML page with structure, formatting, and maybe interactive elements. The document is done.

Then you hit "export to PDF."

Everything that made the HTML good disappears. Responsive layout becomes a fixed page. Links stop working. Tables overflow. Interactive components flatten into screenshots. You email a file that is worse than what Claude gave you, because PDF is a print format and your document was never meant for paper.

PDF is a downgrade, not a format choice

The instinct to convert makes sense: PDFs feel "official," and clients are used to receiving them. But consider what the conversion actually costs:

If you spent ten iterations getting the HTML right, the HTML is the deliverable. Printing it to PDF is like photographing a whiteboard and emailing the JPEG: you captured it, but you lost the thing that made it useful.

The workflow that replaces "export to PDF"

1. Finish iterating in Claude. Get the artifact to the state where you would normally export.
2. Copy or download the HTML. Use Claude's copy-to-clipboard or download feature on the artifact.
3. Drag the file into unfurl. Open the dashboard, drop the HTML file onto the page, and publish. You get a permanent URL in seconds.
4. Send the URL instead of an attachment. Your recipient opens the link in their browser. No download, no security warning, no "which version is this?"
5. Keep iterating. Go back to Claude tomorrow, refine the document, download the updated HTML, and publish again. The URL stays the same. The person you shared it with sees the new version automatically.

What you gain by staying in HTML

Version history without filenames. Every time you publish, unfurl creates a timestamped version. No more report-v3-FINAL-v4.html on your desktop. The dashboard shows what was live on any date.

One link for the life of the document. Paste it in a project channel, a CRM, or a client email. Update the content as often as you need. The link never changes.

A surface that looks intentional. The shared page renders your HTML cleanly in any browser on any device. On the Pro plan, add your brand logo and name so the page reads as your output, not a generic file share.

Claude's built-in publish vs. a dedicated host

Claude's artifact publish feature is fast and works well for quick, ad-hoc sharing. The gap shows up when you need the document to survive beyond that conversation:

If you are sharing a one-off artifact with a colleague, Claude's publish is fine. If the document will be updated, bookmarked, or shared with a client, publish to a dedicated host.

Try it with your next artifact

The next time you finish iterating on a document in Claude, skip the PDF export. Download the HTML, drag it into unfurl, and send the link. Open it on your phone and compare it to the PDF version. The difference is the argument.

For sales-specific workflows, see How sales teams share AI-generated proposals. For the broader hosting model, Host AI-generated HTML documents covers versioning, API access, and MCP integration.