Version history is a record of past versions of a file, kept automatically by a service or application. It typically shows who changed what and when, and lets you compare versions or restore an older one. Google Docs, Microsoft OneDrive, Dropbox and macOS Time Machine all offer forms of it.
Why it matters
It protects against accidental edits, overwrites and deletions, and lets collaborators see how a document evolved. For individuals, it can rescue a paragraph deleted last week. It is lighter than full source control, but retention limits apply: many services keep versions only for a set period or a number of revisions, and the exact limits differ by plan.
Example
In Google Docs, choose File, Version history, See version history. A side panel lists timestamps with names of editors; clicking one shows that state, and Restore this version makes it current again. In Git, the equivalent is:
git log --oneline -- report.md
git checkout a1b2c3d -- report.md
Common mistakes
- Assuming unlimited retention; old versions may be pruned.
- Counting it as a backup if the account itself is lost or deleted.
- Not naming important versions, which makes them hard to find later.
Related
Get notified when this term updates
Plus occasional practical tips on uptime and monitoring, nothing else. Unsubscribe anytime.
This page is general information written by our editorial team and updated when documentation changes. Servers and providers differ, so test changes safely first. See our editorial policy and disclaimer.