The handbook/Artifacts: Beginner Guide to Claude Code
SettingsMy workspaceOfficial docs ↗

Learn one feature at a time

Turn a conversation
into something usable.

Understand Claude artifacts, create a simple example, and review sharing and data access.

STEP-BY-STEP HANDBOOKChecked September 24, 2026

What is an artifact?

An artifact is a reusable output that opens beside a Claude conversation: a document, design, dashboard, or small interactive tool. You can revisit it from the Artifacts tab. Design, Slides, and Docs templates have their own availability requirements.

Make a small practice artifact

  1. Open a Claude conversation or the Artifacts tab.
  2. Ask for one useful, bounded output.
  3. Inspect the content and try every control.
  4. Request one clear revision at a time.
  5. Check the audience and data behavior before sharing.
Claude conversation • Example artifact request
Create an interactive practice checklist for learning GitHub. Use fictional examples only. Include six steps and a reset button. Explain whether progress persists after a reload. Do not connect accounts or publish it without my approval.

Artifacts from Claude Code

Claude Code can publish session output as a hosted artifact, such as a change walkthrough. Publishing uploads content. Auto mode may approve publishing through its classifier, while Manual and Accept Edits normally ask for the initial publication. Review your mode and what the page contains.

A local HTML file alone is not proof of a published artifact. Check the returned link and the actual audience. A prototype also needs review before it becomes a production application.

Publishing controls

Claude Code artifact publishing requires a supported session and claude.ai sign-in. On Pro and Max, a public link is the only sharing option, and anyone with that link can open it without signing in. An artifact using connectors cannot be shared publicly, so it remains private on those plans.

To disable Claude Code artifacts, set "enableArtifact": false in the applicable settings or deny the Artifact tool. Inspect existing settings and organization policy first.

Check data and sharing

Artifacts can use personal or shared storage and connected apps where supported. Before entering information, check who can see it and which tools it can call. Use fictional data while learning. Check Settings → Capabilities if artifact creation is unavailable; your organization may manage access.

Keep the products distinct: this guide’s My workspace saves text drafts. It is not your Claude Artifacts library. For visual design work, continue to Claude Design.

References

Was this chapter useful?

Report an error

Votes are shared only if you enable optional measurement in Privacy & Preferences.

CONTINUE THE GUIDEClaude Design

Edit this example

Changes here affect this copy only. Nothing runs from this site. Closing this window discards your edits.

Search the field guide

Search all chapters and FAQ answers. Use Tab to reach a result and Enter to open it.