Text Artifacts: documents you can export and share
Finished documents, not buried paragraphs in a chat
After this, you'll be able to ask Claude for a standalone document and get it in the panel. You'll export or copy it as a finished piece, instead of scraping text out of the chat.
Before you start
Complete What Artifacts are (and why they show up in the right panel) first; this lesson builds on knowing where the Artifact panel is, because a Text Artifact is the first kind of output you will pull out of it.
The idea
A Text Artifact is a finished document Claude builds for you in the panel. Reports, SOPs, templates, and outlines all count. Unlike a chat reply you lose in the scroll, this one has a title, headings, and its own copy and export buttons.
(An SOP is a step-by-step instruction sheet for a recurring task. It only helps if your team can open and follow it, not if it is trapped between two of your chat messages.)
Here is the before and after: Ask "how do I onboard a new hire?" and Claude gives you advice in the chat that is awkward to forward. Ask "write an onboarding SOP for a new marketing hire, with numbered steps and a checklist" and a clean, titled document opens in the panel, ready to drop into your team wiki.
Now try it: send "Create a one-page SOP titled 'How to publish a blog post' with numbered steps, then a final checklist. Make it a document I can export." When it opens, use the export button, then paste it elsewhere to confirm the formatting survives.
Ask for a document by name and you get a finished piece you can hand off, not text to scrape out of a chat.
Try it (9 min)
Watch out for
- Copying the document out of the chat text instead of the panel; the panel version keeps the formatting, the scraped version often does not
- Asking for 'tips on' a topic when you want a deliverable; 'tips' gets a chat reply, 'a document' gets a Text Artifact
- Forgetting to say roughly how long you want it; without a length cue Claude may write three pages when you wanted one
- Pasting into a tool that strips formatting and blaming Claude; test the paste target, since some apps drop headings
- Treating the first version as final; a Text Artifact is meant to be refined, which the last lesson in this module covers
Paste this into Claude
Create a standalone document for me, formatted as a finished piece I can export and share. Title: "Standard Operating Procedure: Publishing a Blog Post" Include these sections: 1. Purpose (one sentence on what this SOP covers) 2. Before You Start (a short list of what you need ready) 3. Steps (numbered, in order, plain enough that someone new could follow them) 4. Final Checklist (checkboxes for the things that must be true before publishing) Keep it to about one page. Make it a clean document, not a chat explanation, so I can export it and paste it into our team wiki without editing the formatting.
What good looks like
- The output opened as a document in the Artifact panel, with a title at the top
- All four sections are present and clearly labeled
- The Steps section is numbered and written so a new person could follow it without you
- The Final Checklist reads as a checklist, not a paragraph
- You exported or copied the document and the headings and numbering survived the paste
When this breaks
- Breaks when you request 'advice' or 'thoughts' because those words tell Claude you want a conversation, so the output stays in the chat and never becomes a document you can hand off.
- Breaks when the export target cannot hold rich formatting because the document was built with headings and lists, so pasting into a plain-text-only field flattens it and the structure is lost.
AI can help with this
Paste this into claude.ai, filling in the brackets: 'Create a standalone document I can export: write a [SOP / report / template] titled [your title] with [the sections you need]. Keep it to about [length]. Make it a clean document, not a chat explanation, so I can export it without fixing the formatting.'
You can now
You can complete the lesson outcome in a real Claude chat, Project, Artifact, Connector, Desktop, or Code surface.
- You can verify that the output opened as a document in the Artifact panel, with a title at the top.
- You can verify that all four sections are present and clearly labeled.
- You can verify that the Steps section is numbered and written so a new person could follow it without you.
- You can verify that the Final Checklist reads as a checklist, not a paragraph.
Key takeaways
A Text Artifact is a finished document with its own export controls, not a paragraph buried in a chat. Ask for the deliverable by name and you get something you can hand off as-is.
- Ask for a named document (report, SOP, template, outline) to get a Text Artifact instead of chat advice.
- Export or copy from the panel, not the chat text, so the formatting comes with it.
- State a rough length so Claude does not over-write a one-page document into three.
- Test your paste target; plain-text fields can flatten headings and numbered lists.
- Plan to refine the first draft; a Text Artifact is a starting point you can edit in place.
Go deeper