Most of the time Claude replies in the chat, and the answer scrolls away as you keep talking. That is fine for a quick question. But when you want something you will keep, edit, and use later, a reply in a chat is the wrong shape. That is what artifacts are for.
An artifact is a substantial, self-contained piece of work that Claude opens in its own panel beside the chat: a document, a table, a checklist, a diagram, or even a small working app. It sits there while you refine it, and you can download it or come back to it later. Think of the chat as the conversation and the artifact as the thing you are actually making.
What Claude can build
Artifacts cover a wide range. The common ones are documents (a report, a policy, a one-pager), tables and checklists, diagrams and flowcharts, SVG images, and small single-page websites. Claude can also build little interactive tools: a calculator, a quiz, a tracker, a simple game, even a small app that calls on Claude's own intelligence, all from a plain-language description, no coding on your part.
Claude decides to make an artifact on its own when the content is big enough and self-contained (very roughly, more than a dozen lines and something you would want to reuse). You do not have to know the rule: if you want an artifact, just ask for one. "Make this a checklist I can keep" or "build me a one-page tool for X" does the job.
(One-time setup: artifacts need "Code execution and file creation" switched on in Settings, under Capabilities. If you never see a side panel appear, that toggle is usually why.)
Editing, keeping, and sharing
The best part is that an artifact is alive, not a printout. To change it, just tell Claude ("make it shorter", "add a column for cost", "change the tone"), and it updates the panel in place, keeping the earlier versions so you can flip back. For a Markdown document you can go further: highlight the exact text and pick Edit with Claude, so you do not have to describe which bit you mean.
In the corner of the panel you can view the code, copy it, or download the file to use anywhere. And when you want to keep an artifact or send it on, click Publish: that adds it to the Artifacts section in your sidebar and gives you a link. (On Team and Enterprise, sharing stays inside your organisation.) One thing to know: an artifact made in a chat does not save to your sidebar on its own, so if it is a keeper, publish it.
When to ask for one
The rule is simple. If you will edit it, keep it, or use it outside the chat, ask for an artifact. A checklist you will reuse each week, a template, a comparison table, a mockup to show a colleague, a small tool that does a repeated calculation: all artifacts. A quick fact or a one-line answer: just a reply. Reach for an artifact when you are making something, not just asking something.
Try it
Ask Claude: "Build me a one-page pre-meeting checklist as an artifact, the things I should prepare before any client call." Watch it open in the side panel. Now edit it without starting over: "add a section for questions to ask" and "make it fit on half a page". See the versions stack up as it changes.
When you are happy, click Publish so it lands in your Artifacts sidebar, then reopen it tomorrow. That is the whole loop: make, refine, keep, reuse. It is how a chat turns into something you actually use at work.
(General exercise. Role and industry versions come once accounts are in.)