Skip to content

How Version History Works

Every generation and refinement is kept, so you can always go back to the version that worked.

Recently updated
On this page

Version history keeps each state your design has passed through — the first generation, every refinement, and every layer change — so an experiment never costs you a design you already liked.

Overview

Each time you generate or refine, the Studio records a new version rather than overwriting the previous one. The chain is linear: newest at the top, original at the bottom.

Restoring a version makes it the active design again. Later versions are not deleted; you are moving the pointer, not erasing history.

This is what makes aggressive experimentation safe. You can try a bold refinement knowing the previous state is one click away.

Why this matters

Iteration only works if going backwards is free. Without history, every refinement is a gamble and people stop experimenting — which is exactly when designs stop improving.

It also settles the most common frustration in AI design: "the third one was the best and now it's gone". With version history, it is not gone.

Step-by-step guide

  1. Step 1: Open your design in the Studio

    Version history is attached to the design, not to your session, so it is there when you come back.

  2. Step 2: Open the history list

    Versions are listed newest first with the change that produced each one.

  3. Step 3: Preview before restoring

    Compare a candidate version against the current design so you restore the right one.

  4. Step 4: Restore the version you want

    It becomes the active design and further refinements continue from there.

  5. Step 5: Branch deliberately

    Restore an earlier version, then refine differently to explore a second direction from the same starting point.

  6. Step 6: Save what you want to keep

    Designs you want to keep long term belong in My Designs.

Best practices

  • Restore early rather than refining your way out of a bad direction.
  • Before an experimental refinement, note which version you are on.
  • Use restore-then-refine to explore two directions from one strong base.
  • Keep the number of speculative refinements low so history stays readable.

Common mistakes

MistakeWhy it happensWhat to do instead
Refining repeatedly to get back to an earlier lookRefinement moves forward, never backward.Restore the earlier version directly.
Starting over when a design goes wrongIt discards a good base along with the bad change.Roll back one version and take a different path.
Assuming restoring deletes later versionsIt looks like an undo.It is a pointer move — later versions remain in the list.

Frequently asked questions

How long is version history kept?

History lives with the saved design. Storage behaviour is described in Design Storage.

Does restoring a version cost credits?

No. Only generating and refining consume credits.

Can I restore a design I deleted?

See Deleted Design Returned and Starting Over and Restoring Designs.

Do layer changes create versions?

Yes — layer edits are part of the design state and are recorded alongside generations.

Can I compare two versions side by side?

Preview a version before restoring it to compare it against the current design.

Is history shared when I share a design?

Sharing publishes the design, not your working history. See Share a Design.

Need more help?

Was this helpful?

Last updated: August 4, 2026Documentation version: 1.0