Revision history

What creates a revision

Saving an owned Pro cloud document advances its saved version and retains bounded revision history. Local browser saves do not create Pro cloud revisions. Unsaved editor changes are not a revision and cannot be recovered from history.

Use the document action for Version history to open the history overlay for the active eligible cloud document.

Preview without changing the editor

Select a revision to preview its content and saved page settings. Previewing does not replace the active editor document. Use the displayed version and timestamp to compare it with the current saved document before choosing a destructive action.

Restore a revision

Restoring creates a new current saved version from the selected historical content. It does not rewind the database clock or silently discard the intervening audit trail. Current document identity and current template status remain separate from the restored content.

Save or download any unsaved editor changes before restoring. A stale restore request is rejected when the server has advanced beyond the version the action expected; reload history and review the newer state.

Delete an eligible revision

A non-current revision can be deleted when the interface offers that command. The current saved version cannot be deleted as though it were merely historical. Deleting the whole résumé is a separate document-level action and removes its history after confirmation.

Subscription state

Navigable history requires active Pro access. If a subscription becomes inactive, retained history is not exposed through the paid history workflow. Reactivating access can make retained eligible history navigable again. Download the current documents through the cloud archive before closing an account.

Prerequisite: Understand cloud saved state. Next: Review a saved document with AI.