Premium plugin
Versions is not included in the standard Redactor package. It ships as part of the Editorial Suite — purchase the suite on the pricing page (with Redactor, or later from your account), then download the package and enable the versions plugin.
Versions give the document a timeline: automatic snapshots as people write, plus manual saves when something matters — before publish, after a big paste, after an AI pass. The plugin is the store and API; you build the history panel around the editor and call restore / diff from your UI.
That is insurance for long-form work and for teams that need an audit trail of how a piece changed.
API, host UI example, and storage shape: Versions plugin. Pairs naturally with Review when comments should travel with a snapshot.
What authors get#
History that appears on its own. With auto-capture enabled, meaningful edits create versions in the background — fewer “I forgot to save a draft” moments.
Manual checkpoints. Label a version when you hit a milestone (“Ready for legal,” “Before rewrite”) so the list stays readable.
Compare and restore. Open the original baseline or an earlier snapshot, see what changed, and restore when a direction did not work out.
Review-aware snapshots. When Review is loaded, version captures can include review data so feedback and content stay aligned in history.
Where Versions fit#
Ideal for editorial desks, knowledge bases, and any long document where undo is not enough — you need named points in time. Not used together with Schema or Email products, which manage different document models.
Give authors confidence to experiment: AI rewrites, big restructures, and collaborative review all become safer when a good version is one click away.