Skip to content

Guides

AI Website Builder: Build a Site Without Coding

Learn how an AI website builder turns one plain-language prompt into a working site, then refine it in chat and publish it on your own domain. No code…

On this page
  1. What an AI website builder does
  2. How to choose an AI website builder
    1. AI website builder vs WordPress
  3. Step by step: build a site from one prompt
    1. Writing a prompt that gets a usable first version
    2. Adding your own content from files
  4. Refine, test and restore versions
    1. Make one change at a time
    2. Test every form, link and page
    3. Use version history to roll back
  5. Publish to a public URL or your own domain
    1. Publish to a public URL first
    2. Connect a custom domain
  6. Build it with FromScratch
  7. FAQ
Laptop screen showing a website preview, illustrating an AI website builder workflow
Photo by The Connected Narrative on Unsplash

An AI website builder turns a plain-language description into a working site. You say what the site is for, which pages it needs and what should be on them, and an AI agent generates the code, data layer and preview. This guide explains what these tools produce, how to choose one, and how to build a real example site from a single prompt, refine it in chat and publish it, all without writing code.

What an AI website builder does

An AI website builder takes a written description and produces a site you can open, click through and change. Instead of dragging blocks onto a canvas or picking a template, you write something like "a portfolio for a freelance photographer with a gallery and a contact form." An AI agent then decides on the structure, writes the code and sets up storage for anything that needs to be saved.

The output matters more than the interface. Some tools only assemble static pages from a template. FromScratch, for example, generates a React front-end, a Python (FastAPI) back-end and a database. That means a contact form can save messages, a gallery can read its images from a list you control, and login can be added later. A static template usually can't do those things without extra work.

Be realistic about the limits. The first version is a draft. You still need to check the text, test every form and link, and supply the real content: photos, prices, opening hours, legal notices. The builder speeds up the build, but it doesn't replace review. If you don't understand what you're asking for, you won't notice when the result is wrong. For a broader definition of the category, see What is an AI app builder.

How to choose an AI website builder

Most tools claim to be simple, so judge them on specific checks rather than marketing. Use this list before you commit time to any one of them.

A MacBook with lines of code on its screen on a busy desk
Photo by Christopher Gower on Unsplash
  1. Live preview. Can you see the site running within minutes of your first prompt? If you have to wait hours or export files to view anything, iteration will be slow.
  2. Refinement by chat. Can you change the site with plain requests such as "add a search bar" or "require login"? Check whether each change is applied to the existing site rather than forcing a full rebuild.
  3. Your own files. Can you attach PDFs, images or spreadsheets so the site uses your real content? A photographer's portfolio needs their photos, not stock images.
  4. Publishing. Can you publish to a public URL to share a draft, and connect your own custom domain when the site is ready for customers?
  5. Version history. Are changes saved, and can you restore an earlier version? This is the safety net that makes experimenting cheap.
  6. Store features, if you sell. If you plan to take payments, check whether the tool offers a catalog, cart and checkout, and whether payments go to your own payment account.

If you're weighing several options, No-code AI app builder: how to choose one covers deeper criteria. You can also compare pricing on the pricing page before you start.

AI website builder vs WordPress

WordPress is a mature content management system. You install it, pick a theme, add plugins and manage content yourself, and it works well for blogs and sites with many editors. An AI website builder works from the other direction: you describe the outcome and the tool generates the application. Choose WordPress if you want a familiar ecosystem of themes and plugins and are comfortable maintaining it. Choose an AI builder if your site needs custom behavior, such as a booking flow or a contact form that stores submissions in a database, and you'd rather describe that than assemble it from plugins. Many small teams end up needing one or the other depending on the project.

Step by step: build a site from one prompt

The fastest way to understand an AI website builder is to build something small. The example below is a freelance photographer's portfolio with four parts: a home page, a gallery, a services page and a contact form.

Writing a prompt that gets a usable first version

The prompt is the most important input you control. Vague prompts produce generic sites. A useful prompt names four things:

  • The site and its purpose. "A portfolio website for a freelance photographer" tells the builder who the site is for.
  • The pages. List each page and what it contains.
  • The functional parts. Say which things must be saved or processed, such as a contact form that stores messages.
  • The look. Give a few visual rules: colors, layout, density.

Compare two prompts. "Make a photography website" is too thin: the builder has to guess everything. "Build a portfolio for a freelance photographer with a home page that has a hero image and a short introduction, a gallery of attached photos, a services page with three packages and prices, and a contact form whose messages are saved to the database" gives the builder a structure to follow. You can keep the look rules short and refine them later.

Adding your own content from files

Generic placeholder text is the most common reason a first draft looks unfinished. Attach real files instead. For the photographer's site, that means the portfolio photos, a logo if there is one, and a spreadsheet or PDF with the three packages and their prices. Name the files in your prompt or in a follow-up message so the builder knows which content belongs on which page, for example "use the attached price sheet for the services page."

Check the first preview carefully against your source files. If a price is wrong or a photo is missing, correct it in chat right away rather than assuming it will fix itself.

Refine, test and restore versions

Once the first version is running, your job shifts from describing to editing. Work in small steps.

MacBook Pro on table beside white iMac and Magic Mouse
Photo by Domenico Loia on Unsplash

Make one change at a time

Send one request per message: "increase the spacing between gallery images," then "move the contact form to the bottom of the home page," then "change the accent color to a deep green." After each change, check the preview before moving on. If you bundle five changes together and something breaks, you won't know which one caused it.

Short requests work best for layout, copy and navigation. Long, multi-part requests increase the chance of a partial result.

Before you share the site, click through every page on both a phone-sized and a desktop-sized window. Submit the contact form with a test message and confirm that it appears where you expect. Click every menu item and every link to the services page. A portfolio can look finished while a button leads to a blank page, and visitors will notice before you do.

Use version history to roll back

Every change is saved, so when something breaks you can restore an earlier version instead of trying to undo it by hand. Use this freely. Experiment with a new layout, and if it's worse, go back. It also helps to keep a short written log: "Version 3: added gallery filter; Version 4: changed accent color; Version 5: fixed contact form." That log becomes invaluable when you need to explain a change or find the moment a bug appeared.

Publish to a public URL or your own domain

Publishing is a two-stage process. First, share a draft to check how it looks outside your own preview. Second, connect your own domain once the site is ready for real visitors.

Publish to a public URL first

Publish with one click to get a public URL. Send it to a colleague or a friend and ask them to try the contact form and open the gallery on a phone. A fresh pair of eyes will catch wording and layout problems that you've stopped seeing.

Connect a custom domain

When the site is ready for clients, connect a custom domain so the address matches your brand. This is also the usual answer to the question of how to publish a website built with AI on a custom domain: publish first, then point your domain to the published site through the steps the builder provides. Check the domain's status before announcing it, and allow time for changes to take effect.

Re-check every page after publishing. Forms can behave differently on a live address, and contact details, phone numbers and legal text are easy to leave outdated. If you're planning a larger project, such as a client portal, How to build a client portal without code walks through a related workflow.

Build it with FromScratch

FromScratch is an AI app builder. You describe the site in plain language and it builds the front-end, the back-end and the database. Here is how to build the photographer's portfolio step by step.

  1. Create a free account and start a new project.
  2. Paste the prompt below into the chat. Name the site if you have a name for it.
  3. Wait for the live preview. Review the home page, gallery, services page and contact form against the list you wrote.
  4. Attach your real files: the photos, the logo and the price sheet. Tell the builder which file goes where.
  5. Send one refinement at a time. Start with the largest visible problem, such as the wrong hero image, then move to spacing and copy.
  6. Submit a test message through the contact form and confirm it is saved.
  7. Publish to a public URL, share it for feedback, then connect your own domain when you're ready.

The free plan lets you start building. Paid plans add credits and projects, and you can see the details on the pricing page. If you'd rather begin from a related example, you can use the blank prompt or open a guide such as How to build an internal tool with AI. For a side-by-side view of how FromScratch compares with other builders, see FromScratch vs Lovable vs Bolt.

Use this prompt as your starting point:

Build a simple portfolio website for a freelance photographer. It needs a home page with a hero image and a short introduction, a gallery page showing the photos I attach, a services page with three packages and their prices, and a contact form whose messages are saved to the database. Use a clean, minimal design with a white background and one accent color.

FAQ

Do I need to know how to code to use an AI website builder?

No, you don't need to write code to build a site with an AI website builder. You do need to check the result, test the forms and links, and understand what you're asking for. If you can describe the site clearly and compare the preview against your own notes, you can get a working draft.

Can I use my own domain?

Yes. You can publish the site to a public URL first, then connect a custom domain once it's ready for visitors. Re-check every page after you connect the domain, because forms and contact details are easy to leave out of date.

Can I undo a change?

Yes. Every change is saved, and you can restore an earlier version whenever a change breaks something. Keeping a short written log of what each version changed makes it much easier to find the right one.

Do I need a store to sell?

Only if you plan to sell products online. FromScratch offers e-commerce stores with a product catalog, cart and checkout, and card payments go through your own Stripe account. You can also import products from an existing Shopify or WooCommerce store. A portfolio like the photographer's example doesn't need a store at all.

Written by

FromScratch TeamEditorial team

The team building FromScratch, the AI app builder that turns a plain-language description into a real, published full-stack app.