Import

Drop your Claude Design ZIP.
Keep editing.

You started a project on Anthropic's Claude Design. You exported it as a ZIP. Now what? Open Design's welcome dialog accepts that ZIP, parses it into a real on-disk project, opens the entry file as a tab, and stages a continue-where-Anthropic-left-off prompt for your local agent. No re-prompting. No "ask the model to re-create what we just had".

How it works

Export from claude.ai

In Claude Design, hit Export → ZIP. The bundle contains the artifact files plus the metadata Anthropic ships with every project.

Drop on the welcome dialog

First time you open Open Design, the welcome dialog has a drop zone. Drop the ZIP — POST /api/import/claude-design extracts it into .od/projects//.

Keep editing with your CLI

The entry file opens as a tab, the agent gets the project as cwd, and a continue-prompt is staged. Type whatever you want changed. Your local CLI takes it from there.

Why it matters

Your project shouldn't be locked to anyone's cloud.

Claude Design is closed-source, paid-only, and cloud-only. If you want to keep working on a Claude Design artifact without an active subscription, switch models, run on a plane, or hand the project to a teammate who doesn't pay for Anthropic — there's no path. Until ZIP import.

What ports cleanly

· The HTML / CSS / JS artifact body
· Image and font assets in the bundle
· Project metadata (name, created date)
· Inline comments tied to elements

What doesn't (and why)

· Live conversation history with Claude (Anthropic-side state)
· Anthropic-internal design system bindings (we offer 141 of our own)
· Pinned model version (use whichever CLI you have on PATH)

Ready to keep editing?

Three commands to spin up Open Design locally. The welcome dialog is the first thing you'll see — drop the ZIP and you're back where you left off.

Quickstart → Why switch? See /compare

Claude Design is a trademark of Anthropic, PBC. Open Design is not affiliated with or endorsed by Anthropic.