Google Sheets · Sharing, output and safety · Intermediate
Restore version history and inspect cell edits in Google Sheets
Inspect a cell change, preserve an earlier copy and restore a named version without mistaking history for a complete audit log.
Documentation-reviewed author candidate; no native application execution. · Editorial standards
Quick answer
Right-click a cell and choose Show edit history for a focused investigation. Use Last edit to inspect workbook versions. Before restoring, preserve the current state and consider copying the earlier version instead: restoring can clear prior cell-by-cell edit history.
Create a small recovery exercise
Use desktop Google Sheets, edit access, and a private disposable workbook. Do not restore a workbook colleagues are actively editing. The exercise deliberately changes two cells so you can see why reverting an entire version is broader than fixing one number.
On a tab called Budget, enter A1:B3:
| Item | Amount |
|---|---|
| Printing | 100 |
| Delivery | 50 |
In A5 enter Total and B5 enter =SUM(B2:B3). Confirm 150. Wait for the saved status before creating a checkpoint.
Open Last edit at the top right. In the version panel, use the version’s More > Name this version option and name it Before corrections. Return with Back. Named versions help prevent revisions from being merged; Sheets supports up to 15 named versions per spreadsheet.
Inspect before restoring
Change B2 to 900, then change A3 to Courier delivery. Wait for saving. The total is now 950. Name this state After corrections.
Right-click B2 and choose Show edit history. Look for the direct value edit and its attribution. Compare with B5: a formula recalculation is not equivalent to somebody typing 950. Cell history can omit formatting changes, added or deleted rows/columns, formula-driven changes and edits before a restoration.
Open Last edit again, select Before corrections, and inspect both the amount and label. Expand grouped versions if needed. If unchanged rows are hidden, enable Show unmodified rows. Merely viewing this version does not restore it.
Preserve a comparison copy
Next to Before corrections, select More > Make a copy. Give it a distinct name, such as Budget earlier-state comparison, and choose its destination. Do not select sharing with the same people for this private exercise.
Inspect the separate copy: Printing 100, Delivery 50, total 150. The original should still show Printing 900 and Courier delivery, totaling 950. A copy is useful when you need to recover a value without replacing everyone else’s later work; do not assume it preserves the original workbook’s complete historical audit trail.
Before restoring, also preserve the current original: choose File > Make a copy, name it Budget after-corrections backup, and keep it private. Open that backup and confirm Printing 900, Courier delivery 50, and total 950. Leave this backup unchanged until the repair exercise below.
Restore only in the disposable original
Return to the original, reopen Last edit, and choose Before corrections. Select Restore this version, then Restore. Expect both B2 and A3 to revert, not just the mistaken amount. B5 should return to 150.
This operation clears cell-by-cell edit history for changes before the restoration. If that evidence matters, do not use restoration as your investigation tool. Keep the comparison and current-state records instead.
Verify a deliberate repair
For a less disruptive alternative, make a new private practice copy of Budget after-corrections backup and change only B2 from 900 to 100. The total returns to 150 while Courier delivery remains. That difference is the point: cell repair and whole-version restoration have different scopes.
If an earlier state is absent, confirm edit permission and expand grouped revisions; unnamed revisions may have been merged. Do not delete history while troubleshooting: history deletion is permanent. Reopen the saved result and check the two cells and formula rather than relying on a banner alone.
These are documentation-supported recovery steps with synthetic expectations, not a report of a live restore or account test.