How to replay a Google Doc's revision history

What Google Docs actually stores

Behind the version history menu, Google keeps a far more detailed record than the named versions you see. Every insertion and deletion is logged as a small change with a timestamp and the account that made it. Google's own interface collapses these into snapshots a few minutes apart. The raw record is what makes a full replay possible.

Checked4AI reads that record through the Google Drive API for any document you can open, reconstructs the document state after each change, and plays the changes back in order. The result looks like watching the author type, because in effect that is what it is.

How to replay a document

1. Add Checked4AI to Chrome and sign in with your Google account.
2. Open the Google Doc. A Checked4AI button appears in the toolbar on docs.google.com.
3. Click it. The extension syncs the revision history and opens the viewer in a new tab. Long documents with many sessions take a few seconds.
4. Press play. Choose 1×, 4×, 8× or 10× speed, or drag the scrubber to any point in the document's life.

Revision data is cached in your browser's local storage so re-opening the same document is instant. Nothing is uploaded to Checked4AI's servers unless you run an AI check. See the privacy policy.

Reading the replay

The session timeline

Writing rarely happens in one sitting. The timeline groups the history into sessions, separated by gaps in activity, and shows when each session happened and how much text it added. Click a session to jump the replay to its start. For a long essay this is usually the first thing to look at: three evening sessions across a week tells a different story from one 20-minute session the night before the deadline.

Paste events

Pasted text arrives in one instant, so it stands out in a replay: a paragraph appears fully formed instead of building up a few characters at a time. Checked4AI flags large pastes in the timeline so you can jump straight to them. It also distinguishes internal pastes, where the author moved their own text around within the document, from external pastes that brought in new text from outside.

The Natural Typing score

Above the replay, Checked4AI summarizes the whole history into a single Natural Typing score from 0% to 100%. It combines three signals:

• Delete ratio. How much text was removed relative to how much was added. Human drafting involves constant backspacing; pasted text does not.
• Keystroke variation. How irregular the timing between keystrokes is. People speed up, slow down and pause; scripts don't.
• Paste volume. What share of the final document arrived through pastes rather than typing.

Beyond the replay

The replay answers "how was this written?" Two Pro features answer the follow-up questions. The AI Content Check runs on the document text automatically when the viewer opens and returns an AI-generated likelihood with a one-sentence explanation. Auto-typer detection examines keystroke timing and flags text that was typed by a script rather than a person, which a plain replay cannot distinguish from real typing.

When you need to share what you found, Pro users can export the replay as a video file. It plays anywhere and captures every keystroke, paste and deletion exactly as it happened.

Who uses revision history replay

• Teachers checking whether an essay was drafted or pasted. See how teachers check Google Docs for AI writing.
• Students who need to prove they wrote something themselves. See what to do if you're accused of using AI.
• Editors and hiring managers reviewing writing samples and take-home assignments.
• Writers who want to watch their own process, or record a draft coming together for a class or a portfolio.

Replay vs Google's built-in version history