Claude Design Standalone Closes Dec 14: What to Do With Your Tokens
By The WAALEE Team · · 5 min read
Mark December 14, 2026 on your calendar if you've built anything inside Claude Design. That's the day the standalone site at claude.ai/design closes for good, according to Anthropic's own migration guide. Claude Design itself isn't going away, it's moving to live inside regular claude.ai, but the standalone version becomes read-only and then disappears. If your design system, your projects, or your client handoffs live only there, you've got a deadline now whether you knew it or not.
What actually closes on December 14
Just the standalone site. Claude Design as a feature keeps running, folded into the main Claude product instead of its own URL. Anthropic's migration starts from the Artifacts page with a "Migrate team design systems" banner, and it's opt-in up to the deadline: nothing moves on its own. The original stays put in the standalone version, unchanged, until the whole thing closes and whatever wasn't moved goes with it.
What moves, what doesn't, and who has to click the button
This is the part worth reading carefully before you assume you're covered. Reporting on Anthropic's own guide and independent writeups lines up on a few specifics:
- Design systems move through the Artifacts banner, and only the system's owner, or an org owner moving everything at once, can trigger it.
- Projects are a separate, slower rollout. Anthropic says more detail is coming; one source reports it's rolling out gradually to paid plans only.
- Organizations on zero data retention can't move projects at all. If that's you, download your work before the 14th, there's no other way out.
- Chats and comments don't carry over. They're deleted once the standalone site closes, migrated or not.
- Public links to standalone projects stop working on the same date, migrated or not.
The deadline is a symptom, not the real problem
Say you click the banner, migrate cleanly, and everything that matters lands inside claude.ai before the 14th. You've dodged this specific deadline. You haven't fixed the thing that created it: your design system existed as one vendor's proprietary project format, reachable only through that vendor's UI, with no export path until someone wrote a migration tool under time pressure. That's true of any tool that stores your colors, type, and spacing as its own internal object instead of an open standard. The next shutdown notice, whenever it comes from whatever tool, hits you the same way.
The fix isn't migrating faster next time. It's not keeping your actual design system, the source of truth for your colors, type scale, spacing, and radii, inside any single AI tool's project format at all. Keep it as plain W3C design tokens, a JSON file you own, and feed that same file into Claude Design, Claude Code, Lovable, v0, Cursor, or whatever replaces any of them next year. The tokens outlive the tool.
Three ways to handle it before the 14th
Whether you migrate, export, or rebuild from scratch, here's what's actually available right now:
- Anthropic's native migration: The official path. Covers design systems cleanly via the Artifacts banner; projects and ZDR orgs need extra care per the caveats above. Keeps you inside Claude's format either way.
- html.to.design export guide: A third-party walkthrough for pulling a Claude Design project into Figma before the deadline. Useful if your team already lives in Figma, but it's exporting to another closed format, not an open one.
- WAALEE: Extracts your real colors, type, and spacing straight off your live site as open W3C tokens, then turns them into ready prompts for Claude, Lovable, v0, Cursor, and Bolt. No migration needed because nothing was locked in to begin with.
If you've got something in Claude Design worth keeping, go click the migration banner this week, not on December 13th. But treat the real lesson as bigger than one deadline: a design system you can only reach through one tool's login isn't a system, it's a dependency. Pull your tokens out into a format you own, and the next shutdown notice becomes someone else's problem to read about.