Restore a previous version of a table
Open Version history in the table editor header and choose a snapshot to restore. Restoring puts the table's name, columns, dropdown options, and rows back exactly as they were at that moment, so it undoes changes made by you, the AI assistant, or a connected AI tool. You need the same access as editing the table.
Open Version history
The Version history panel lives in the table editor header and lists every saved snapshot of that table.
Open the table you want to work with in the table editor.
Click Version history in the header.
The panel lists snapshots newest first, each with its creation time and a source label: Published, Autosave, AI edit, Claude Code edit, Codex edit, or MCP edit. The current version is the one you are looking at and has no restore action. When no versions exist yet, the panel shows: “No versions yet. One is saved every time the AI changes your table.”
Restore a previous version
Any snapshot except the current version can be restored, and the restore action appears when you hover or focus a version in the list.
Click Version history in the table editor header.
Hover or focus the version you want to go back to.
Choose Restore this version.
ConvertSite applies any pending table edits first, then saves the current table as an Autosave, and then applies the snapshot you chose. The editor reloads with the restored name, columns, dropdown options, rows, and column display settings, and your current selection and filter are reset. The table, column, dropdown-option, and row identifiers are preserved, so pages and data sources connected to the table keep working.
Restoring also rolls back rows your live site wrote after that snapshot, including form submissions. Anything submitted to the table since the snapshot disappears when you restore.
A restore cannot remove a column that a page still needs. When the snapshot lacks a column a page references, the restore fails and the editor shows: “Failed to restore this version. Try again in a moment.”
An active editing lock on the table can also prevent the restore.
How table versions are created
The first time the built-in assistant or an MCP session writes to a table in a run or session, ConvertSite saves an Autosave of the table as it was. When that run or session finishes, ConvertSite saves another version labeled with its source: AI edit for the built-in assistant, or Claude Code edit, Codex edit, or MCP edit for a connected tool. The assistant or MCP client can supply a description for the version.
Everyday manual edits do not create a version for each change, and a write that leaves the table unchanged adds no new version. You can read how the assistant and the ConvertSite MCP change tables in Edit table rows with the AI assistant.