Live on Product Hunt Intraface launched today. Less steering, more vacations. See the launch
Start for free

What is version history?

Version history is the record of every saved state of a document or file: what changed, who changed it and when. Instead of overwriting the old copy, each save adds a new version, so you can compare two points in time, see who did what, and restore an earlier version if a change went wrong.

Part of Glossary: the terms behind MCP, coding agents and shared pages, defined plainly.

How it works

Every publish adds a version to the stack with who made it; you can compare any two and restore an old one as a new version.younothing is overwrittenversions 1 to 4each with who and whenthe newest is livethe page nowversion 41. each publish adds one2. compare, restoretop of the stack
  1. Every save or publish writes a new version next to the old ones instead of over them. The current document is simply the newest version.

  2. Each version records who made it and when, and usually a message or the diff against the one before.

  3. You open the history to compare two versions, find the one that introduced a problem, and read it in full.

  4. Restoring copies an old version forward as a new one. The versions in between stay, so a restore is itself undoable.

  5. Tools differ on how long versions last: Google Docs may merge revisions over time, a personal OneDrive keeps the last 25, git keeps every commit.

Source: Google Docs Editors Help: See what's changed in a file

Version history versus undo

Undo lives in one editing session and in one person's app. Close the tab and it is gone, and it never shows you a colleague's changes. Version history is stored with the file. It survives the session, it includes everyone's edits, and it names the person behind each one. Undo answers "what did I just do?"; version history answers "how did this page come to say this, and who decided?"

The other near neighbour is a backup. A backup is a copy of everything at one moment, taken for recovery. Version history is per file and per change, and it is meant to be read, not only restored from.

Example: three agents, one page

Picture a landing page edited by three people's coding agents over a week. The history shows version 12 by Lee's agent (new hero copy), version 13 by Priya's agent (moved the pricing table) and version 14 by Omar's agent (fixed a broken image). On Friday the signup button is missing. You open the history, diff 11 against 12, and see that the hero rewrite deleted the button's markup. You restore the button from version 11 into a new version 15. Versions 12 to 14 stay exactly as they were.

Intraface boards work this way: every publish is kept with who made it, agents can list the versions and ask for the diff between any two, and nothing is ever overwritten. The current board is just the newest version.

Why it matters

A page that several people edit needs a memory, or arguments about it cannot be settled. History turns "someone broke it" into "version 12 removed it", which is a fact you can act on. It also makes people braver: a bold edit is cheap when the previous state is one click away.

The detail that matters is retention. Google Docs may merge revisions over time unless you name a version, and it allows 40 named versions per document and 15 per spreadsheet. Microsoft 365 keeps version history only for files stored in OneDrive or SharePoint, and a personal account can retrieve the last 25 versions. Git keeps every commit until you deliberately rewrite history. Know which of these you are relying on before you treat history as permanent.

Common mistakes

  • Assuming you can see it. In Google Docs you need edit permission on the file to browse earlier versions. People with view access see the current state only.
  • Restoring instead of reading. Rolling back to version 11 also removes the good changes in 12 to 14. Diff first, and copy forward only what you need.
  • Saving without saying why. A history of fifty versions labelled only by time is hard to use. Name versions, or write a one-line message with each publish, as git commits do.
  • Treating it as a backup. If the file itself is deleted, or the service's retention trims old revisions, the history goes with it. Export the versions you must keep.

FAQ

Who can see a document's version history?
It depends on the tool. In Google Docs you need permission to edit the file before you can browse its earlier versions. In git, anyone with the repository has the whole history. On a shared board, usually anyone who can open the board can read its versions.
Does restoring a version in version history delete the newer versions?
Usually not. Restoring copies the old content forward as a new version, so the versions in between stay in the history and the restore itself can be undone. Check your tool's documentation, because retention rules differ.
How far back does version history go?
As far as the tool keeps it. Google Docs may merge older revisions unless you name them, a personal Microsoft account keeps the last 25 versions, and git keeps every commit. Systems built around publishing, such as shared boards, tend to keep every version.

Stop sending HTMLover Slack.

Create an account in a minute, connect your coding agent, and make your first board.