Design Versions and History

Why versions

Designing on a chat-to-design canvas is exploratory by nature — you try one direction, then another, then circle back to an idea from before. Versions make that exploration safe: you capture the state of your design at any moment, so you can always return to a good point.

Instead of hesitating before asking for a bold change, you snapshot first, then experiment freely. If it doesn't work out, you restore the snapshot as if nothing happened.

Snapshotting

A snapshot is a saved state of a page at a point in time — its layout, content, and the style applied to it. Take a snapshot whenever you reach a result you want to keep before going off to try something new.

Reach a good state

Iterate by conversation and direct editing until the page is in a state you'd want to be able to return to.

Capture the snapshot

Save the current state as a version. Give it a descriptive name ("calmer hero," "dark palette") so it's easy to recognise later in the history.

Keep experimenting

With a safe snapshot in the history, ask for bigger changes confidently. Each later meaningful iteration can become its own snapshot too.

💡

Tip.Snapshot before any risky change — a full restyle or a drastic layout rework. A snapshot is far cheaper than rebuilding good work you've lost.

Comparing iterations

Often the real question isn't "is this good?" but "which is better?" The history lets you put two iterations side by side, so you can see the differences in layout, style, and content directly rather than relying on memory.

Comparison is especially useful after trying several Design DNA restyles: capture each direction as a snapshot, then view them together to decide which system to commit to.

Open the history

Open the version history for the page you're working on. It lists each saved snapshot in chronological order with its name.

Pick two versions

Choose the two snapshots you want to compare — like the current state and an earlier version, or two different restyles.

Review the differences

View them side by side on the canvas to judge which serves the audience and purpose better before restoring.

Restoring

When you decide an earlier version was better, restore it. The page on the canvas returns to exactly that saved state — its layout, content, and style — so you can continue from there.

Restoring is not a dead end. Your most recent work remains in the history as its own snapshot, so even if you restore an older version and then change your mind, you can move forward again.

ℹ

Note.A restore applies to the page you selected. Other pages on the canvas are unaffected — each one has its own history (see the next section).

History per page

Each page on the canvas keeps its own independent version history. This means you can experiment boldly on a landing page without risking the polished pricing page beside it, and restore each one separately.

Because each page has its own history, one page's versions never get tangled with another's. You navigate to a page, open its history, and see only that screen's snapshots.

💡

Tip.When working across a multi-page flow, snapshot each page that reaches a good state before a system-level restyle. Then you can compare each page before and after the new look.

A suggested workflow

Capture starting points

As soon as the assistant builds a sensible first pass of a page, snapshot it. You now have a safe fallback before any refinement.

Branch before big changes

Before a restyle or a major restructure, take another snapshot. Try the bold direction knowing the prior state is preserved.

Compare, then commit

When you have a few strong directions, compare them side by side, restore the favourite, and keep building on it.

Export with confidence

Once you've settled on a version, you can turn the design into a real Web App knowing every good iteration is still safe in the history.

Next steps

Chat to a design→Style & Design DNA→Design to Web App→

← Back to Guide