Put a website made with Claude online: step by step

You put a website made with Claude on your own domain by getting the files out of Claude and placing them with a hosting provider. It starts with one question: do you have a page from the Claude app, or a project from Claude Code? The first is a single file or a zip, the second a folder with a build. You can put both on your own domain through hosting for Claude websites, they just need a slightly different approach.

Which Claude did you use?

The Claude app. You ask in the chat for a page, and it appears as an artifact next to the conversation. With Claude Design you also make designs on a canvas. What comes out is a single page or a set of pages, not a program with a server.

Claude Code. This is the version for your terminal or editor. Claude then works in a folder on your computer, can run commands and builds a complete project. What you get depends on what you ask for. There is no fixed stack.

No idea which one you used? If the page exists only in the chat, it is the app. If you have a folder of files on your computer that Claude worked in, it is Claude Code.

A page or design from the Claude app

You can share an artifact in two ways. With the publish option you get a public link hosted by Claude. Handy for showing something, but it is an address of Claude and not of yours. You cannot connect your own domain to it. For your own domain you need the code itself.

This is how you get it out:

• An artifact. Open the panel with the page and look for the buttons to view, copy or download the code. If you copy the code, put it in a new file called index.html.
• A Claude Design project. At the top right there is an Export button. Under it you will find, among others, “Download as .zip” and “Export as standalone HTML”. The standalone version is a single file with everything in it, the zip contains the separate files.

Then open the file by double-clicking it. If it looks in your browser just like it did in Claude, it works.

One thing to know: artifacts may only load scripts and fonts from a number of known addresses, such as cdnjs, jsDelivr, unpkg and Google Fonts. Because of that, such a file usually works on ordinary hosting without changes. Parts that use the Claude environment itself, such as a built-in call to Claude, do not move to another place. A form that lets your visitors send a message also needs something extra, see a contact form on your AI website.

A project from Claude Code

With Claude Code you decide the outcome with your instruction. So ask explicitly for a static site. A useful instruction:

Turn this into a static website that I can put on ordinary hosting.
No server, no database. Make sure npm run build creates a dist folder
with an index.html in the main folder.

If Claude uses Next.js, ask for a static export with output: 'export'. The output then lands in the out folder. With Vite and Astro the folder is usually called dist.

Then run this in the project folder:

npm install
npm run build

The contents of the output folder are your website. So do not upload the whole project folder with node_modules, src and package.json, only what comes out of the build. You can read more about what such a project looks like and what to check in hosting a React or Vite website without a Node server.

Does Claude ask for a Node server, a database or server-side rendering? Then this is no longer a loose set of files. Such a project fits a custom offer: send us a WhatsApp message with what you built and we will work out together what is needed.

Checklist before you upload

Go through these points. It takes five minutes and prevents a site that looks fine locally and not online.

1. index.html in the main folder. The home page must sit directly in the folder you upload, not in a subfolder such as dist/dist or my-site/.
2. Relative paths or a correct base. If an image points to /assets/photo.jpg, that works on your own domain. In a subfolder it does not. In Vite the base setting defaults to /, which suits a domain.
3. No secrets in the files. Search your code for keys, passwords and tokens. Whatever is in a build with the prefix VITE_ can be read by anyone in the browser. An API key does not belong there.
4. All files present. Images, fonts and stylesheets sit next to index.html or in a subfolder that comes along.
5. Several pages in React. If your site has routes such as /about-us that are handled in the browser, the server must send unknown addresses to index.html. That applies to every host. With us it is a setting that we switch on for you on request, a WhatsApp message is enough.

Putting it online on your own domain

Now you have a folder that is ready. There are two ways.

Upload it yourself. You use SFTP with a free program such as FileZilla or Cyberduck. The login details are in your portal (My account) under Files. Drag the contents of your folder to the main folder of your site. After that your site is online.

We do it. Send us the zip or a GitHub link and we put it online as part of the free migration. More about zip and GitHub is in exporting an AI website as a zip or GitHub.

After that you connect your domain. You get two nameservers from us, which you enter once at your registrar. The step-by-step guide is in connecting a domain name to your AI website. If another site is already on that domain, it stays online until you change the nameservers.

The site sits behind Cloudflare, SSL is included and there is a backup every day that you can restore in your portal under Backup and restore. The Website plan costs € 9 per month, or € 90 per year. You order it through the order form.

Do you want Claude to change or add files itself later? That is possible with your own Claude through MCP, without having to upload again every time. The overview of all routes is in putting a website from AI online.