How to Publish Claude Design Websites (2026 Guide)

Claude Design is very good at making websites. Describe a landing page in plain English and you get a live, clickable page seconds later, real HTML rendering right next to the chat, with editing modes for tweaking spacing, colors, and copy until it looks exactly right.

Then you go looking for the publish button, and there isn't one.

That's not an oversight, it's just where Claude Design's job ends. It designs and prototypes; it doesn't host. The share link it gives you is a preview for people in your workspace, not a website your customers can visit. To get your design onto the real internet, at a real URL, you need to take one more step, and there are three good ways to do it. This guide walks through all three.

What Claude Design gives you, and what it doesn't

When you finish a design session, what you actually have is real front-end code: HTML, CSS, and JavaScript that works, not a screenshot of something that might. Claude Design can export it in several formats, including plain HTML and a handoff into Claude Code.

Here's what you don't have yet: hosting, so there's no public URL for the world. No custom domain. And no backend, which matters more than people expect: a contact form that doesn't send anywhere is decoration, and the same goes for sign-ups, bookings, and payments. Claude Design builds the front of the house. Publishing means giving it an address, and usually a back of the house too.

Method 1: Export the HTML and host it as a static site

The most direct route. Export your design as HTML, then drop it on a static host: Netlify Drop, GitHub Pages, Cloudflare Pages, or Vercel all work, and all have free tiers.

This is a fine path for a single page that doesn't need to do anything: a personal page, an event page, a simple brochure site.

The trade-offs show up quickly, though. You're now managing a hosting account and DNS settings yourself. Every edit means going back to Claude Design, re-exporting, and re-uploading, so the design and the live site drift apart unless you're disciplined. And your forms still don't send, because there's still no backend. For anything beyond a static page, you'll outgrow this fast.

Method 2: Hand off to Claude Code and deploy it yourself

Claude Design has a direct export into Claude Code, Anthropic's agentic coding tool. That turns your design into a real codebase you own, and from there a developer can wire up any backend, any framework, any host.

This is the right path if you're a developer who wants full control, or the design is one piece of a larger existing codebase.

The trade-off is the same one Claude Code always carries: you're now running a software project. Framework choices, hosting, deployment pipeline, database, maintenance, all yours. Claude writes the code; the infrastructure is your job. If that sounds like a fun weekend, great. If it doesn't, keep reading.

Method 3: Publish through Floot MCP, without leaving the Claude chat

This is the sweet spot for most people: connect Floot to Claude, and the same chat where you designed the site can build and publish it as a real app.

You're not exporting files or opening a deploy dashboard. You're telling Claude to take the design you just made and turn it into a hosted website on Floot, with a live preview link while it works, a real backend underneath, and one-click publishing to a live URL.

Step 1: Connect Floot to Claude

In Claude's settings, add Floot as a connector. It takes about a minute, and the Floot docs have the current walkthrough.

Step 2: Bring your design across

In the same conversation, ask Claude to build the site on Floot using the design you made: same layout, same colors, same copy. Claude can see what it designed, so nothing gets lost in translation. You'll get a preview link from the first edit and can watch the site take shape live.

Step 3: Make it actually work

This is where the missing backend appears. "Make the contact form email me." "Let people book a slot and pay a deposit." "Add accounts so customers can see their orders." Floot includes a real database, user authentication, and payments, so these are normal requests, not feature requests.

Step 4: Publish

Say the word and your site goes live at its own URL, with one click. Connect a custom domain when you're ready. Hosting scales automatically, and Floot sites ship with pre-rendering and sitemaps, so Google can actually read your pages, something raw exported prototypes rarely handle well.

Step 5: Keep editing in chat

The part that's easy to undervalue: after publishing, the loop stays the same. Notice a typo on Tuesday, tell Claude, republish. No re-export, no re-upload, no drift between the design and the live site.

Which path should you pick?

The short version: export static HTML if you need one page on the internet and nothing more. Hand off to Claude Code if you're a developer who wants to own the stack and doesn't mind the DevOps. Connect Floot MCP if you want the design you made to become a real, published website, forms that send, logins, payments, custom domain, without touching hosting or code.

What it costs

The design work runs on the Claude plan you already pay for. Publishing is where the paths differ. Static hosts are free-ish until your needs grow. Claude Code means paying for whatever hosting and services you assemble. Floot is a flat subscription that covers hosting, the database, and publishing, and building over MCP uses zero AI credits on top of your Claude plan, no token metering, no credit packs. Two flat plans, and that's the whole bill.

FAQ

Can I publish a website directly from Claude Design?

Not today. Claude Design creates and previews designs, but it doesn't host public websites. The share link is an internal preview, not a live site. Publishing means exporting the design or handing it to a connected platform like Floot.

Do I lose my design when I move it to Floot?

No. Because the design and the Floot build can happen in the same Claude conversation, Claude carries the layout, colors, and copy across. You're reproducing the design on a platform that can host it, not starting over.

Will my published site work as a real product?

That depends on the path. A static export stays a brochure: nothing on it can save data or take payments. Published through Floot, the site has a real backend, so forms, sign-ups, bookings, and payments all work.

Can I use my own domain?

With static hosts and with Floot, yes. Floot publishes to a live URL out of the box and supports connecting a custom domain from the dashboard.

Will a Claude Design website rank on Google?

Raw exports need work: prototypes generally aren't built with meta tags, sitemaps, or pre-rendering in mind. Floot handles pre-rendering and sitemaps by default, which is most of the technical SEO checklist before you've written a line of it.

Design in Claude. Publish from the same chat.

Claude Design got you a website that looks right. Getting it live is one decision: a static export for a simple page, Claude Code if you want to own the stack, or Floot MCP if you want the whole thing, hosting, backend, domain, handled from the conversation you're already in.

Ready to publish yours? Connect Floot to Claude, point it at the design you just made, and you'll have a live preview link before you've picked a domain name.