Claude Artifact to PDF: Print to PDF, One Tall Page or A4

To turn a Claude artifact into a PDF, open its HTML in a browser tab of its own and print it with Save as PDF as the destination, or render it as a single PDF page sized to the design. Printing keeps the text selectable and searchable but splits the page onto A4 or Letter sheets, where page breaks can cut charts in half. A single tall page keeps every chart and card whole, but the text becomes part of an image. Claude Design, Slides and Docs artifacts are different again: they have their own PDF export.

Does Claude have a PDF export for artifacts?

Only for template artifacts. Since 16 September 2026, Design, Slides and Docs artifacts each have an Export menu, and PDF is in all three. Ordinary artifacts, the dashboards, reports and small tools Claude builds in a chat, have no documented PDF export, and Claude Code artifacts have no download of any kind.

For Claude Design files, the Claude Design to PDF guide compares the built-in export with a rendered one. The rest of this guide is about everything else.

How do you print a Claude artifact to PDF?

1. Get the HTML. For a chat artifact made before 16 September 2026, use the controls at the top of the artifact panel to download it. For a newer one, use Share, then Export, then HTML. For a Claude Code artifact, ask Claude Code to "save the HTML file for this artifact to my Desktop".
2. Open it on its own. Drag the .html file into a Chrome window. Printing the claude.ai tab itself is unreliable: you get Claude's page with the artifact inside it, not the artifact on its own.
3. Print. Press Ctrl+P (Cmd+P on a Mac) and set Destination to Save as PDF.
4. Set it up. Under More settings, pick the paper size (A4 or Letter), margins and scale, and tick Background graphics.
5. Save.

Firefox and Safari work the same way; there the option is called Print backgrounds. The result has real text, so it can be searched and copied, and its links still work.

What goes wrong when you print an artifact?

Artifacts are designed as screens, and printing turns them into paper. Expect some of these:

• Page breaks cut through things. The browser breaks wherever a sheet runs out, through a chart, a card or a table row.
• Backgrounds vanish. Browsers skip background colours and images by default, so a dark or coloured design prints white unless Background graphics is ticked.
• The layout changes. An A4 sheet is about 794 pixels wide in browser terms, before margins, so a dashboard built for a 1280-pixel screen switches to its narrow layout or gets squeezed. Landscape and a smaller scale help.
• Controls come along. Buttons, sliders and filter bars print as they are. The upside: print takes the page as it is on screen, so you can click to the tab you want first.
• Long pages become many sheets. Right for a report, wrong for a dashboard meant to be seen in one go.

How do you make an artifact print cleanly?

Ask Claude to add print styles. They only apply when the page is printed, so the artifact looks the same on screen:

Add print styles to this artifact for A4 paper: never split a card, chart or table row across two pages, start each main section on a new page, keep background colours when printing, hide buttons, sliders and filters, and use 15 mm margins. Send me the whole HTML file.

Print again with Background graphics ticked. If a chart still splits, ask Claude to "start the [section name] section on a new page". This is the one route to a multi-page PDF of an artifact with selectable text and no awkward breaks, which makes it the right choice for reports, proposals and anything someone may print.

When is one tall PDF page better than A4 sheets?

When the artifact is meant to be seen whole: a dashboard, a one-page summary, a landing page mock-up, an infographic. One page has no breaks at all, so nothing is cut in half, and the PDF looks like the page in a browser window. People open it, scroll once and see everything.

Renda makes this kind of PDF. Paste the HTML or drop the file into the Claude Artifact to PNG tool and choose PDF, Fit to design. It captures the whole page at its natural width (1280 pixels if the page sets none) and turns it into one PDF page of the same shape. Pages up to 4096 pixels tall are captured at 2x and up to 8192 at 1x; anything taller is cut at 8192 pixels, so print a very long report instead.

Fit to design or A4: which should you choose?

The rendered A4 options place one capture of the design on a single sheet, centred and fitted with margins, never stretched. Unlike Fit to design, they do not capture a long page from top to bottom or continue it onto more sheets, so anything below the first view may be left out. Keep them for pages that are already roughly A4 shaped. For anything long, use Fit to design, or print to PDF if you need several A4 pages.

Does it matter that the text is not selectable?

It depends who, or what, reads the PDF. A rendered PDF is a picture of the page: you cannot search it, copy from it or click its links, screen readers cannot read it, and software that reads documents, such as the applicant tracking systems that screen CVs, may find no text at all. A printed PDF keeps real text and avoids all of that.

For dashboards, slides and visual one-pagers, the picture is often the point: it looks identical on every device and nobody can accidentally reflow it. For reports, proposals, CVs and anything people will quote, search or print, choose print to PDF. You can make both from the same HTML. For a CV in particular, see turning an AI-written resume into a PDF.

Frequently asked questions