Save a Claude artifact as a PDF

To save a Claude artifact as a PDF, use Export → PDF inside a Claude Doc. For an older Markdown document artifact, copy its content into the free Markdown to PDF converter. Save the whole chat when you also need the questions, corrections, and decisions behind the document.

Use the artifact’s own PDF export first

A Claude Doc’s Export menu includes PDF. For a report, letter, or summary saved as a Doc:

1. Open the Doc you want to save.
2. Select Export inside the Doc.
3. Choose PDF.
4. Open the resulting file.

Confirm that the opening paragraph and final section match the version you intend to send. If the Doc has several tabs, check that the file contains the sections you need. The Claude Docs guide covers its other formats and sharing permissions.

Slide decks also have native PDF export. For a Claude Design project, select Export in the upper right and choose PDF.

Convert an older Markdown document artifact

Claude calls artifacts made in a chat before September 16, 2026, legacy artifacts. The top controls in the artifact panel let you view the source, copy content, and download the artifact. The artifact guide explains those panels and current templates.

For a legacy document whose source is Markdown, use the free Markdown to PDF converter. For application code, keep the source files as described below.

1. Open the document artifact in its source chat.
2. Copy the content using the panel’s top controls.
3. Paste the copied Markdown into the converter.
4. Start creating the PDF in the converter.
5. Choose Save as PDF as the destination in Chrome’s print dialog.
6. Save the file.

Copy from the artifact panel to get the document rather than the reply announcing it. Compare the pasted text’s first and last lines with the artifact before converting. Keep Markdown headings, table separators, and math delimiters intact.

The converter runs in your browser and uses the same PDF converter as DocMyChat’s extension. It formats headings, tables, and code, and typesets LaTeX formulas. In Chrome’s print dialog, under More settings, turn off Headers and footers to remove Chrome’s additions. Inspect the print preview before saving.

For example, an older artifact contains a meeting summary with three sections and a four-row action table. Copy it, convert it, and then check that all four actions and their owners appear in the PDF. Save it as planning-meeting-summary-2026-11-03.pdf. Keep the chat separately if attendees also need the discussion about dropped actions.

Include the conversation when the decisions matter

Save the conversation when a reviewer needs the prompts, requested changes, and decisions alongside the artifact.

In Google Chrome on a computer, DocMyChat can save the open claude.ai conversation as a PDF with an artifact appendix:

1. Open the relevant conversation and branch.
2. Select Export next to Share in the chat header.
3. Leave Include artifacts enabled.
4. Choose PDF.
5. Choose Save as PDF in Chrome’s print dialog.

Ordinary artifact content appears in an appendix, with a note showing how many versions it went through. Notes in the conversation mark where artifacts appeared. The chat-to-PDF walkthrough covers the full export procedure.

Published Claude Docs and decks appear as titled links where they were created, without their contents. Save those with their own native export controls and keep the resulting files beside the transcript.

Read the surrounding messages before sharing. Someone who needs a final report may not need the planning discussion. Give the transcript a distinct filename so recipients can tell it from the deliverable.

Keep source files for code and HTML

A PDF can be useful as a code-review handout or a visual reference for a web page. To run or edit the work, keep the source files too. Printed code cannot replace the files, styles, and other resources an application needs.

Use a legacy artifact’s native download control and keep the file in the format it provides. For a Design project, its own Export menu offers a ZIP file or standalone HTML as well as PDF. Choose HTML or the ZIP file when the next person needs source files to open the page or continue development. Open the saved page or project and collect any missing assets or dependencies before handing it over.

To collect ordinary artifacts and files from a chat, choose Artifacts in DocMyChat’s export menu. The artifact ZIP guide explains that route. The ZIP keeps the latest versions in a flat archive, so restore any required folder structure before treating it as a project.

Slide HTML and JSON written only to build a published deck are excluded from the appendix and ZIP. That exception does not apply to every HTML or JSON file in a chat.

Check the PDF as a reader

Open the saved file itself, then inspect the first page, the last page, and any page with a wide table or chart. Check that headings stay with their text and small labels are readable. The saved PDF is the file you’ll send.

For converted Markdown, judge the page’s readability without expecting the artifact panel’s exact layout. If a table is too wide, adjust the print layout and save another copy.

Open links you expect recipients to follow. Supply essential supporting files separately if access depends on your account. A report that refers to an inaccessible chart still needs that chart in the handoff.

Keep the source artifact or downloaded text alongside the PDF when you expect revisions. Make corrections there, then generate a fresh PDF with a distinct filename for the version you deliver.

Questions