Version history

Version history lets you review and restore earlier versions of an entry. You can view history on every plan. You can restore a version only if the workspace itself is on Plus or Pro. A free team that shares storage from a personal paid plan cannot restore.

Review earlier versions

Open a saved entry in the editor.
Select "History" at the top of the editor. The button is disabled for entries that have not been saved yet.
Select a version in the list to see what was recorded.

On narrow screens such as phones, history opens full screen. Select "Close" in the upper right to go back to editing.

History keeps the latest 50 versions of each entry. A version is recorded whenever the content or publish status is saved. Beyond 50, the oldest versions are deleted one at a time. Unsaved input is not recorded.

When you "Save as draft" on a published entry, the version is labeled that way. Publishing and discarding unpublished changes are also shown as separate records. See unpublished changes.

Restore a version

Owners and editors can restore the selected version. Restoring saves the entry immediately and adds a new history record.

A restore brings back the field values. It does not bring back the earlier publish status or scheduled times. If you restore a published entry, the restored content stays published and is delivered.

Restoring a version discards any saved unpublished changes. The restored content goes live as it is, so check the diff first if you need to.

After restoring, check the entry, and use preview if you want to see how it looks on your site. Viewers can see history but cannot restore.

What can be restored

Versions deleted after the 50-version limit cannot be recovered.
If you delete the entry itself, its history is deleted too.
It does not restore files themselves or earlier schemas.
If you have changed fields or deleted media since, a restored version may not look the same as before.

To keep important entries for the long term, do not rely on version history alone. Store a copy of the content elsewhere.

History by language

For multilingual APIs, history shows the language selected in the editor. Saves and restores are recorded separately for the main language and each additional language. Restoring one language does not change the values or publish status of the others. A restore brings back field values and keeps the current publish status, so restored content is delivered in whichever language versions are currently published.

Deleting an additional-language version also deletes its history, and recreating the version does not bring the old history back. The plan requirement, permissions, and 50-version limit are the same as for the main language.

When history cannot be used

You can open and read history in a free workspace. If you cannot restore, check the workspace's plan and your role. Even if your personal workspace is on a paid plan, you cannot restore in a Free team. See Plans and limits.