Skip to content
Wixy

AI design

Type what you want to change and see it before you publish

“Dark background on the hero, title on the left, big image on the right and the main button in yellow.” That’s all you have to write. A model writes your theme’s code, a preview is built, and you decide: publish, keep editing or discard. Your published site isn’t touched until you say so.

Start freeHow versions work

Step by step

From the sentence you type to the published site

Four steps, always the same ones, whoever asks for the change. Between the second and the fourth there’s nothing to approve by hand: the platform checks what the model wrote on its own.

  1. You pick what changes

    One section, one page or the whole site. The scope decides what the model gets: sending the whole project to move one button is expensive, slow and risky.

    this section · this page · whole site

  2. You describe it in your own words

    No file names, no code, no technical terms. Before anyone is called, the cost is estimated and the credits are reserved; if your balance falls short you’re told how much is missing instead of calling and failing.

    “the main button in yellow” · ~1 credit

  3. The platform checks what came back

    Which files it touches, whether it wrote your text into the code, and whether it actually compiles, inside an isolated container with no network. What doesn’t pass never gets built.

    paths · content separation · build

  4. You look at the preview and decide

    The version is served on its own address, outside your domain and not indexed. You decide there, with time, and whatever you decide is written down with your name and the date.

    discard · keep editing · publish

If validation fails twice, the change is discarded on its own and every credit is refunded. Half a component is never saved, and your published site stays exactly as it was.

The scopes

You pick how much gets touched. The platform watches the rest.

The more context a model receives, the more likely it is to change something nobody asked for. So every request starts by deciding what’s in play, and the price follows from that.

  • This section

    “The main button in yellow.” The model gets that block’s component, your colors and typefaces, and the data contract. It touches that file and, at most, one new helper. Estimate: around 1 credit.

  • This page

    “Move the form to the top and the map to the bottom.” It gets the components for that page’s blocks and its layout. It changes those files and no others: the contact page can’t alter the home page. Estimate: around 3 credits.

  • Whole site

    “Give the whole site a more serious look.” By default that means colors, typefaces, spacing and corner radii: two files instead of forty, and the change shows on every page at once. If it needs more, it goes block by block and you watch the progress. Estimate: around 5 credits.

  • What the model receives

    Each block’s data contract (which fields exist and what type they are), your colors, the accessibility and animation rules, and the exact list of files it may touch. Your content travels separately, marked as data.

  • What it can’t do, even if you ask

    It doesn’t create fields or content types: if a design needs data that doesn’t exist, it tells you instead of inventing it. It doesn’t upload images or link photos from another site: images come from your library. And it doesn’t install a single dependency.

  • Content doesn’t cost credits

    Type “change the title to Industrial Solutions” and the panel answers “that’s changed in Pages” with the link ready. No model is called, nothing is charged, and the change takes you ten seconds.

The proof

Your content never ends up inside the code

The model sees each field’s type, not your text. It can change how the title is drawn — size, color, position, animation — but the component has to keep reading the field. A validator compares every literal in the generated code against your real content and rejects any match. It isn’t a line in the prompt: it’s platform code, and it runs every time.

  • If it writes your title into the component, it’s rejected

    And so is a component that stops reading a field it used to read. The version isn’t saved, you’re told what happened, and you aren’t charged.

  • Change a price in the panel and the site shows it

    Nothing to regenerate, nothing to ask the model, not one credit spent. That’s the difference between a CMS and a pile of loose pages.

  • Your checkout and your SEO are out of reach

    No prompt reaches the commerce folder or the system folder, and it isn’t a box anyone can uncheck. It’s checked when the version is created and again before it compiles.

How a page is composed with blocks
bloques/Hero.astro

change «the button in yellow»

<section class="bg-white">
<h1 class="text-4xl text-center">
{pagina.titulo}
</h1>
<a
href= {bloque.boton.href}
before: class="bg-blue-600 text-white"
after: class="bg-yellow-400 text-black"
>
{bloque.boton.texto}
</a>
</section>
before after {pagina.titulo} content: untouched

After generating

Every generation is a version. The published one isn’t touched until you say so.

The preview has its own address, doesn’t show up in Google and opens behind a signed link that expires. It uses the same mechanism as your real site, because a preview built differently proves nothing. And the version stores the prompt, the scope, the model and what it cost: six months later you still know what you asked for and what you paid.

  • “Keep editing” starts from the version just generated, not from the published one.
  • Discarding deletes nothing: the version stays in the history and stops being the head.
  • If your team saved another version while the model was writing, yours isn’t lost: you’re warned and you compare.

How versions work

Version history v18 – v21

Every version can be previewed, compared and restored.

  1. v21 You · AI You added testimonials published
    2 hours ago
  2. v20 Team Mobile responsive
    yesterday
  3. v19 You · AI You changed the hero
    3 days ago
  4. v18 Team Initial design
    2 weeks ago

If something goes wrong

A model’s mistake isn’t on your bill

If the change fails validation, if it touches something it shouldn’t, if the model declines or if the answer is cut off halfway, nothing is applied and every credit comes back. We take the cost: if the model tried something it isn’t allowed to do, we’re the ones who need to tune the prompt.

See plans and credits How your site is protected

Questions

What people ask before their first change

What happens if the AI gets it wrong?

It never reaches your site. What the model returns is validated before it’s built; if it fails, a correction is requested with the error in front of it, and if it fails again, it’s discarded. In that case every credit is refunded: a failure on our side isn’t on your bill. And if something doesn’t convince you after publishing, you go back to the previous version in seconds.

Can the AI touch my checkout or my SEO?

No, and it isn’t a box you can uncheck. The commerce folder and the system folder, where the <head> with your SEO and the form submissions live, are on a blocklist written into the platform’s code, above any setting. It’s checked twice: when the version is created and again before it compiles. If a prompt tries to touch them, that part isn’t applied, you’re told what was done and what wasn’t, and nothing is charged.

What is a credit, and what does a change cost?

A credit is the unit that measures what the model consumes. Before the call, the cost is estimated and reserved; afterward you’re charged for what was actually used and the difference is returned. As an estimate: “the main button in yellow” is around 1 credit; “move the form to the top and the map to the bottom”, about 3; “give the whole site a more serious look”, about 5. The cost of every change is written next to its version, in the history.

Do I need to know how to code?

No. You type what you want in your own words and review the result in a preview. The code exists so your team or ours can open it, read it and fix it, and so every change can be compared and rolled back. You never have to look at it if you don’t want to. And we never ask you for an API key or hand you one: the model’s credentials are ours, and what you use is measured in credits.

Can I ask it to change a text or a price?

You can ask, but that isn’t design: it’s content, and it’s changed in Pages, Posts or Products without spending a credit. If you type “change the title to…”, the panel replies with a link to the right place and doesn’t call the model. AI design changes how your content looks, not what it says.

Who can ask for design changes in my account?

Only the people you authorize. Every user has their own design permission: none, propose (generate, look at the preview and request publication) or publish. Writers don’t have it by default, and granting it to someone is an action of yours that’s logged. Depending on the plan, publishing may go through our team’s review first.

What happens when I run out of credits?

Your published site stays published, the history and the preview are still there, and the SEO analysis with its score keeps working because it costs nothing. Only generation stops. You’re warned at 80% and at 100% of the cycle, and you can upgrade whenever you want. Plan credits renew every month; purchased credits don’t expire.

Your first change takes one sentence and one minute

The Free plan comes with a site at yourname.wixy.app, blocks, forms, SEO and 50 credits a month. Forever, and no card needed.

Start freeTalk to the team