Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Everyday tasks

Claude Design closes December 14: export now

Written November 9, 2026

claude.ai/design closes Dec 14, 2026 — read-only, public links stop working, chats and comments don't carry over. What to save, and where Design lives after.

What closes, and when

The standalone Claude Design site, claude.ai/design, closes on December 14, 2026. You can keep using it until that date. After that it is read-only, and you cannot start new projects there. Design itself is not shutting down: Claude Design now lives in Claude, where a new design, design system, or slide deck is created as an artifact. The closure is a consolidation into Claude, not a cancellation of Design.

Two things end on December 14 that catch people out. Public links to projects in the standalone version will no longer work after it closes — any link you sent a client or a colleague stops working. And the originals left in the standalone version are deleted some time later, under Anthropic's data retention practices. No cutoff hour is published; the date is the deadline.

What moves, and what does not

Design systems move, once, for the whole organization. From the Artifacts page in Claude, one move brings over every design system in the organization. The originals stay in the standalone version until it closes, and moved design systems become read-only there. A system that cannot move is listed under "Didn't move" with its name, owner, and a reason — too large, a name an artifact cannot use, a kind an artifact cannot hold, contents missing, or a file that cannot be opened. Shrink, rename, convert, or re-upload the flagged files, then move again. Empty design systems and ones made from a built-in starter theme are not migrated. A moved design system keeps its files as they were, and you cannot edit it yourself on its page yet — its editors see a note saying it was moved and that they can ask Claude to make changes.

Projects move one at a time, or all at once. Only a project's owner can move it, from the pop-up or banner in the project. On Team and Enterprise plans, an organization's owners can move everyone's projects at once with "Move everything" on the Artifacts page; only an Owner or the Primary Owner can start it. After the move, the copy in the standalone version is read-only for everyone, and this cannot be undone. Most projects keep their owner, and private projects stay private. The Artifacts page in Claude lists up to 60 of your standalone projects, and they open in the standalone version.

Chats and comments do not move. When you move a design system, your chats and comments cannot move to Claude, so they stay in the standalone version until it closes. The same applies to projects: chats and comments stay in the standalone copy, where you can read them until the standalone version closes, and are deleted some time after it closes. There is no transfer path for them. Copy anything you need out of them before December 14.

How to save your work

A download of all the projects you own is rolling out together with "Move to Claude" — you will find it on the home page of the standalone version once you have it. It includes your files, not your chats or comments, and it is not available to organizations with the HIPAA-ready configuration. If you do not have it, download your projects one at a time: each gives you a .zip file with every file in the project, free, and it does not count toward your usage limits.

One group cannot move at all. Claude Design in Claude depends on artifacts, and organizations with zero data retention cannot turn on artifacts, so they cannot move. If that is your organization, download your projects before the standalone version closes — there is no other path.

Verdict

Move design systems first, then download every project that matters — chats and comments have no transfer path, so copy anything you need out of them before December 14. Do the download even if you plan to move the project: the moved copy in Claude is the future, the .zip is the copy you control.

Steps

  1. Inventory the standalone site. List your design systems, your projects, and every public link you have sent out. The Artifacts page in Claude lists up to 60 of your projects; anything beyond that, check in the standalone version itself.
  2. Move the design systems. One person runs the move from the Artifacts page. Read the results, fix anything listed under "Didn't move," and move again.
  3. Move or download the projects. Owners move their own projects, or an owner runs "Move everything" on Team and Enterprise. Download a .zip of each project that matters, whether or not you move it.
  4. Save the chats and comments. They do not move and are deleted some time after the close. Copy the text you need now, while the standalone version still lets you read it.
  5. Replace the public links. Every claude.ai/design link stops working after December 14. Point people at the moved copy in Claude, or at a file you control.

What can go wrong

Limits

Related playbooks

Sources

Back to: Everyday playbooks hub · Also: Google Jules ends Nov 11: export your work · November shutdowns: Runloop, Conductor, Moondream · Claude Duet: Anthropic's proactive agent app