Claude artifacts explained: what they are and how to keep them

Claude artifacts are documents, designs, presentations, and other reusable outputs that open beside a conversation. Use the artifact’s export controls to keep a copy outside Claude. Save the conversation separately if you need its prompts and decisions. Controls and sharing rules differ between current and legacy artifacts.

Identify which generation of artifact you have

Claude’s general artifact guide calls artifacts made in a chat before September 16, 2026, “legacy artifacts.” Existing ones still work and can be shared or published, but you cannot create new legacy artifacts. Their panel lets you view source, copy content, or download it.

The Cowork live-artifact guide covers artifacts made before August 19, 2026. You can still open them, but cannot edit them in place. Follow its Share instructions to republish an older item as a new artifact and resume editing. First check the guide’s exceptions for your organization’s configuration.

Check the date and controls before using an older tutorial: Publish may apply to an old artifact while a new Doc uses Share.

Choose the export for your artifact type

These are Claude’s native options, separate from an extension’s chat export.

For Docs, Slides, Design, and Motion, open the artifact and select Export. Choose a format for your next task: revising, presenting, or handing over a file. Open the result in the app you’ll use and check that the details or interactions you need survived conversion.

As of November 2026, Docs, Slides, and Design are available on Free, Pro, Max, Ultra, Team, and Enterprise. Dashboards is a beta for Pro, Max, Ultra, Team, and Enterprise. Motion is a Team and Enterprise beta. Organization settings can affect availability.

For a saved Dashboard, check chart queries and refresh information, then confirm the recipient can access the connected data. If they need a file, check the controls and open any result before promising a format. An organization’s usage-analytics dashboard is a different feature.

Find it in the Artifacts tab and its conversation

Claude collects current artifacts in the sidebar’s Artifacts tab, accessible from different conversations. The artifact also opens beside its working conversation. The Docs guide describes a Doc as saved to your Claude account.

Check a distinctive section, chart, or paragraph as well as the title before exporting. Similarly named reports may belong to different tasks.

For work you will revisit, keep an index of artifact titles, source conversations, purposes, and local filenames. The artifact storage guide covers finding older work and keeping local copies.

Understand sharing, publishing, and access

Current artifacts begin private. The general sharing guide lists link sharing for Pro, Max, and Ultra, plus organization options for Team and Enterprise. Readers need a Claude account.

On Free, check the rules for your artifact type. The general sharing table leaves Free link sharing blank, but the Docs page allows Free-plan Doc links.

On Team and Enterprise, owners can allow external artifact sharing, within each type’s restrictions. Docs stay inside the organization. Artifacts using connected apps or Claude cannot use Anyone with the link. Team and Enterprise chat links also stay within the organization. Check the conversation’s permissions separately.

Legacy artifacts use Publish on Free, Pro, Max, and Ultra, or Share & copy link on Team and Enterprise. Publicly published legacy chat artifacts can be viewed without an account. The legacy instructions warn that unpublishing prevents republishing the same artifact and permanently deletes its personal and shared storage data. Sharing a legacy Team or Enterprise chat artifact also exposes the originating chat’s attachments and files.

Check each recipient’s access before sending a link. For Docs, email invitations are unavailable, readers need a Claude account, and organization boundaries still apply. Doc editors can export. Viewers can read.

Keep the deliverable and the discussion separately

A proposal goes to the client, while its conversation records requirements, rejected options, and corrections. Decide which record you need before choosing an export button.

Use Claude’s own controls for outputs made from current templates. The Claude Docs export guide explains how its native export saves the document without the surrounding conversation.

Save a useful discussion alongside the deliverable, using related names such as proposal.docx and proposal-conversation.pdf. Note which version they accompany. A title alone may not reconnect them months later.

The guide to Claude’s PDF and Word options distinguishes saving a document, generating a file, and preserving a chat. Ask which is needed when someone requests “the Claude output.”

Save chat files as a ZIP or a document appendix

In Chrome on your computer, DocMyChat saves chat artifacts and files from claude.ai. Choose Artifacts for a ZIP of their newest versions, without earlier drafts. PDF, Word, and Markdown chat exports can include artifact content in an appendix, noting how many versions each went through.

Docs and decks published as artifacts appear as titled links where they were created in the conversation, without their contents. Use Claude’s own Export for the document or deck. Slide HTML and JSON files written only to build a published deck are left out of the appendix and ZIP.

1. Open the source chat.
2. Select Export in the chat header.
3. Choose Artifacts for the ZIP, or a document format with Include artifacts enabled.
4. Open the result and check the required files or appendix material.

The ZIP is flat: all files sit at the top level, without folders. Named files keep their names, except slashes become spaces: src/parser.py becomes src parser.py. Duplicate names become notes.md and notes (2).md. Conversation exports follow the displayed branch. See the artifact download walkthrough for ZIP steps.

Interactive widgets cannot run in exported documents. Their markers point readers to the chat. Pages Claude published appear as links. Keep these references for continued online access.

Example: handing over a workshop package

Suppose your workshop chat produced a participant guide, presentation, and short animation. The organizer needs files to distribute and present. You need a record of requested changes.

Export the guide using the Doc’s controls, the deck in the presenter’s preferred format, and the animation as MP4. Open each result and compare the exercises, slide order, and final wording with the agreed material.

For revisions, agree on Word or Google Docs with colleagues before exporting. For reading, PDF may be enough. Check the format they will use.

Save the conversation separately to preserve instructions and decisions. Add individual chat files needed for delivery, checking the ZIP’s contents against a list of required files. Include that list in a handoff note so the organizer can see what was supplied.

If the package includes a Dashboard, record its question and check the displayed query and refresh information. Agree on access with the organizer. If its controls produce a file, check it before offering an offline copy.

Keep dated copies before making later changes

Save local copies at meaningful milestones, such as approval or submission, and label them separately from the working version. Keep the matching conversation when decisions matter. Reopen saved files before deleting anything you rely on.

Enterprise custom retention settings can affect artifacts. Check the admin guide and your organization’s settings before relying on an expiration date or recovery window.

We will update this page as Claude’s formats and sharing rules change. Check your account’s controls and organization settings.

Questions