Version History
Version history keeps a snapshot of your email every time you publish. Each snapshot captures the full editor content and the rendered HTML at that moment, so you can experiment freely and roll back to a previous version if something goes wrong.
How version history works
When you publish an email, Temway saves a version that captures both:
- Content — the editor state (blocks, structure, and styling).
- HTML — the rendered output from that publish.
The snapshot is saved at the same moment as the publish itself, so the version and the published email always stay in sync — you’ll never have a published email without its matching version.
Restoring a version
Restoring a version copies its content and HTML back into the email and resets the email’s status to draft. This means a restored email must be re-published before it can be sent — restored content is treated as edited, not frozen.
This keeps the send pipeline safe: you never accidentally send a restored draft as if it were the currently published version. Restoring requires editor permission on the email.
Viewing past versions
Versions belong to the email they were created from. You can look back through an email’s snapshot history and restore any previous version to bring back an earlier state. Because each version is tied to a single email, you can’t share or pull in a version from a different email or workspace.
Plan version caps
The number of versions retained per email is capped by your plan. When a new publish would push you past the cap, the oldest versions are deleted automatically to make room for the new snapshot — so your version list always reflects your most recent work within the limit.
| Plan | Versions retained per email |
|---|---|
| Free | 3 |
| Starter | 10 |
| Pro | 100 |
| Max | 100 |
Why this matters
Version history turns publishing into a safe, reversible action:
- Experiment without fear — try a redesign or a new layout, then roll back if the result doesn’t land.
- Recover from mistakes — restore a known-good version after an unwanted edit.
- Audit your work — each version reflects exactly what was published at a point in time.
Because every publish creates a reliable snapshot, your version history is always an accurate record of what you actually shipped.
Next steps
- Learn how publishing and exporting work alongside version snapshots.
- Organize related designs with layouts and keep branding consistent with branding.