--- title: "Versions, undo and redo | Briks" url: https://briks.dev/docs/versions description: "Every build and change is saved as a version of your site. Undo a change, redo it, or put any earlier version back live exactly as it was, with no credits held." last_updated: 2026-10-08 --- # Versions, undo and redo Briks saves every version of your site it publishes. If a change goes wrong, or you preferred last week's hero, you can step back, step forward again, or put any saved version back live exactly as it was. Nothing is rebuilt, so going back holds no credits. 6 minute read Checked against the studio on 8 October 2026 ## What a version is A version is the site as it was published at one moment: its pages, words, pictures and code. Each one gets a number (v1, v2, v3 and so on), and the one visitors see is the live version. New versions come from: - the first build; - every change you ask for in the conversation; - code you save and publish in the File Explorer; - changes you publish from the [Visual Editor](https://briks.dev/docs/visual-editor); - a picture or video swapped with **Replace** on the **Media** tab; - publishing again with new settings, for example with **Apply to the live site** or by going to production; - a repair published after the site was checked again, marked **Repaired**. Some things aren't part of a version, so they stay as they are when you go back: form messages, analytics, your own domains, files in Storage and the records in the site's database. ## Finding your versions Above the preview, beside the width buttons, are an undo arrow, a redo arrow and a clock icon showing the live version's number, such as **v7**. Click the clock to open **Versions**. Where 1. Projects 2. Your project 3. Studio 4. Versions | In the list | What it means | | --- | --- | | **v12** | The version's number. Higher is newer. | | **First build**, **Change** or **Published again** | What made it. **Published again** is a republish with the site's settings, for example after **Apply to the live site** or going to production. | | **Repaired** | Published after the site was checked again and broken rendering was mended. | | 3 h ago | When it was saved. Older versions show the date. | | **92/100** | The visual check's score, when that version was checked. | | **Live** | The version visitors see now. | | The line underneath | What was asked for, or what changed. | | Since version 12 … | Did the change help: for a version at least a week old, the visits and enquiries of the pages it changed, a week's average, in the two weeks before it was published and after (or until the next version). A change an agent asked for is named as that agent's. It is an everyday read, not proof: to be sure, test the version against the one before. With fewer than 25 visits a week to those pages it says there are too few to say. | Versions show up in four places, each with a slightly different view: | Where | What it lists | What you can do | | --- | --- | --- | | **Versions**, above the preview | The latest 100, with what made each and its check score | **Make live**, **Test against live** | | **Settings**, **Versions** | The latest 100, with who asked for each and when | **Restore** | | **Settings**, **Backups** | Up to 200, with who made each | **Restore**, and **Download** its code on a paid plan | | **History** in the [Visual Editor](https://briks.dev/docs/visual-editor) | The site's versions beside the page | **Preview** one as it was published, **Restore** | ## Undo a change 1. Let any build finish Where: Studio Undo is greyed out while anything is running on the site. 2. Press the undo arrow Where: Preview toolbar Hover first: the tooltip names the version it goes back to, such as “Undo to version 11”. 3. Watch it publish Where: Studio The conversation shows a single **Publishing** step. Nothing is designed or built again. 4. Check the result Where: Preview Briks replies “Version 11 is live again, exactly as it was published.” If the site's settings have changed since (production or preview, or a domain that went live), it is published again with the settings as they stand now, and the reply says so. The preview reloads and the clock reads **v11**. Undo goes back to the version the live one was made from. Press it again to keep stepping back. Undo Garden centre > Live was v9, a darker header the owner had just asked for. On phones it looked heavy, so they pressed undo. v8 went back live exactly as before. v9 stayed in the list, ready if they changed their mind. ## Redo After an undo, the redo arrow takes you forward again, to the newest version made from the one that's live. 1. Press the redo arrow Where: Preview toolbar The tooltip names the version, such as “Redo to version 9”. If it says “Nothing to redo”, no newer version was made from the live one. 2. Wait for the publish Where: Studio As with undo: one **Publishing** step, then a reply naming the version that's live. Redo after a new change If you undo and then ask for a new change, that change is made from the version you went back to, and redo now leads to it. The versions you stepped back from aren't lost: open **Versions** and press **Make live** on any of them. Branching Bookshop > Live was v6. The owner pressed undo twice, back to v4, then asked for a new banner. That became v7, made from v4. From v4, redo now goes to v7. v5 and v6 are still listed, and **Make live** puts either back. ## Put any version back live 1. Open Versions Where: Preview toolbar Click the clock icon above the preview. 2. Find the version Where: Versions Read the line under each one and the time it was saved. 3. Press Make live Where: Versions It's on every version except the live one. The panel closes and the publish starts. 4. Check it Where: Preview When the reply says the version is live again, look it over at each width. You can do the same from **Settings**, **Versions** or **Settings**, **Backups**, where each row has a **Restore** button. It asks first, “Restore version 4?”, and adds that the versions after it stay saved, so you can come back. Where 1. Settings 2. Backups 3. Restore ## What happens when you go back - The saved version is published again exactly as it was. No new version is made: the **Live** marker moves to the one you chose. - Nothing is held or charged, because nothing is designed or built. - Your next change starts from whichever version is live. - Form messages, analytics, domains, Storage files and database records are left as they are. Make undo easy for yourself Send a big or risky change on its own, so undoing it takes nothing else with it. When you save code in the File Explorer, add a note: it becomes the line under that version, so the list explains itself months later. Database records don't go back If your site stores data, going back changes the pages and code, not the records. Anything you or your visitors added since stays where it is. ## Who can use versions, and when Anyone with edit rights (Editors, Admins and Owners) can undo, redo and make a version live. Viewers can open the list and read it. Versions are locked at two times: - while anything is building or publishing on the site: “Something is already running on this site. Wait for it to finish.”; - while an A/B test runs. The panel says “A test is running. End it by keeping one version before restoring another.” See [A/B tests](https://briks.dev/docs/ab-tests). ### Does undo cost credits? No. Undo, redo and **Make live** hold no credits, because they publish a saved version without building anything. ### Can I download an old version? Yes, on a paid plan. **Settings**, **Backups** has a **Download** button on every version, which gives you its code as a zip. See [Your site's code](https://briks.dev/docs/code). ### Is anything deleted when I undo? No. Every version stays saved, and any of them can be made live again. ### I undid by mistake. Press redo, or open **Versions** and press **Make live** on the version you want. ## Read next - [Working on a project **Making changes** How to change your site by writing to Briks: what to say, adding pictures, what a change holds and costs, inner pages, queued requests and fixing a miss.](https://briks.dev/docs/making-changes) - [Working on a project **A/B tests** Test a saved version of your site against the live one: start it from Versions, see which converts more visitors, then keep the winner. With a worked example.](https://briks.dev/docs/ab-tests) - [Data and automation **Backups** What Briks keeps of each project: code versions, database restore points and nightly copies. How to restore, how to download and what each copy holds.](https://briks.dev/docs/backups) - [Publishing and domains **Published versions and deploy hooks** See every version your site has published, restore one, and make deploy hooks: private addresses that publish your site again when another tool calls them.](https://briks.dev/docs/publish-history) Still stuck? Write to [hello@briks.dev](mailto:hello@briks.dev) with your project's name and what you expected to see. A screenshot helps.