Version history
Every change you make to your website is automatically saved. Version History lets you travel back in time, compare different versions, and restore your project to any previous state.
Every change you make to your website is automatically saved. Version History lets you travel back in time, compare different versions, and restore your project to any previous state.
Why Version History Matters
- Safety net: Never lose your work, even if you make a mistake
- Experimentation: Try bold changes knowing you can always go back
- Comparison: See how your website evolved over time
- Recovery: Restore accidentally deleted content
Accessing Version History
- Open your project in the chat
- Look for the History icon in the top toolbar
- Click it to open the Version History panel
Understanding Versions
Each version represents a snapshot of your website at a specific point in time.
Version Information
Each version shows:
- Version number - Sequential number (v1, v2, v3...)
- Timestamp - When the version was created
- Preview - Thumbnail of how the site looked
Automatic Versioning
New versions are created automatically when:
- The AI completes building your initial website
- The AI finishes making requested changes
- You save changes from the code editor
Using Version History
Viewing a Version
- Click on any version in the history list
- The preview panel will show that version
- Browse the site as it was at that point
Comparing Versions
To see what changed between versions:
- Select the version you want to compare
- Look at the preview to see differences
- Compare with the current version
Restoring a Version
Want to go back to an earlier version?
- Find the version you want to restore
- Click the Restore button
- Confirm your choice
Version History Best Practices
Create Checkpoints
Before making major changes, you can ask the AI:
"I'm about to request some big changes. Let me know when you're ready so I can use the current version as a checkpoint."
Review Before Major Changes
Before requesting significant modifications:
- Open Version History
- Note the current version number
- Make your changes
- If unhappy, restore the noted version
Don't Hoard Versions
While history is preserved, it's good practice to finalize designs rather than keeping dozens of experimental versions.
Common Scenarios
Scenario 1: Experimented Too Much
You requested many changes and the website looks worse than before.
- Open Version History
- Find a version you were happy with
- Click Restore
- Start fresh with more targeted changes
Scenario 2: Client Changed Their Mind
Your client approved a design, then wanted to go back to an earlier concept.
- Find the version with the earlier design
- Restore it
- Continue from that point
Scenario 3: Accidentally Deleted Something
You asked the AI to remove a section, then realized you needed it.
- Find a version before the deletion
- Restore it, or
- Ask the AI to add the section back (it remembers what was there)
Version Limits
- All versions are kept for the lifetime of your project
- Versions are associated with conversations
- Deleted projects will have their version history removed
Tips
Before Publishing
Always review a few recent versions to make sure you're publishing the best iteration.
Team Collaboration
If working with others, version history helps you track who made what changes and when.
Learning from History
Look back at earlier versions to see how your website evolved – it can inform future design decisions.