Claude Design's own site closes, ZDR teams can't migrate

If your organization runs with zero data retention, Claude Design has no migration path for you: ZDR organizations can't turn on artifacts, so projects have to be downloaded one .zip at a time, according to a Claude support article. The deadline comes from Anthropic closing the standalone site at claude.ai/design on December 14, 2026 and moving Claude Design into Artifacts in the Claude app.

At a glance

• After December 14, 2026, claude.ai/design takes you to Claude, and every new design, design system or slide deck you start in Claude is created as an artifact.
• Design systems can be migrated now, but the copy arrives frozen: you can't edit it on its own page yet, and editors see a note telling them to ask Claude for changes.
• Projects stay on the old site until it closes, public project links stop working afterwards, and Anthropic says details on moving projects into Claude are only coming soon.

If you haven't followed it: according to Anthropic, Claude Design launched as an Anthropic Labs product powered by Claude Opus 4.7, in research preview for Pro, Max, Team and Enterprise subscribers. The Learn AI wiki, an unofficial source, dates the launch to April 17, 2026 and describes a web workspace at a dedicated URL.

Migrated design systems keep their files but can't be edited on their page yet

Design systems are the one thing you can move today. A migrated system shows up in the design system menu when you make designs and slide decks in Claude. The full list sits under "View design systems" in the Claude Design menu on the Artifacts page and opens in Settings, where owners can pick an organization default with "Set as default."

The copy keeps its files exactly as they were, and the original stays untouched in the standalone version until it closes. What you lose for now is direct editing. The page is locked, and editors see a note at the top: "Migrated from the standalone version. Ask Claude to make changes."

Seven kinds of file problems block a migration, and three more need an organization owner

Systems that fail are listed under Couldn't be migrated, with name, owner and a short reason such as "it's too large." A banner on the Artifacts page keeps count, for example "6 of your 11 design systems couldn't be migrated." Anyone who can edit a system can run the check and fix it; everyone else has to ask the owner named in the row.

The fixes are mundane: shrink oversized files, rename ones with names an artifact can't use, convert unsupported kinds, drop files that can't go in a design system artifact, re-save ones that can't be opened, fix unreadable characters, re-upload missing ones. If the whole system is too big, the card says "It's too large. Make it smaller."

Three reasons belong to the organization owner: design systems turned off for the team, the team unable to publish artifacts, or the system owner's role lacking design systems. The first two halt the migration and leave the rest under Not started. A message saying the problem is in the migration, not your files, means try again later.

Up to 60 projects appear in Claude, but they still open on the old site

Projects don't migrate yet. They stay in the standalone version and keep working until it closes, and the Artifacts page in Claude lists up to 60 of them, each opening back on the old site. Anthropic says more details about moving projects to Claude are coming soon.

Whatever isn't carried over stays on the old site and is deleted after it closes, in December 2026, per Anthropic's data retention practices. Public links to standalone projects stop working at the same point. If the owner of a project or design system has left your organization, its Primary Owner takes over.

The fallback is downloading, one project at a time: each yields a .zip with every file, free and outside your usage limits. For design systems, "Migrate again" in the Claude Design menu picks up new, changed or fixed ones. To replace a migrated copy, delete it and migrate again, duplicating it first if you've edited it.

On Enterprise plans, design systems and the Design and Slides templates start switched off

Everything rests on the Artifacts setting, on by default. Under Templates sit two more switches: Design systems, for migrating and creating systems, and Design and Slides, for new designs and decks. Both are on for Team plans and off for Enterprise plans. With artifacts off, nobody can design in Claude or migrate, and the "Claude Design lives here now" banner never appears.

On Enterprise plans with custom roles, each role also needs these permissions, listed under Artifacts in the role editor, so access can be limited to Claude Design users. While Design systems is off, owners clicking "Migrate team design systems" get an "Open Organization settings" button; everyone else sees it grayed out with "Ask your admin to turn on Design systems."

If your organization's default design system migrates, it becomes the default in Claude too, unless one is already set there. ZDR organizations sit outside all of this: they can't turn on artifacts at all, so downloading is their only option.

Why does everything hinge on artifacts?

Because in the new setup a design is an artifact. According to MindStudio, a third-party blog, Claude's Artifacts system generates a self-contained HTML, CSS and JavaScript file and renders it live in the chat. Claude's product page adds that every artifact gets a link, private by default until you're ready, and describes pulling a design system in from Claude Code with /design-sync.

The design system is the other half. According to Anthropic, Claude builds one during onboarding by reading a team's codebase and design files, and every later project inherits its colors, typography and components; teams can keep more than one. Think of a brand style guide the designer rereads before every job, which is why it travels separately from projects.

In our view, it is odd to fix a shutdown date for the standalone site while project migration details are still only "coming soon": design systems get a path, the work built on them does not yet. The frozen copies add friction too, since any edit to a migrated system has to go through Claude rather than its page. For ZDR customers the outcome is plainer still: a manual export, one project at a time.

What has to happen by December 14 The standalone site stays open until December 14, 2026; after that claude.ai/design leads to Claude, originals are deleted and public project links break. No date has been given for the promised project migration details, so teams with more projects than the 60 the Artifacts page lists should plan for downloads. Enterprise owners also need to switch on design systems and templates before anyone can migrate.