Publish a Claude Design Website on Your Own Domain

Claude Design turns a brief into a finished-looking page: a landing page, a pricing section, a portfolio, a launch site. In the canvas it looks ready, and showing it to a colleague takes one click. A share link is not a website, though. Anthropic's sharing rules require everyone who opens a shared design to have a Claude account, its help pages describe no way to put a design on your own domain, and public links to projects in the old standalone Claude Design site stop working when it closes on 14 December 2026. This guide covers what Claude Design exports today, the Vercel route exactly as Vercel documents it, and the VibeDeploy route: one upload, your own domain, a contact form that delivers, and updates that keep the same address.

Where Claude Design lives now

Anthropic launched Claude Design on 17 April 2026 as an Anthropic Labs research preview for Pro, Max, Team and Enterprise subscribers. It has since moved into Claude itself. The help center now describes it as one of the templates you can start an artifact from, so you can use it in any chat, in Claude Code and from the Artifacts tab. It lists Claude Design on the Free, Pro, Max, Team and Enterprise plans, and on Enterprise plans it turns on by default on 15 October 2026.

The standalone site at claude.ai/design closes on 14 December 2026, after which that address takes you to Claude. Until then your projects keep working there. Anthropic says public links to projects in the standalone version will no longer work after it closes, so if people know your design through such a link, it needs a new home before that date.

What Claude Design can export

Open the design and click Export in the upper right corner. Anthropic's help center lists these options:

• Download as .zip: in Vercel's words, a zipped folder of website files. This is the one to host.
• Export as standalone HTML: the design as an HTML export you can upload as it is.
• Export as PDF, Export as PPTX and Export to Google Slides: documents and decks, not websites.
• Send to the tools you already use: more than a dozen partner tools, among them Canva, Gamma, Lovable, Netlify, Replit, v0, Vercel and Wix.
• Handoff to Claude Code: send the project to your local coding agent or to Claude Code on the web, so it can grow into a codebase.

In the standalone site the download sits elsewhere: click Share, choose Project HTML, keep Project archive selected and click Export. Anthropic says that archive is free and does not count toward your usage limits.

For a website, take the .zip. It keeps the project's files together, so styles, scripts and images land where the page expects them.

Why a share link is not enough

Designs start private to you. Click Share and you choose who can open the design and whether they can view, comment on or edit it. For the details, Claude Design's help sends you to the artifact sharing rules, and those are strict: everyone needs a Claude account to open a shared artifact, even with the link. The only exception is a legacy artifact published from a chat, and new designs are not legacy artifacts. On Team and Enterprise plans, artifacts stay inside the organization by default.

That works well for reviewing a design with your team. It does not work for a landing page that customers, recruiters or search engines should open. For that, the files have to be on a web host, at an address you control.

The Vercel route, as Vercel describes it

Vercel is one of the destinations in Claude Design's export menu and publishes its own guide for it, with two ways in:

1. Send it from Claude Design. Open the project, select Share in the upper right corner, click Send to, then Add a destination, choose Vercel and follow the prompts to connect your Vercel account, pick a team and deploy.
2. Drop the .zip. Choose Export, then Download as .zip, go to vercel.com/drop and drag the file onto the page; Vercel says there is no need to unzip it first. Pick a team, enter a project name and select Deploy. If the export has no index.html at the top of the folder, Vercel asks which page visitors should see first.

The guide is candid about updates: each drop creates a new Vercel project, so re-exporting and dropping again gives you a new project with a new URL. Vercel's Drop documentation offers two ways to keep one project: drop a folder onto the existing project in the Vercel dashboard, which creates a new production deployment of that project, or connect a Git repository, after which, in Vercel's words, every push deploys automatically and your project URL stays the same. Both work; pick one before you hand out the link.

Publish it on VibeDeploy in four steps

VibeDeploy is where the sites your AI tools build go live. You keep designing in Claude Design; VibeDeploy hosts the result.

1. Export the design. Click Export, then Download as .zip. You do not have to unzip it, and a single folder inside the ZIP is unwrapped automatically.
2. Check the homepage file. Your address serves the file called index.html at the top of the project. If the ZIP has no index.html but only one HTML page, VibeDeploy uses that page as the homepage automatically. With several pages and no index.html, rename the main one to index.html and zip the folder again; otherwise the upload goes through, but the bare address has no page to show. A standalone HTML file needs no renaming, because an uploaded HTML file becomes the homepage.
3. Upload it. Start the 14-day trial (no card), choose Upload, name the site and drop the file. About 30 seconds later the site is live over HTTPS at an address like https://my-design.vibedeploy.be.
4. Connect your domain. Add the domain to the site in the dashboard and set the DNS records it shows: a CNAME that points www at proxy.vibedeploy.be, and for the bare domain the record the dashboard lists. Once the records resolve, the SSL certificate is issued automatically, usually within a minute.

The trial includes one custom domain that you already own. Buying a new domain through VibeDeploy needs a paid plan.

Change the design, keep the address

A design rarely stops at version one. When you change it, export the .zip again and upload it to the same site: in Upload, choose Update my site, pick the site and drop the new file. The address stays the same, your domain keeps pointing at it, and nobody you sent the link to needs a new one.

An upload replaces the whole site with the contents of the new file, so the new export should contain every page you want online. Every deploy is kept as a version, and a restore point is taken before each one. If the new export breaks something, restore the previous version in one click from the dashboard's History tab, within your plan's restore window: 3 days on the trial, Solo and Maker, 7 days on Studio and 30 days on Business.

Make the contact form deliver

Designs often include a form: a contact block, a waitlist field, a quote request. In a static export that form has nowhere to send its data until something receives it. On VibeDeploy that is the built-in forms relay, and you switch it on from Claude. With the VibeDeploy connector added (the full connector setup takes a few minutes), say:

Turn on the forms relay for my-design, send submissions to hello@example.com and connect the contact form to it.

Claude calls set_forms_config, which switches the relay on and returns the address the form should send to, then edits the form on the live site so it posts there. Each submission is emailed to up to five addresses you choose. A hidden honeypot field filters simple bots, and the recipients are fixed on the server, so nobody can redirect your submissions to another address. There is no form service to sign up for and no backend to run.

Or hand the design to Claude Code

If the design is the start of a bigger project, Handoff to Claude Code sends it to your local coding agent or to Claude Code on the web. In a local Claude Code session, add VibeDeploy once:

claude mcp add --transport http --scope user vibedeploy https://mcp.vibedeploy.be/mcp

Run /mcp in a session to sign in, then ask: "Deploy this project to VibeDeploy as my-design." Claude Code uploads the files and prints the live address, and "update the site" later redeploys to that same address. If the project has a build step, ask Claude Code to run the build and deploy the output folder. The terminal route is covered in depth in from Claude Code in your terminal to a live site.

What Claude Design does better

Claude Design is a design tool, and VibeDeploy is not one. Claude Design gives you a canvas where teammates view, comment on and edit a design with you, design systems for your brand, and exports to PDF, PowerPoint, Google Slides and Canva. Its export menu can also send a design straight to partner tools such as Vercel, Netlify and Wix; VibeDeploy is not one of those destinations, so the route above starts with an export. And while a design is still under review inside your team, Claude Design's own sharing is the better place for it.

VibeDeploy takes over once the design is finished: a permanent address on your own domain that anyone can open without an account, a contact form that delivers, versions you can restore, and hosting under EU jurisdiction.

Why host it on VibeDeploy

• Hosted in Belgium. VibeDeploy runs on its own Kubernetes cluster in Belgium, operated by Tnet Comm.V, a Belgian company. All 8 subprocessors are listed on the subprocessors page.
• Your own domain on every plan, the trial included, with SSL issued automatically.
• One address for every version, with one-click restore in the dashboard.
• Room to grow. Static sites and single-page apps are served directly. A site can also run containers next to it (your own server, Postgres, MySQL, Redis or workers; up to 6 services with 2 CPU and 2 GiB in total), deployed by your AI through the MCP tool deploy_app and isolated with gVisor. Container data is not yet included in snapshots.
• Private when you need it. Maker and up include password-protected and private sites, handy for drafts and client previews.
• Analytics built in: privacy-friendly page views and visitors per site.

The 14-day trial needs no card. After it, Solo costs EUR 4 a month (EUR 38 a year) for one site with one custom domain, and Maker costs EUR 15 a month (EUR 144 a year) for three sites. Prices include VAT where it applies. If the trial ends without a plan, the site goes offline and your files are kept for 30 days; choosing a plan in that time brings it back at the same address. Details are on the pricing page.

Sources

• Anthropic, Introducing Claude Design by Anthropic Labs (17 April 2026): the launch as a research preview for Pro, Max, Team and Enterprise. Checked 13 October 2026.
• Anthropic Help Center, Get started with Claude Design: plans, the artifact template, the Export menu and its formats, the partner tools, Handoff to Claude Code, sharing. Checked 13 October 2026.
• Anthropic Help Center, Migrate from standalone Claude Design to Claude: the closing date of claude.ai/design, public links after it closes, the Project HTML download. Checked 13 October 2026.
• Anthropic Help Center, Share artifacts: who can open a shared artifact, organization defaults on Team and Enterprise. Checked 13 October 2026.
• Vercel Knowledge Base, Deploy a Claude Design project to Vercel (vercel.com/kb/guide/claude-design-vercel-drop redirects here): the connector and Drop steps, the homepage prompt, a new project and URL for every drop. Checked 13 October 2026.
• Vercel Docs, Deploying with Vercel Drop: dropping onto an existing project and connecting Git. Checked 13 October 2026.