HTMLRadar · Free tool

Turn a Claude artifact into a PDF, in your browser.

Updated August 2026

Save or export the artifact as an HTML file, drop it here, and press Save as PDF. Your browser’s own print dialog writes the PDF, and the file itself is never uploaded to HTMLRadar. Scripts, forms and navigation are blocked in the preview, so interactive artifacts print as their static layout. The PDF is a frozen copy; the HTML stays the version you can send as a tracked link.

Drop an HTML file, or click to browseSingle-file .html or .htm, up to 30 MB. The file is never uploaded to HTMLRadar.

How it works, in three steps

  1. Save or export the artifact as an HTML file.
  2. Drop that file above. Your browser renders the preview.
  3. Press “Save as PDF”, then choose Save as PDF as the destination in the print dialog your browser opens.

What you get, and what you do not

You get the page exactly as your browser lays it out for print. Scripts, forms and navigation are blocked in the preview, so an artifact that builds part of itself after loading, or that reveals content on a click, prints as its static layout. Long pages break across print pages the way the browser decides.

What happens to your file

The file itself is never uploaded to HTMLRadar. Your browser reads it, previews it, and prints it, and you do not need an account.

One thing worth knowing: if the HTML references images, fonts or stylesheets on other websites, your browser fetches those to render the preview, exactly as it would on any web page. Scripts, forms and navigation are blocked in the preview.

Common questions

How do I turn a Claude artifact into a PDF?
Save or export the artifact as an HTML file, drop it on this page, and press Save as PDF. Your browser opens its own print dialog; choose Save as PDF as the destination and pick where the file goes.
Does my file get uploaded to HTMLRadar?
No. The file itself is never uploaded to HTMLRadar: your browser reads it, renders the preview, and prints it, and no sign-in is required. If the HTML references images, fonts or stylesheets on other websites, your browser fetches those to render the preview, exactly as it would on any web page. Scripts, forms and navigation are blocked in the preview.
Why does my interactive artifact look static in the PDF?
Scripts, forms and navigation are blocked in the preview, so anything that only appears after a click or an animation will not be in the PDF. You get the static layout. If the artifact needs to stay interactive, share it as a live page instead.

A PDF answers nothing after you send it. On Thursday you still cannot tell whether the client read the pricing section or stopped on page two. The same HTML file, sent as a tracked link, does answer that: opened at 4pm, four minutes on scope, the pricing section read twice. Keep the PDF for whoever asked for one, and send the artifact as a tracked link to the person whose answer you actually need.

Related: HTML file to link and tracking Claude artifacts.