Find the draft you want to keep.
Revisit a paragraph before the rewrite. Version history shows saved versions of a cloud document so you can compare the text and restore the draft you need.
Open the editorVersion history requires a signed-in account and a paid workspace owner plan. Restoring also requires write access.
Current document
## Review notes
Combine all observations in the main analysis.Selected earlier version
Review notes
Keep the pilot study separate from the main analysis.
Choose a saved version to inspect its content. Selecting it does not change the current document.
Compare before you restore
Open the document’s History dialog and select a saved version. The comparison shows the text added or removed since that version, alongside the current document. Selecting a version only changes what you are inspecting.
Use this to recover a removed explanation, revisit wording before an AI rewrite, or check how a note changed. If you only want one sentence back, read the earlier version and edit that passage rather than replacing the whole document.
Restore the document, with confirmation
Choose Restore this version and confirm when you want the selected text to become the current document. The differing, non-empty text it replaces is saved as another version first. The filename and document stay in the workspace.
A viewer can inspect accessible history but cannot restore it. An active live collaboration session can also block restoration when collaboration is enabled. Restoring a source file does not refresh a published page; review the draft and update that publication separately.
Know what the history contains
The editor keeps up to 50 versions per file. Older versions are removed as new versions are added. Automatic snapshots preserve the previous text when a cloud write changes it, at most once every 10 minutes. Unchanged text and an empty initial state do not need an automatic snapshot.
MCP writes that replace non-empty text record the previous content without that automatic-snapshot interval. The same 50-version limit still applies. History is therefore a record of saved states, not a recording of every keystroke or an unlimited archive.
Keep long-term copies when you need them
Download a Markdown copy for a milestone you need to retain independently of the history limit. Keep important research data and original source files in their own storage as well. Version history helps you revise a document; it is not a complete backup policy for everything linked from it.
Use workspaces to organize the current files, or read the MCP targeting guide to keep an assistant’s revisions in the same document. For a longer writing project, the Markdown for writers guide covers structure and export choices.