Rewind a site or restore a content version
Compare previous work, restore selected site items, and recover a CMS item without confusing draft and live content.
Choose the history that matches the change
Use site history for pages, collection structure, forms, and the common layout. Use a CMS item’s version history for that item’s title, body, and other saved fields. A site rewind is not a complete backup of every project setting, file, and piece of CMS content.
Before restoring, finish or discard unsaved edits and tell collaborators which parts you plan to restore. A rewind can replace work made after the selected point. Neopress may warn you when other people are editing or have changed the site since then.
Rewind selected site items
- Open the project’s Restore or Rewind site control to enter site history.
- Select a restore point from the timeline. Review the changed items and use Compare with current version to understand what would change.
- Choose Select items to rewind, then select the pages, collections, forms, or layout you want to restore.
- Review dependency warnings. A restored page may need a matching collection or form structure; include the required related items when appropriate.
- Confirm the rewind and inspect the restored draft in the editor. Publish the restored changes if you want them on the live site.
This workflow can also recover a deleted page when its previous state is available in history. Rewinding changes the draft; it does not immediately replace the published page design.
Restore a CMS item
- Open the item in its collection and choose Version history.
- Select a version to preview its content. Published versions, automatically saved checkpoints, and manually saved versions can appear in the timeline.
- Choose Restore this version, then review the item in the editor.
- Use Publish or Publish changes on the item when the restored content should replace its published content.
Restoring an item’s title, slug, and field values does not switch its published content snapshot. However, stored metadata can be restored too, and metadata is an immediately saved setting. Review the item’s search and sharing settings as well as its body.
Keep useful checkpoints
Choose Save version and add a short comment before a substantial content rewrite. Pin versions you want to keep. CMS item history normally keeps the latest 50 versions; pinned versions and the currently published version are protected beyond that limit. Automatic history checkpoints are created after 60 seconds without editing or when the editor closes.
After any restoration, check related content and links. Site history and item history serve different scopes, so restoring one does not guarantee that every related asset, reference, or external configuration returns to the same moment.