--- title: "Version history" description: "Save your guidelines, compare changes, restore an earlier version, and choose when updates reach your AI tools." label: "Version history" date: "2026-08-11" --- Version history keeps saved versions of a brand. You can save one at any point, compare two to see exactly what moved, restore an earlier one, and choose which version your connected apps receive. Version history is a paid feature. If it is not on your plan, the page tells you so. See [Plans](/docs/billing/plans) for what each plan includes. ## What a version covers Versions are kept per scope. The picker at the top of the page chooses what the page is about: - **Everything**: the brand layer and every project, on one timeline. - **The brand layer** on its own. - **One project**: that project's overrides on their own. Beside each scope the page says where live authoring stands: **Never saved**, **Unsaved changes**, or the version it currently matches. Everything shows **All saved** only when every part is. ## Save a version **Save a version** takes the chosen scope as it stands right now and stores it under a name you give it, with an optional note. Nothing about the live brand changes, so saving is always safe. On Everything, **Save a version of everything** saves the brand layer and every project together, in one go, under one note. A scope that has not changed since its last version is skipped rather than saved again. If nothing at all has changed, the page tells you so and saves nothing. Save a version before a large edit, at the end of a round of work, or whenever you want a point you can name and come back to. ## Automatic versions Before every restore, UI Rules saves a version of where you were automatically, so the restore can be undone. These carry an **Auto-saved** badge and are hidden by default, because a scope with a few restores behind it would bury every deliberate save under them. **Show N saved automatically** brings them back into the list. Every row also says how it came to exist: saved on its own, saved with everything, saved alongside a project version, or saved automatically before a restore. ## Choose when your AI tools receive changes By default, your connected AI tools use your latest guidelines and styles. The app calls this **Live**. You can also keep a project using a saved version while you work on changes. For example, your website can keep using your existing colors while you explore a new palette in UI Rules. Your AI tools keep receiving the saved colors until you choose to share the new ones. In Version history, choose **Deliver this version** on the saved version you want that project to use. Choose **Go back to Live** when you want its AI tools to use your latest changes again. The saved version remains available either way. ## Compare two versions A comparison lists every difference between two versions, grouped by what happened rather than by where it happened: - **Added** and **Deleted**, for things that appeared or went. - **Edited**, for something changed in place. These rows open so you can see both versions. - **Overridden** and **Override removed**, for project overrides laid on or taken off. - **Hidden** and **Shown again**, for changes to what a project can see. Rows are filed by what they affect: components, blocks, rules, token values, links, [modifiers and contexts](/docs/styles/overview#modifiers-and-contexts), and visibility settings. ## Restore an earlier version ### Pick the version Open the version you want to go back to. Comparing it against Live first is a good way to confirm it is the one you mean. ### Choose what to restore You can bring back the whole version or narrow it to part of the brand. ### Restore it The brand returns to that state. Restoring is reversible. Where you are now is saved first as an automatic version if it is not already saved, so it stays in the list and you can restore it to undo the restore. ## Related Every change to the brand, and who made it. Restore something you deleted.