How to use Claude artifacts in 2026: pick the right form

If you search for how to use Claude artifacts, most of what comes back describes a feature that no longer exists in that form: code and diagrams in a side panel, stuck inside the chat that made them. In mid-September 2026, Anthropic made Claude Docs and Claude Slides built-in artifact types alongside Claude Design, and artifacts moved out of individual chats and into your account (release notes; Anthropic blog).

That change affects more than a tutorial's screenshots. The main skill is no longer getting Claude to make an artifact. It's choosing which kind of thing to ask for. This post covers what an artifact is now, what changed, and a four-question test for picking the right form. At the end we point to a nine-lesson course that covers the whole workflow.

What an artifact is now

Anthropic's help center defines an artifact as "anything Claude makes for you that you'd put in front of someone": a design, a deck, a document, a dashboard, or a small interactive tool (What are artifacts). It opens in its own panel next to the conversation, so you keep working on it without it scrolling away.

That definition is about audience, not technology. An artifact is the thing that outlives the conversation because someone else will read it, present it, or use it.

What changed in 2026

Three changes matter if you learned artifacts before this autumn:

• Artifacts live in your account, not the chat. Everything you make is collected in the Artifacts tab in the sidebar, and every update saves a new version (What are artifacts; Use artifacts in Claude Cowork). Losing track of a chat no longer means losing the checklist you made in it.
• There are ready-made types. Docs are living documents you edit with Claude and your team, Slides are decks built from your notes or the chat, and Design covers visuals, mockups and one-pagers (What are artifacts).
• Chats made before September 16, 2026 hold "legacy" artifacts. They keep working and can still be shared, but you can't make new ones that way (What are artifacts).

One caution: the rollout is still in progress, and Anthropic's pages don't yet agree on which plans get templates first. Check the current plan table before you rely on a particular feature. Artifacts also need Cloud code execution and file creation turned on, in Settings, then Capabilities on a personal account, or by an Owner on a Team or Enterprise account.

The real skill: choosing the form

The same request can come back in very different shapes. Ask for "the launch plan" and you might get bullets in chat, a Word file, a shared doc, a deck, a poster-style design, or a checklist page your team ticks off every day. Each fits a different job, and picking the wrong one costs you later: a deck that three people have to edit together, or a file you download only to upload it again.

The course we built around this uses four questions, in order:

1. Will you use it again or share it? If not, a chat reply is fine.
2. Does it need to go into another app as a file today? Only then ask for a .docx, .pptx, .xlsx or PDF. Docs, Slides and Designs all export later, so "my boss wants a PowerPoint" usually means make Slides, then export.
3. Will people interact with it repeatedly by ticking, filtering, or calculating? That's a small interactive page, not a document.
4. Is it mainly read and edited, presented, or looked at? That picks Doc, Slides, or Design.

This is our own heuristic, not an Anthropic rule. It works because it follows Anthropic's descriptions of each type and names the question people usually skip. For Doc versus Design, one quick test helps: strip the formatting and ask whether it still does its job. If it does, you probably want a Doc. If it only works because of the formatting, you want a Design.

Name the form in your prompt

When you don't say what you want, Claude decides for itself. The signals it uses (length, reuse, whether the content stands alone) tell it whether to make an artifact, but not always which kind (What are artifacts). A long launch plan clearly deserves an artifact. Claude can't tell whether you're about to present it or hand it out for comments.

The fix is to put the form word early in the request:

Make this a doc: the launch plan, for the three of us to edit.
Turn this doc into a short deck for Monday's team briefing.
Just answer in chat, no artifact: what date should we launch?

Getting the form wrong costs little, because you can reply "make this a doc instead." Naming it up front still saves a round trip, and it's the habit that separates people who use artifacts on purpose from people who wait to see what they get.

Learn it hands-on

Claude Artifacts Essentials is a nine-lesson, no-code course that takes about four hours. It covers what artifacts are and where they live, editing and versions, Claude Docs, Slides and Design, the decision guide above in full, and how to share an artifact with the right people at the right access level. Every lesson ends with a practice task you run in Claude. The capstone is a three-piece launch kit (brief, kickoff deck, and checklist page) for a fictional tea shop.

The course cites Anthropic's help center and release notes throughout. Anthropic's documentation remains the source of truth. The course turns it into a sequence you can practice, with flashcards and a lesson chat that answers from the course's own sections.