The Claude Design migration has a hard deadline: the standalone Claude Design site closes on December 14, 2026. Until then you can keep working in it, and after that claude.ai/design simply sends you to Claude. Your design systems can move over, but your chats, comments and public project links can’t.
Anthropic announced the change on October 9, according to Zeniteq, and the details below come from Anthropic’s own migration help page.
Here are the facts worth knowing before you read further.
- The standalone site closes on December 14, 2026.
- Design systems can be migrated with a built-in tool; projects can’t yet.
- Chats and comments are not carried over, and are deleted in December.
- Public project links stop working when the site closes.
- It applies to Free, Pro, Max, Team and Enterprise users.
What actually happens on December 14
Think of it as a move, not a shutdown. New designs, design systems and slide decks are now created as artifacts inside Claude, so the standalone site is no longer needed.
Projects you already have stay in the standalone version and keep working until it closes. The Artifacts page in Claude lists up to 60 of them, and they open back in the standalone site. Anthropic says more detail on moving projects is coming.
The table below shows what survives and what doesn’t.
| Item | What happens |
|---|---|
| Design systems | Can be migrated to Claude; the original stays untouched until closing |
| Projects | Stay in the standalone site; export them one at a time |
| Chats with Claude | Not carried over |
| Comments | Not carried over |
| Public project links | Stop working on December 14 |
The loss of chats is the one that catches people. If a chat holds a decision or a prompt you liked, copy it out now.
How to run the Claude Design migration for design systems
The migration tool lives on the Artifacts page in Claude, and the steps are short.
- Open the Artifacts page in Claude.
- Click “Migrate team design systems” in the banner. If you closed it, use the Claude Design menu at the top right.
- Click Migrate to confirm. Individual plans skip the confirmation and start right away.
- Wait for it to finish. Closing the window doesn’t stop it.
- Check the results under “Migrated,” which lists each system with its owner.
Anyone who can use Claude Design can start a migration, not just owners. One run brings over every design system in the organization, including ones other people built.
A few systems are skipped on purpose. Empty design systems aren’t migrated, and neither are ones made from a built-in starter theme, even if you edited them.
What to do if a design system fails to migrate
Failures show up under “Couldn’t be migrated,” with a reason such as file size. The fix is a loop you repeat until it’s clean.
Click “Fix in Claude Design Standalone,” run “Check,” fix the files it lists, then run “Check again.” The uploads folder often holds duplicate files, so trim there first. Once nothing is blocking, migrate again.
Some problems need an organization owner, such as design systems being switched off for the team. Design systems are off by default on Enterprise plans, so owners should check that early.
Zero data retention organizations can’t turn on artifacts, so they can’t migrate automatically. If that’s you, download your projects before the site closes.
How to save your projects before the standalone site closes
Projects can only be exported one at a time for now, so start sooner rather than later if you have many.
Open the project in the standalone site, click Share, then “Project HTML.” For slide decks, look under “More formats and apps.” Keep “Project archive” selected and click Export. You get a free .zip with every file, and it doesn’t count against your usage limits.
If you want to see where Anthropic’s artifact tools are heading, our look at Claude Dashboards and Motion covers the newer artifact types. And if your design work feeds AI agents, Figma’s new design-rules specs are worth a read too.
Migrating again and keeping your edits
You can run “Migrate again” from the Claude Design menu whenever you add or change a system. Unchanged ones are marked “already up to date.”
Systems you’ve edited in Claude are skipped, so your changes aren’t overwritten. Migrated systems keep their files, but you can’t edit them directly on their page yet. A note on top tells you to ask Claude for changes instead.
To replace a migrated system with a fresh copy, delete it in Claude and migrate again. To keep your edits, duplicate it first.
Frequently Asked Questions
When does standalone Claude Design shut down?
December 14, 2026. After that, claude.ai/design redirects to Claude.
Will my old chats move over?
No. Chats and comments aren’t carried over, and any left in the standalone version are deleted in December. Copy out anything you need first.
Do my public project links keep working?
No. Public links to standalone projects stop working on the closing date, so tell anyone who relies on them.
Is migration only for team owners?
No. Anyone who can use Claude Design can start it, though owners handle settings like turning artifacts on.
Don’t leave this for the last week. Migrate your design systems now, export the few projects that matter, and copy out the chats you’d miss. It takes an hour, and December 14 is a lot less stressful when it’s already done.
Leave a Reply