Claude Design

Claude Design is a visual workspace from Anthropic Labs, the team that incubates experimental products on top of Claude. You describe a prototype, deck, or one-pager, Claude builds it on a canvas, and you refine it through conversation, inline comments, direct edits, or sliders Claude creates for the parameters worth tuning. It launched as a research preview on April 17, 2026, powered by Claude Opus 4.7, and is in beta as of September 2026.

It is aimed at product teams and founders who need something clickable or presentable fast, and at marketers producing landing pages and one-pagers on brand. Designers use it to turn static mockups into interactive prototypes without a code review; the design-system ingestion is what makes the output usable rather than generic.

Highlights

• Prototypes, decks, and documents from one prompt. Interactive prototypes, wireframes and mockups for feature flows, pitch decks, landing pages, social assets, dashboards, onboarding flows, forms, internal tools, and one-pagers.
• Design-system ingestion. During onboarding Claude reads your codebase and design files and builds a design system; every later project uses your colors, typography, and components. Sources include GitHub repos, design files, raw uploads, and a local codebase through /design-sync. Admins on Team and Enterprise can approve and lock the standard system.
• Three ways to refine. Chat for structural changes, inline comments for a specific component, and direct canvas editing (drag, resize, edit text) for layout. Claude can also generate sliders for a value you want to explore.
• Real exports. PPTX, PDF, standalone HTML, zip download, Send to Canva, and an org-scoped link. Integrations with Adobe, Base44, Gamma, Lovable, Miro, Replit, Vercel, and Wix.
• Handoff to Claude Code. When a design is ready to build, Claude packages a handoff bundle you can pass to Claude Code, locally or on the web, with a single instruction.
• Code-powered prototypes. Prototypes can include voice, video, shaders, 3D, and built-in AI, so a demo can behave like the product rather than a click-through.

In an AI-assisted workflow

The pattern that fits most teams: ingest the design system once, generate in Design, then hand the bundle to Claude Code for the real implementation. That keeps Design as the exploration layer and the repository as the source of truth.

Using our design system, build an interactive prototype of the new
billing settings page: plan card, usage meter, and an upgrade modal.
Add a slider for the usage percentage so I can screenshot 20%, 80%,
and 100% states. Then package a handoff bundle for Claude Code.

For a deck, the same flow ends in PPTX or Canva instead of code. The Cowork agent can gather the research that feeds the deck; Design produces the deck itself.

Good to know

Availability, as of September 2026: beta on Pro, Max, Team, and Enterprise, included with the subscription. Enterprise requires an admin to enable it in organization settings. It is not on the Free plan; the plans comparison covers what each tier includes. Access is at claude.ai/design on the web or from the Claude Desktop sidebar; there is no mobile version. Design is web and desktop only.

How it compares: v0 and Lovable generate working apps from prompts and are the closer fit when the goal is shippable code from the start. Figma MCP is the route when the design already lives in Figma and you want an agent to read it. Claude Design sits between: faster than an app builder for exploration, decks, and documents, with a bundle you hand to Claude Code when it is time to build. Because it is early and Anthropic ships changes often, expect the export list and editing controls to keep moving.