How to Turn a Claude Artifact Into a PDF

There's no export-to-PDF button on a Claude artifact, and the obvious workaround fails in a specific, confusing way: pressing Cmd/Ctrl + P while looking at the artifact prints the conversation. You get the chat transcript, your prompts, Claude's prose — and the artifact reduced to a small panel or missing entirely.

That's not a Claude quirk so much as how browsers work. The artifact renders inside a frame within the chat page, and printing acts on the page, not on the frame. So the whole trick is getting the artifact onto a page of its own first. There are three ways to do that, and they suit different artifacts.

Route 1: Publish, then print (works for everything)

The most reliable path, and the only one that handles React artifacts without extra work.

1. Get the artifact onto its own URL. Either use Claude's Publish button, or copy the artifact's code and paste it onto a link. Both give you a page containing the artifact and nothing else.
2. Open that URL in a normal browser tab.
3. Print to PDF — Cmd/Ctrl + P, then "Save as PDF" as the destination.

Because the artifact is now the whole page, the PDF is the artifact — no chat, no sidebar, no prompt history.

Two settings are worth a glance in the print dialog before saving. Background graphics is off by default in Chrome, which silently strips every coloured header, tinted table row, and card background; a dashboard printed without it comes out as black text on white and looks broken. And Scale set to "Fit to page width" rescues a wide table that would otherwise be sliced down the middle.

If the artifact is genuinely private, use the paste route rather than Claude's Publish — you can put a password on the page, and you're not left with a public link you'd then have to unpublish permanently.

Route 2: Download, then print (HTML artifacts only)

If Claude produced a self-contained HTML artifact, you can skip hosting entirely:

1. Download the artifact — you'll get a .html file.
2. Double-click it to open in your browser.
3. Print to PDF as above.

Same result, nothing leaves your machine. The catch is that this only works when the download is actually openable, which rules out React artifacts — they download as .tsx source that a browser can't run. Which type you have, and why, is covered in how to download a Claude artifact.

Route 3: Ask Claude to make it printable first

Worth doing when the PDF is the deliverable rather than an afterthought — a report going to a client, a one-pager, an invoice.

Ask for it directly: "Add print styles so this prints cleanly on A4 — hide the navigation and buttons, avoid page breaks inside cards, and make sure the tables fit the page width." Claude will add a @media print block, and the difference is substantial. Interactive controls that mean nothing on paper disappear, and content stops breaking across pages mid-card.

This is the step that turns "a screenshot of a webpage" into something that looks designed for print, and it costs one more prompt.

If the artifact is a Markdown document

A Markdown artifact isn't a webpage yet, so there's nothing to print until it's rendered. Downloading gives you a .md file that opens as plain text with the # symbols visible.

Render it first — the Markdown to PDF converter takes the Markdown and produces the PDF in one step, no hosting in between.

What about screenshotting it?

It works, and for a small chart it's genuinely fine. For anything longer than the visible panel it isn't: you get one screen's worth, at screen resolution, with text that's an image rather than text — not selectable, not searchable, and blurry when printed. If the PDF is for anyone other than you, print properly.

Quick reference

Bottom line: the artifact has to be on a page of its own before printing works — that's the whole problem, and publishing or downloading both solve it. Turn on background graphics in the print dialog, and if the PDF matters, spend one extra prompt asking Claude for print styles.