The short answer
An AI website builder reads what you tell it about the site, decides which sections and pages it needs, writes the copy, picks a design and produces a site you can edit and publish. Depending on the tool it assembles existing components, generates code, or combines the two. You then refine the draft by asking for changes, by editing directly, or both.
Apps rather than sites are covered in what is an AI app builder.
Assembling components or generating code
How a builder makes the first draft and how you edit it are separate questions.
- Assembling components. The AI arranges templates, sections and design components, then fills them with copy and images. What you can build depends on the components the platform has.
- Generating code. The AI writes the page structure, styling and behavior as code. Veloxa Build works this way and writes plain HTML, CSS and JavaScript files.
Either approach can offer conversational changes alongside direct editing. Check editing, hosting and code export separately: one does not guarantee the others.
What happens, step by step
Seven steps from the first sentence to a live address. The details vary by builder; the shape does not.
Step 1: You describe the site
A sentence or a paragraph, sometimes with attachments such as a logo, photos or your existing copy. The useful information is always the same: what the site is for, who it is for and which sections it needs.
Step 2: The model works out what you meant
A language model reads the description and infers what you did not say. “A site for a two-person landscaping business” implies services, a quote form, the area you cover and photos of past work. How to write a build prompt covers how to make this step go well.
Step 3: It produces the structure
Pages, sections and their order. A bakery site might need a menu, opening hours, a gallery and a contact section.
Step 4: It writes the copy and picks the design
Headings, body text and calls to action, plus placeholder details for anything you did not supply. A palette, type and spacing are chosen to fit the tone you described. Images come from the files you attached or from what the builder can generate or find.
Step 5: It loads the site in a preview
The pages load so you can see and use the site. Veloxa Build reloads the preview after every change and checks that the page runs; if it reports an error, the AI works on a fix before it finishes. Those fixes use AI usage like any other message.
Step 6: You review and change things
Ask for a change (“add a testimonials section”) or point at the exact element and say what should be different. Look at the site at phone and desktop widths as you go.
Step 7: You publish
Once you have checked the content, links, forms and phone layout, publish to a hosted address. Custom domains for Veloxa Build sites are coming soon (1 on Starter and 5 on Pro). Until then a published site lives at an address like yourname.veloxa.site, with HTTPS.
What the model is actually doing
The word “AI” covers a stack of ordinary parts. The one doing most of the work is a large language model given a long set of instructions about what a good website looks like: phone layouts first, readable contrast, one clear call to action, alt text on images, a sensible heading order. Those instructions are where a builder's opinions live.
Around the model sit the pieces that turn its output into a working site: file editing, a preview, error checking, version history and publishing.
Nothing in this stack understands your business. The model predicts what a good site for your description would contain. That is why it is strong on conventional sites, and why the details only you know (prices, hours, what you actually offer) are the things to supply rather than let it guess.
Refining the draft
The first version is a draft. In Veloxa Build you refine it in two ways.
- Describe the change. “Move testimonials above pricing and make the quote button stand out more.” Best for structural changes and anything that touches several parts of the site.
- Point at the element. Turn on click-to-edit in the preview toolbar, click the heading, card or button you mean, and describe the change. The AI gets the exact element, so you do not have to explain where it is.
Every AI message that changes your files saves a version, and restoring one is reversible, so an edit that makes things worse is easy to undo. The how it works page shows the whole loop.
How layouts adapt to phones
A responsive layout adapts one site to different screen sizes: cards in a row on a desktop stack on a phone, images shrink to fit, and navigation can fold into a menu. The builder writes those rules into its components or generated styles.
Check the result at both widths. Look for text that is too small, buttons that are hard to tap, images that overflow and forms that are awkward to fill in. Then ask for a specific correction, such as “stack the menu cards on phones and make the contact button full width”.
Where it falls short
Four limits show up again and again.
- Generic output. A first draft with no direction reads like every other first draft. Supply your real copy, your photos, your prices and a few words of tone.
- Made-up details. If you do not give it hours, prices or an address, the model invents plausible ones. Check every fact before publishing.
- Features the builder does not have. Veloxa Build has forms with an inbox, sign-in and per-user storage, but no payments, no booking calendar and no email sending to your visitors. Check what a platform really supports before you plan around it.
- Judging correctness. Whether a site works is checkable by clicking around. Whether it is secure, for anything sensitive, needs a person who can read the code.