How to Export Claude Artifacts and Move Them to Another AI

You can export most Claude Artifacts from the Export button at the top of the artifact. Docs, slides and designs each have their own formats, Claude Sheets export to .xlsx or CSV, and older artifacts made in a chat can be downloaded as code. Claude Data dashboards have no export. What none of the exports bring with them is the live part of an artifact: its saved data, its connected apps, its sharing and its comments.

The details here come from Anthropic's help center and its November 10 announcement, so check those pages if a menu has moved since.

Can you export Claude Artifacts?

Yes, with limits. Since September 16, 2026, every new artifact starts from a template. Docs, Slides and Design came first, and Data, Sheets, Whiteboards and Motion have joined since. Each template exports differently. Artifacts made in a chat before that date are "legacy" artifacts. They keep working, and they use the older controls at the top of the artifact panel.

An export gives you a file. It's a snapshot of the artifact on the day you exported it, and it won't update when the artifact does.

How do you export a Claude Doc?

Open the doc and click Export. Claude Docs go out as Word, PDF, Markdown or Google Docs.

Pick Markdown if you plan to keep working on the doc with an AI. It's plain text, every model reads it, and the headings, lists and links survive. Word and Google Docs are better when the next reader is a person who lives in those apps. PDF is for sending, not for editing.

How do you export Claude Slides?

Decks export to PowerPoint and PDF, or go straight to Google Slides as editable files. The PowerPoint keeps your slides editable. The PDF is the one to attach to an email.

How do you export a Claude Design or an interactive artifact?

Designs export as a .zip, PDF, PowerPoint or standalone HTML. For anything interactive, like a calculator, a form or a small tool, take the standalone HTML. It's the whole page in one file, and you can open it in any browser.

For a legacy artifact, use the controls at the top of the artifact panel to view the code, copy it or download it. That gives you the HTML or React source Claude wrote. A Motion artifact exports as an MP4 video.

How do you export Claude Sheets?

Claude Sheets export to .xlsx or CSV. The .xlsx keeps your tabs, formulas and formatting. CSV keeps only the values, one tab at a time, which is what you want if the rows are going into a database.

Can you export a Claude Data dashboard?

You can't export one as a working dashboard. Anthropic doesn't list an export for Claude Data, and a dashboard there is a set of queries that Anthropic runs against your warehouse or CRM on a schedule. What you can take is the queries themselves. Each chart shows the query behind it and when it last refreshed, so copy those out. Your team spent the time getting those right.

What doesn't come with a Claude artifact export?

A Claude export holds only the content. These parts stay in Claude:

• Saved data. Artifacts on Pro and above can store up to 20 MB of text between sessions, in personal or shared storage. There's no export for it. If the page itself has a way to show or download its data, use that.
• Calls to Claude. A page that asks Claude something runs on Anthropic's infrastructure, and each viewer's usage counts against their own Claude plan. The exported HTML still has the code, but outside Claude those calls have nothing to answer them.
• Connected apps. Pages that read Slack, Asana or Google Calendar do it through each viewer's own Claude connectors.
• Sharing and comments. Who could open the artifact, who could edit it, and every comment thread.
• Version history. You get the latest version only.

One warning for legacy artifacts. Anthropic says that unpublishing one "also permanently deletes any personal and shared storage data the artifact used." Get the data out first.

How do you move Claude Artifacts to ChatGPT or another AI?

Put them somewhere every AI can reach. Another chat app is the wrong place, because ChatGPT's Canvas and Gemini's Canvas each keep your work inside their own vendor's app. If you only need the files, a shared drive or a Git repository of your Markdown and HTML exports will hold them, though every change means another export. If you want your agents to keep editing them, you need a file store that any agent can read and write over MCP, the open protocol Claude, ChatGPT, Cursor and Gemini CLI all support. That's what we built Anchor for.

Here's how we'd do it:

1. Connect Claude to Anchor. On claude.ai, open Customize, then Connectors, and add Anchor from the directory. Our supported agents page has the steps for Claude Desktop and Claude Code too.
2. Ask Claude to move the artifact. Open the chat or artifact you want to move and ask Claude to save it to Anchor. Claude still has the source, so it can write the page, document or deck straight into a folder, without a download in between.
3. Upload what you exported. For anything you already exported, ask your agent to put the file in Anchor. Anchor hosts HTML, Markdown, SVG, images, PDFs and video, and reads text out of Word, PowerPoint and Excel files.
4. Turn sheets into tables. Give your agent the CSV and ask for an Anchor table. Every Anchor table is a PostgreSQL table, so ChatGPT or Cursor can query it with SQL later.
5. Rebuild dashboards as apps. Paste the queries you copied from Claude Data and ask for an Anchor app that runs them against your warehouse, CRM or an Anchor table. The queries live in the app's code, where any agent can read and change them.
6. Share and connect the next agent. Share the folder with your team, then connect ChatGPT, Cursor or Gemini CLI to Anchor. They see the same files Claude saved.

The prompt for step 2 can be this short:

Save this artifact to Anchor, in Sales > Q4 Pipeline, and give me the link.

How do you switch from Claude to ChatGPT and keep your work?

Move the artifacts first, then your conversations. Your artifacts are what your team opens every day, and they're the hard part to recreate. A chat history is easier to live without.

Once the artifacts are in Anchor, you connect ChatGPT to Anchor from the ChatGPT plugin directory, mention @Anchor in a chat, and ask it to change something Claude built. ChatGPT edits the same file at the same link, with its sharing and version history intact, so the people who use it keep their bookmark.

And you don't have to switch everyone at once. Some of your team can stay on Claude while others try ChatGPT, because both work on the same files. We wrote about that setup in how to share Claude Artifacts with ChatGPT, Cursor and Gemini, and about the lock-in risk in our Claude Artifacts alternative post.

What should you check before you leave Claude?

A short list:

• Export every doc as Markdown and every sheet as CSV, or have Claude save them to Anchor.
• Copy the query behind every Claude Data chart your team relies on.
• Pull out any data saved inside interactive artifacts before you unpublish or delete them.
• Write down who had access to each shared artifact, since sharing doesn't export.
• On Team or Enterprise, talk to your owners before you remove anyone's account. Anthropic says removing a person takes away their access to artifacts right away.