Undo, redo & edit history
The editor keeps a full undo history, so you can edit freely without fear of breaking something. If a change doesn’t look right, take it back.
The shortcuts
Section titled “The shortcuts”| Action | macOS | Windows / Linux |
|---|---|---|
| Undo | ⌘Z | Ctrl+Z |
| Redo | ⌘⇧Z | Ctrl+Shift+Z or Ctrl+Y |
The toolbar also has undo and redo buttons, which dim when there’s nothing to undo or redo. (Shortcuts pause while you’re typing in a text field, so editing a value won’t trigger an undo mid-keystroke.)
What’s on the stack
Section titled “What’s on the stack”One history, covering everything that changes the document:
- Turning an entry on or off
- Editing an entry’s text, type, or replacement
- Adding or removing an entry
- Drawing, toggling, or removing a redaction box
- Highlighting text to redact
- Applying a template
Entries and drawn areas share the same stack, so undo walks back through your work in the exact order you did it, whatever the kind of change.
What’s not on the stack
Section titled “What’s not on the stack”A few things sit outside undo because they’re not edits to the document’s content:
- Switching the view (Original ⇄ Anonymized, Instant redact) — these just change what you’re looking at.
- Refresh / regenerate — this produces a version, and versions are their own safety net (every regenerate is kept and selectable).
- Save to output — promoting a version is a deliberate, separate action.
So the mental model is: undo handles the list and the boxes; versions handle the generated documents; Save to output is the one commit to your real file.
You won’t lose work by accident
Section titled “You won’t lose work by accident”If you try to close the editor with unsaved changes — anything not yet saved to output, including a method switch you refreshed but didn’t promote — Piixie asks first: Save & close, Discard, or Cancel. Closing never silently throws away edits.