Skip to main content
The editor has unbounded undo/redo for the current session. Every action you take — move, resize, color change, layer add/delete — lands on a history stack you can walk backward and forward.

​
Undo and redo

  • Undo: ⌘Z (Mac) or Ctrl+Z (Windows/Linux). Also in the toolbar.
  • Redo: ⌘⇧Z or Ctrl+Shift+Z. Also in the toolbar.
The toolbar buttons dim when there’s nothing left to undo or redo.

​
What’s captured

Every discrete edit creates a history entry. Specifically:
  • Creating a layer (text, image, shape, frame, QR, clipart, custom component).
  • Deleting a layer.
  • Transforming — move, resize, rotate, skew.
  • Styling — color, stroke, font, opacity.
  • Editing content — typing text, replacing an image source, changing a QR value.
  • Reordering layers up or down the stack.
  • Grouping / ungrouping.
Text typing is coalesced into larger entries so a single undo doesn’t cost you one keystroke at a time — it rolls back to the last natural break.

​
What’s NOT captured in history

Some things are intentionally out of the history stack:
  • Selection — selecting and deselecting doesn’t create history entries (that would be noisy).
  • View state — zoom, pan, ruler visibility, panel collapse states.
  • Saved vs unsaved state — undoing past a save still undoes; saving doesn’t clear history. But closing and reopening the editor resets history entirely.

​
Saving vs history

Undo and save are independent:
  • Undo walks your local history in memory.
  • Save pushes the current state to the server.
If you undo past a save, Customei still works — the next save will persist the undone state. There’s no concept of “uncommit” or “discard to server state” in the current editor; if you want to revert to the last saved version, close the editor without saving and reopen it.

​
History is per-session

History is kept in browser memory. Closing the tab or navigating away clears it. This is by design — every session starts fresh, so you can edit confidently in one session without carrying ambiguous state across days.

​
Tips

  • Undo is fast. Don’t be afraid to experiment; you can always walk back.
  • Save when you’ve hit a known-good state. Save acts as a “checkpoint” you can return to by closing and reopening.
  • Complicated edits deserve a save before you continue. If you’re about to restructure the layer tree, save first so a crash or accidental close doesn’t cost you progress.

​
Next