How to Open Version History in Google Sheets (Ctrl+Alt+Shift+H)
Windows: Ctrl+Alt+Shift+H
Mac: Cmd+Option+Shift+H
Ctrl+Alt+Shift+H (Cmd+Option+Shift+H on Mac) opens the complete version history panel for the current spreadsheet, showing every saved revision in a chronological timeline along with which collaborator made changes at each point.
**Why this matters more in Sheets than in a typical desktop spreadsheet**: because Sheets is built for continuous, simultaneous multi-person editing with no manual save step at all, a shared operational spreadsheet can accumulate an enormous number of small changes from many different people over weeks or months — version history is the mechanism for making sense of that ongoing edit stream after the fact, something a single-author Excel workbook rarely needs in the same way.
**Named versions versus automatic checkpoints**: Sheets automatically creates revision checkpoints as you work, but you can also manually name a specific version (through the same version history panel, via "Name current version") to mark a meaningful milestone — like "Final version before Q3 review" — making that specific point easy to find again later rather than having to scroll through an undifferentiated timeline of automatic checkpoints to locate it.
**Previewing versus restoring**: clicking any point in the timeline shows a read-only preview of the spreadsheet as it existed at that exact moment, without changing anything about the current live document — only explicitly clicking "Restore this version" actually reverts the spreadsheet, so browsing through history to compare past states carries no risk of accidentally overwriting current work.
**What restoring actually does**: restoring an earlier version doesn't delete the intervening history — it creates a new current version that matches the restored point in time, while every version between that point and now remains accessible in the timeline if you ever need to step forward again. This means restoring isn't a destructive, one-way action the way it might sound.
**Color-coded collaborator tracking**: the version history view highlights which specific collaborator is responsible for which changes using distinct colors, similar in spirit to a diff view in version control software, which is considerably faster for identifying who changed what than manually asking around a team about a specific edit.
**Related shortcuts**: Option+Shift+H (or the right-click context menu on Windows) narrows this same investigative question down to a single cell's specific edit history, which is faster when you already know exactly which value you're questioning rather than needing the full document-wide timeline.
**Mistake to avoid**: assuming version history has an unlimited retention window — while Sheets retains a substantial history, extremely old automatic checkpoints on a very actively edited file can eventually be consolidated or pruned over long timeframes, which is part of why naming genuinely important milestone versions explicitly (rather than relying purely on automatic checkpoints) is worth doing for anything you might need to reliably find again months later.
**Restoring from version history versus manually undoing**: Ctrl+Z steps backward through your own personal undo stack for the current editing session only, and stops working entirely once you close and reopen the file, or in some cases once enough time or intervening edits from other collaborators have passed. Version history, by contrast, persists indefinitely (within Sheets' retention policy) and works across sessions and devices, making it the far more reliable tool for recovering from a mistake discovered well after the editing session that caused it ended, rather than relying on an undo stack that may no longer exist by the time you notice the problem.
**Comparing two specific points rather than just restoring**: beyond restoring, the version history panel is genuinely useful purely for comparison purposes — checking what a specific section of the spreadsheet looked like a week ago against its current state, without any intention of actually reverting anything, which is a common use case in itself when trying to understand how a shared operational number changed over time rather than only when trying to undo a specific mistake.