Loading

Creating with artifacts

Lesson 610 min
In this lessonBy the end, you’ll be able to
  • Explain what artifacts are and where your outputs live
  • Create designs, decks, and living documents as artifacts (on paid plans)
  • Edit an artifact directly, with a comment, or by asking in the conversation
  • Share an artifact and control who can see and edit it

What are artifacts?

Artifacts are the outputs you create with Claude: a document, a deck, a design, a dashboard, a prototype. Instead of getting a long block of code or text buried in the chat, you see the real thing take shape in a dedicated window alongside your conversation, ready to use and refine.

Claude creates an artifact when you ask for something that stands on its own — something you'll want to edit, reuse, or share rather than just read once. If you want to ensure Claude creates an artifact, just say so: "Create this as an artifact."

On paid plans, an artifact isn't tied to the conversation that created it: everything you make is saved in the Artifacts tab, so you can come back to it later, keep editing it, and share it with others. Think of the conversation as where you create, and the Artifacts tab as where your outputs live. (On the Free plan, an artifact stays with the conversation that created it.)

Designs, decks, and living documents

Claude has a dedicated way to make each of the most common work deliverables:

  • Claude Design creates visual work — landing pages, one-pagers, product mockups, interface prototypes. You can bring in your design system so drafts come back in your brand, and edit directly on the canvas: drag, resize, and align anything.
  • Claude Slides creates presentations. Share the notes, report, or conversation you already have, and Claude outlines, writes, and lays out every slide. You can edit any slide directly, add your own images, and present without leaving Claude — or export to PowerPoint or PDF when you're ready.
  • Claude Docs creates living documents — rich-text pages you and Claude write together. Claude drafts in front of you, asks clarifying questions, and explains its choices in comments. You and your colleagues can edit the same doc at the same time, and changes save as you go. Claude can also pull data from your connected tools into charts and diagrams right in the page — a snapshot, not a live feed; ask Claude to refresh it when you need the latest. Export to Google Docs or as a .docx file anytime.

These work together in one conversation, and you can ask for one from another: "turn this doc into a deck," or "make a one-pager from this deck."

Artifacts on every plan

Not everything needs Claude Design, Claude Slides, or Claude Docs. Ask for a dashboard of your team's numbers, a tracker you update each week, a flowchart of your onboarding process, an interactive page, or working code, and Claude builds it as an artifact right in the conversation — on every plan, including Free.

Artifacts are different from Claude's file creation, which produces downloadable Word documents, Excel spreadsheets, PowerPoint presentations, and PDF files. The practical difference: an artifact opens and updates right in Claude and is shared by link, while file creation hands you a file to download and open in other apps.

Creating your first artifact

Creating an artifact is as simple as having a conversation. Describe what you want in any conversation with Claude (the composer's Output menu lets you pick a design, slides, or a doc), or start from the Artifacts tab, where you can pick a design, a deck, or a doc and describe what you need.

For example, you might say (the first three assume your plan — and on Team and Enterprise, your admin — has the design, deck, and doc experiences turned on):

  • Turn these meeting notes into a five-slide deck for my team meetingCreates a deck you can edit slide by slide and present.
  • Draft a one-page project brief for the onboarding revamp as a doc I can share with the teamCreates a living doc your team can edit with you.
  • Design a landing page for a productivity app with a hero section and feature listCreates a design on an editable canvas.
  • Build an interactive dashboard that lets me input monthly expenses and see a breakdownCreates an interactive dashboard — available on any plan.

When the artifact appears, you can copy it or download it — and keep going: everything stays editable.

Whatever you ask for, Claude uses the context it already has — the files you've shared, the conversation so far, your project knowledge, and your connected tools — so you don't have to feed it everything. If you've just worked through an analysis together, the deck starts from that thinking.

Working on an artifact

Once an artifact exists, you have three ways to change it — and you can mix them freely (editing directly and commenting are part of the design, deck, and doc experiences):

  • Edit it directly. Type straight into a doc, edit any slide, or drag and resize elements on a design canvas. Your edits and Claude's can land side by side.
  • Comment for Claude. Leave a comment on the exact element, slide, or passage you want changed, and Claude makes the change there. In a doc, @-mention Claude in a comment and it replies explaining what it changed and why.
  • Just ask. Keep talking in the conversation and Claude takes the next pass on the artifact, showing you every change it makes.

Fixing a typo or nudging a logo yourself means you don't have to describe the change and wait for a rewrite. One note on where this happens: editing directly, commenting, and changing sharing happen on desktop or web — on mobile, you can ask for an artifact in any conversation and open it full screen in the Artifacts tab.

Sharing your work

Your artifacts are private until you share them. For designs, decks, and docs, add people by name or email and choose what each person can do — view, comment, or edit (docs offer view and edit) — or share a link with everyone in your organization. Anyone you share with needs a Claude account to open the artifact.

  • On Pro and Max plans, you choose between keeping an artifact to yourself or sharing it with anyone who has the link — and you can publish a design or a deck as a public artifact. Only the artifact becomes public — your conversation stays private.
  • On Team and Enterprise plans, links stay inside your organization by default. Sharing outside the organization ("anyone with the link") is available only after an Owner or Primary Owner turns on External sharing in Organization settings > Artifacts.
  • On the Free plan, you can copy your work, download it, or publish it so anyone with the link can view it.

When the work needs to leave Claude, export it. Artifacts export to files that match what you've made: a deck to .pptx or .pdf, a design to .pptx, .pdf, or .html, a doc to Google Docs or .docx. You can also copy or download any artifact directly from the artifact window.

Tips for getting the most from artifacts

Ask for the deliverable, not just the content. "Summarize our Q3 results" gets you a chat reply; "turn our Q3 results into a one-page doc for the leadership team" gets you an artifact you can share and keep working on.

Be specific about what you want. "Build a budget tracker" is good, but "Build a monthly budget tracker where I can input expenses by category, see a pie chart breakdown, and get a warning when I'm over budget" is better.

Describe the end user. Telling Claude who will use the artifact helps it make appropriate design choices. "This flowchart is for new employees" leads to different results than "This flowchart is for the engineering team."

Build on work you've already done. The best artifacts come at the end of a conversation, when Claude already understands the problem.

Refresh data when you need it current. Charts and diagrams embedded in a doc don't update on their own — when you want the latest numbers, ask Claude to pull fresh data from your connected tools and update the chart.

Lesson reflection

Before moving on, consider:

  • What's the deliverable you most often build by hand — a status doc, a team deck, a one-pager — that could start as an artifact instead?
  • What recurring work could benefit from having an interactive artifact you can reuse?
  • Who would you share your next piece of work with, and what should they be able to do — view it, comment on it, or edit it with you?

What's next

In the next lesson, you'll learn about Skills — reusable instruction sets that teach Claude specialized workflows.