Skip to content

Version History

Modular Mail protects your work with two layers of version control: real-time undo/redo for immediate corrections and automatic checkpoints for recovering earlier states.


Undo and redo work in real-time while you edit. Use them to reverse recent changes without leaving the editor.

  • Undo: Cmd+Z (Mac) or Ctrl+Z (Windows)
  • Redo: Cmd+Shift+Z (Mac) or Ctrl+Shift+Z (Windows)

You can also use the undo and redo buttons in the editor toolbar.

Every change you make in the editor creates an undo point:

  • Editing text, images, or links in module fields
  • Adding or deleting modules
  • Reordering modules by drag-and-drop
  • Duplicating modules
  • Changing style options or layout variants
  • Editing module code (template editor)
  • Renaming modules (template editor)

The editor stores up to 50 undo states per session. Undo states reset when you reload the page.

When you undo, the editor reverses your last action and moves it to the redo stack. When you make a new change after undoing, the redo stack clears—you can’t redo actions after making new edits.

Undo and redo happen instantly. Changes sync to your preview in real-time.


Version checkpoints are permanent snapshots of your template or campaign. They let you review and restore earlier states, even after closing the editor.

The editor creates checkpoints automatically every 5 minutes when you’ve made changes. These auto-checkpoints capture your work in the background without interrupting you.

Auto-checkpoints appear in version history as “Autosave 1,” “Autosave 2,” and so on. The system keeps the 30 most recent auto-checkpoints and removes older ones.

If you’re editing a template, you can save named versions—permanent checkpoints that are never auto-deleted.

Use named versions for milestones like “Final Design” or “Ready for Review.” Named versions appear at the top of your version history with the name you chose.

To save a named version:

  1. Click Save Version in the editor toolbar
  2. Enter a version name (required)
  3. Add optional notes describing what changed
  4. Click Save Version

Named versions protect important states from being removed by auto-cleanup.


The version history panel shows all checkpoints for the current template or campaign.

To open version history:

Click the Version History button in the editor toolbar. The panel slides in from the right.

The list shows:

  • Version type: Named versions have a bookmark icon. Auto-checkpoints have a clock icon.
  • Version title: Named versions show the name you provided. Auto-checkpoints show “Autosave 1,” “Autosave 2,” etc.
  • When it was saved: Relative timestamps like “2 hours ago” or “Jan 15”
  • Who saved it: The team member who made the changes
  • Notes: Any description you added (named versions only)

If you have named versions, the panel shows a Show named versions only toggle. Turn it on to hide auto-checkpoints and see only your permanent milestones.

Your filter preference is saved per browser.


You can restore any version from history to bring back an earlier state of your work.

To restore a version:

  1. Open the version history panel
  2. Click a version from the list
  3. Review the preview to confirm it’s the version you want
  4. Click Restore This Version
  5. Confirm the restore action

When you restore a version, the editor:

  1. Saves your current work as a new checkpoint (so nothing is lost)
  2. Replaces the current content with the selected version
  3. Reloads the editor to show the restored state

The page reloads after restore to ensure the editor loads fresh data from the server.


The save status button in the top toolbar shows when your changes are saved to the server.

  • Saving… (animated spinner): Changes are being sent to the server
  • Saved (checkmark): All changes are saved. Hover to see when the last save occurred.
  • Retry (warning icon): Save failed. Click to retry.

The editor auto-saves your changes continuously as you work. Most edits save within seconds.

Auto-save handles the immediate save-to-database operation. Version checkpoints (every 5 minutes) create permanent snapshots for history.

If you want to force an immediate save, click the save status button when it shows “Saved.” This triggers a save even if no changes have been made.


Undo/Redo is for in-session corrections. Use it to reverse the last few actions while editing.

Version checkpoints are for recovering earlier states. Use them to restore work from hours or days ago.

Auto-save ensures your changes reach the database immediately. You won’t lose work if your browser crashes.

Save status shows when auto-save completes. Wait for “Saved” before closing the editor to ensure nothing is lost.


Save named versions at milestones. Before major changes, create a named version so you have a clear restore point.

Check version history before big changes. If you’re about to restructure a template, review version history to confirm recent checkpoints exist.

Wait for “Saved” before closing. Always check the save status indicator shows “Saved” before closing the browser tab.

Use undo for quick fixes. If you make a mistake, use Cmd+Z immediately. It’s faster than restoring from version history.

Filter to named versions when needed. If you have dozens of auto-checkpoints, toggle “Show named versions only” to find important milestones faster.