Document Artifacts
Document Artifacts are for long-form text outputs — reports, technical specifications, README files, proposals, and structured prose. They appear in the Artifact panel with rendered Markdown formatting, keeping the conversation thread clean while giving you a polished, exportable document.
When to Ask for a Document Artifact vs a Chat Response
The choice affects how you interact with the output:
Use a Document Artifact when
- The output is a deliverable you'll use outside the conversation
- Formatting matters — you want rendered headings, tables, and lists
- You plan to copy, download, or share the output
- The content is long enough that it would crowd the conversation thread
- You'll want to iterate on and refine the document
Keep in conversation when
- The output is an answer or explanation, not a deliverable
- You want to discuss the content inline, not act on it
- The content is short (a few paragraphs)
- You want the output to flow as part of the conversational context
Markdown Rendering in the Artifact Panel
Document Artifacts render Markdown natively. The following all render correctly in the Artifact panel:
- Headings (
#,##,###) - Bold, italic, and strikethrough text
- Ordered and unordered lists (including nested lists)
- Tables with aligned columns
- Code blocks with syntax highlighting
- Blockquotes
- Horizontal rules
- Inline links
What does not render: HTML tags, embedded images from URLs, interactive elements. For interactive or visual content, use React or SVG Artifacts instead.
Common Document Types
Technical documentation
README files, API documentation, setup guides, architecture decision records (ADRs), technical specifications. Ask Claude to follow a specific format: "Write this as a standard README with sections: Overview, Installation, Usage, Configuration, Contributing."
Business documents
Project proposals, executive summaries, meeting notes, status reports. Specify the audience: "Write this as a one-page executive summary for a board audience — no jargon, focus on outcomes and risks."
Structured data summaries
Analysis outputs, comparison tables, research summaries with citations. Markdown tables in Document Artifacts render cleanly and are easy to copy into presentations or spreadsheets.
Formatting Control
You have full control over the document structure. Be explicit about what you want:
- "Use H2 headings for major sections and H3 for subsections."
- "Include a summary table at the top before the detailed sections."
- "Use bullet points for lists, not numbered lists."
- "Include a code block example in each section."
- "End with a ‘Next Steps’ section listing 3 action items."
If you have a template you want to follow, paste it into the prompt: "Write this document following this template: [paste template]."
Exporting Document Artifacts
- Copy to clipboard: The copy button copies the raw Markdown source, which you can paste into any Markdown-aware editor (VS Code, Notion, Obsidian, GitHub)
- Download: Downloads the Artifact as a
.mdfile - To Word/Google Docs: Copy the Markdown, then use a Markdown-to-Word converter (e.g. Pandoc) or paste into a tool that accepts Markdown (Notion imports Markdown natively)
- Share link: Share the Artifact directly as a read-only view from Claude.ai
Checklist: Do You Understand This?
- Document Artifacts are for deliverable text outputs — reports, specs, READMEs — not conversational answers
- Markdown renders fully in the Artifact panel: headings, tables, code blocks, lists
- Be explicit about document structure — headings, section order, table of contents, format of each section
- Copy the raw Markdown and paste into VS Code, Notion, Obsidian, or GitHub — it renders natively
- Subsequent modification requests update the same Document Artifact with a new version