> ## Documentation Index
> Fetch the complete documentation index at: https://docs.foundable.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Version history
> Every change Ted saves is a version. Look at any earlier version, bookmark the good ones, and put your website back the way it was.
Every time Ted saves a change to your website, Build keeps it as a version. There’s no save button, and nothing is thrown away. History lists every version, newest first, so you can look at any of them and put your website back the way it was.
Open your website in Build and press the clock (**Show history**) at the top. History opens where the chat was. On a phone, press **More actions**, then **History**.
Press any version. The preview shows your website as it was then, and the top says when that version was saved. Press **Back to latest** to return.
Press **Revert to this version**, at the top or on the version’s row. Build asks “Revert to this version?”. Press **Revert**.
Reverting changes your website in Build. Visitors see it once you [publish an update](/build/publish#update-your-live-website).
## What you’ll see in History
Versions are grouped by day. Each one has a title that says what changed:
* Ted’s own summary of a change he built, like “Changed the opening hours”.
* “Visual edit”, for words you changed yourself with [Edit text](/build/preview-and-edit#edit-text).
* “Reverted to” and a version’s title, for a revert.
* “Duplicated from” and a website’s name, for a [copy](/build/overview#rename-duplicate-or-delete-a-website).
* “Undid a text change the website couldn’t build”, when Build put your old words back.
* The first line of a commit, for a change that came from [GitHub](/build/github).
| On a row | What it means |
| - | - |
| “Latest” | The version you see in Build now. |
| “● Published” | The version visitors see on your live website. |
| Bookmark (**Bookmark in history**) | Saves the version under **Bookmarks**. Press it again (**Remove bookmark**) to take it off. |
| ⋮ (**Version actions**) | **Open preview in new tab** shows that version in its own tab. **Go to message in chat** takes you to the message that made it. |
| **Revert to this version** | Puts your website back to this version. It’s greyed out on Latest: “Cannot revert to the current version”. |
To see older versions, press **Load more versions** at the bottom of the list.
## Revert to an earlier version
Reverting doesn’t delete anything. Build saves a copy of the version you picked as your newest version, and every other version stays in History.
The question tells you when the version is from: “This will revert your website to how it looked on…”. Changes you made after that point stay in the chat, so you can ask Ted to make them again anytime. Press **Revert** to go ahead, or press Esc to cancel. You’ll see “Reverting…” while it works.
The copy becomes Latest, with **Undo** on its row. Changed your mind? Press **Undo** to go back to where you were.
Your live website stays as it was until you publish an update.
Before a big change, like a new design, bookmark the version you have. If you don’t like the result, it’s right there under **Bookmarks**.
## Go back from the chat
You can also go back right from the chat. Under Ted’s reply that saved your newest change, press **Undo latest edit** to take that change back. Under an earlier reply, press **Revert to this version** to put your website back the way that reply left it. You’ll see “Reverted to message”: “Your website has been successfully reverted to this message.”
The replies you went back past fold into “Reverted messages”. Press **Show** to see them again.
To try a different request from an earlier point, press **Edit message** on your own message, change the words and press **Revert and resend**. Your website goes back to that point, and the chat continues from your new message.
## Bookmarks
Bookmark the versions you want to find again, like the one you’re happy with. Press the bookmark on a version’s row in History, or **Bookmark in history** on Ted’s build card in the chat. Your bookmarks are in History’s **Bookmarks** tab. Until you add one, it says “No bookmarks yet”.
## If you can’t go back
| What you see | What it means | What to do |
| - | - | - |
| “Ted is working on this website. Revert once he’s done.” | Ted is changing this website now. | Wait until he finishes, then try again. |
| “A newer version was just saved. Try again.” | A change was saved while you were deciding. | Check History again, then revert. |
| “Another change to this website is still saving. Try again in a moment.” | A change is still on its way. | Wait a moment, then try again. |
| “Newer changes were saved, so this can’t be undone.” | Something changed after that reply. | Open History and revert to the version you want. |
| “There’s no earlier version to go back to.” | That change made the first version. | Nothing to undo. Ask Ted for the change you want instead. |
| “Couldn’t revert. Try again.” | The revert didn’t go through. | Try again. |
| “This version doesn’t build” | “Its code has errors, so it can’t be previewed.” | Pick another version, or ask Ted to fix it. |
## Who can do it
Everyone in your foundable can look at History. The owner, admins and members can revert, undo and bookmark. A teammate with view-only access can only look.
## FAQ
Not by itself. Reverting changes your website in Build. Your live website changes when you [publish an update](/build/publish#update-your-live-website).
No. Every version stays in History, including the ones after the version you went back to. Those changes also stay in the chat.
All the way to your website’s first version. Every version stays in History.
The one marked “● Published”. If a newer version is Latest, visitors see it once you publish an update.
## Related
Check a version page by page.
Send the version you want live.
Ask for changes and follow Ted’s work.
Keep your website’s code in GitHub.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.