Build a Website With Claude: Chat, Claude Code or a Builder
Build a Website With Claude: Chat, Claude Code or a Builder
There are three practical ways to build a website with Claude. You can ask for a page in the chat app and see it right there, you can let Claude Code build a full project in a folder on your computer, or you can use an AI website builder that turns a description into a live site at a real address. The right choice depends on whether you want a draft, code, or a site people can visit.
What does "build a website with Claude" actually mean?
The phrase hides three different goals, and most frustration comes from picking a tool that serves the wrong one.
The first goal is a draft. You want to see what a page could look like: layout, sections, wording. You will throw it away or hand it to someone else. Speed matters, permanence does not.
The second goal is code. You are comfortable with a terminal, you want a project you control, and you will host it yourself. You care about structure, frameworks and what happens when you change something next month.
The third goal is a site that works. You run a business, a studio, a side project or a portfolio. You want an address you can put on a card, a form that actually sends leads, and a way to change the text without learning git.
Claude can help with all three. The tools around it differ in what you are holding at the end.
How do the three ways compare?
| Way | What you get | Where it lives | Your own domain | Skills needed | Good for |
|---|---|---|---|---|---|
| Claude app (chat) | a page you can see and click inside the conversation | in your chat, shareable by link | no | none | drafts, mockups, one-off tools |
| Claude Code | a full project in a folder on your computer | wherever you deploy it | yes, through your host | terminal, git, reading code | developers who want control |
| AI website builder | a live site at an address, with forms and publishing | on the builder's hosting, code exportable | yes, on a paid plan | none | business sites, landing pages, portfolios |
The column that decides most cases is "where it lives". A page inside a chat is perfect for looking at an idea and awkward as the thing your customers visit. A project folder is perfect if you know what to do with it and a dead end if you do not.
When is the Claude app enough?
When the goal is to see an idea quickly. Describe the page in plain words, and Claude writes it and shows it as something you can scroll and click in the same conversation. For a mockup to discuss with a colleague, a one-page tool for yourself or a first version of copy, this is the fastest route there is.
It stops being enough at the point where the page has to live somewhere on its own. At the time of writing, a page made in the chat is not a hosted website with your domain, a working contact form and a place to update prices every week. You can copy the code out, but then you are the one who has to put it online, and that is where people get stuck.
When does Claude Code make sense?
When you are, or want to become, the person who owns the code. Claude Code works in your terminal or editor: it reads the project, writes files, runs commands and builds a complete site in a folder you control. You choose the framework, you commit to your own repository, and you deploy to a host such as Vercel, Netlify or GitHub Pages.
The price of that control is responsibility. You review what it changed, you keep dependencies updated, you set up the domain and the forms. For a developer this is exactly the point. For someone who just wants the bakery's site online by Friday, it is a detour through tools they never wanted to learn.
What does a builder add on top?
An AI website builder closes the gap between "the code exists" and "the site works". In Zugo you describe the site in plain words, it gets built, and before it is called done it is checked by actually running in a browser, not by looking finished. Then it is published to an address anyone can open, and you change it by writing the next message: "move pricing above the reviews", "add a booking form".
Three things matter here, and they are the same questions to ask of any builder:
- Does it host the site, or just hand you files?
- Can you attach your own domain, and on which plan?
- Can you take the code with you if you leave?
In Zugo the answers are yes, yes on a paid plan, and yes, to your own GitHub repository, which is explained in can I export the code from an AI builder. If you are building from a phone rather than a laptop, the same flow is covered in how to build a website from your phone.
What about Claude Design and Cowork?
People also search for building a site with Claude Design or Cowork. At the time of writing, both are aimed at other parts of the work: Claude Design at visual drafts such as mockups and layouts, Cowork at tasks on your own computer. They are useful earlier in the process, for deciding what the page should look like or preparing its content. For the live site itself, the same three questions apply: where it is hosted, whether your domain can point at it, and who fixes it next month.
How should you write the prompt?
Whichever tool you choose, the first message decides most of the result. Four blocks do the heavy lifting:
- Who the site is for and what they should do. "Parents in Leeds booking a trial swimming lesson" beats "a swimming school website".
- The sections, in order. Hero, what you offer, prices, reviews, questions, contact. Name them rather than hoping.
- Real facts. Prices, opening hours, address, phone. A model does not know them, and invented details are harder to remove than to never add.
- What should not be there. "No stock photos of people", "one page, no menu". Constraints save more time than requirements.
A longer walkthrough with examples is in how to write a good prompt for a website.
Who owns the code at the end?
In the chat, you own whatever you copy out. With Claude Code, you own the repository from the start. With a builder, it depends on the builder, and it is worth checking before you invest an evening: some keep your site inside their platform for as long as you pay, and there is no export button at all.
The practical reason to care is not ideology. A site built in one evening should not become a trap: when you eventually need something the tool cannot do, you want to hand a developer a working project instead of starting over.
What does it cost?
The Claude app and Claude Code follow Anthropic's own plans, which change over time, so check their pricing page. In Zugo, you get 1875 starting credits without a card. A typical build costs about 600 credits and an edit about 300; the word "about" is precise, because what you are charged is the model's actual work on your task. When the starting credits run out, Lite is $7 a month with 5000 credits and Pro is $25 a month with 20000 credits. Publishing to an address costs nothing extra, and your own domain is on a paid plan.
In short
Use the Claude app to see an idea, Claude Code to own a project, and an AI builder to get a site that works for people who are not you. The question that decides it is where the site lives: in a chat, in a folder, or at an address with your domain. Write the first message with the audience, the sections, real facts and clear limits, and check that you can take the code with you before you commit.