Skip to main content
Reactive Resume keeps two layers of change history for every resume:
  • Undo and redo: a live timeline of the changes you’ve made in the current builder session.
  • Version history: server-side snapshots taken at meaningful moments, kept even after you close the builder.
Use undo for a quick correction. Use version history to jump back to an earlier editing snapshot, import, or AI/API edit.

​
Undo and redo

Every change in the builder is undoable: typing, drag-and-drop reordering, template and layout switches, and edits applied by the AI assistant.
1

Open your resume in the builder

Undo history is scoped to the resume you have open.
2

Undo or redo

Use either the toolbar buttons on the floating dock or a keyboard shortcut:Rapid typing collapses into a single step, so one undo removes a phrase rather than one letter.
When your cursor is inside a text field, Cmd/Ctrl+Z falls back to your browser’s native input undo, so you can undo just the characters you typed. Click outside the field, or use the dock buttons, to undo builder-wide changes such as a template switch.
Undo history lives in your browser for the current session. Reloading the builder clears it, so use version history for anything older.

​
Version history

Reactive Resume snapshots your resume automatically:
  • when you import a resume;
  • when the AI assistant or API applies edits;
  • on periodic saves during editing, including template switches;
  • when you restore a version.
Snapshots are stored on the server, per resume, and are kept across sessions. Reactive Resume keeps a rolling window of the 30 most recent snapshots for each resume. Periodic editing snapshots, including template changes, are throttled to at most one every two minutes. Imports, AI/API edits, and restores create their own checkpoints.

​
Open version history

Click the clock icon in the builder header, next to the resume name, to open the version history menu. The menu lists recent snapshots newest first, each with a label describing what triggered it and a relative timestamp such as 2 hours ago.

​
Restore a version

1

Open the version history menu

Click the clock icon in the builder header.
2

Pick a snapshot

Select the entry you want to restore. Reactive Resume asks you to confirm before replacing the current data.
3

Confirm the restore

The resume is updated to the snapshot’s contents and reloads in the preview.
Restoring is non-destructive: it writes the older snapshot back through the normal update path, so:
  • your previous versions are still listed in the menu;
  • the restore itself becomes a new snapshot;
  • if you change your mind, you can restore the pre-restore version, or press Cmd/Ctrl+Z to undo the restore.
Only the resume owner can list or restore versions. A locked resume cannot be edited or restored until you unlock it from the dashboard.

​
Keep longer owner-managed history with Git

In-app version history and Git backups solve different problems:
  • In-app version history is automatic, stored by Reactive Resume, and limited to the 30 most recent rolling snapshots for one resume.
  • Git history contains only the JSON exports you choose to commit. It is stored in your own local repository, uses your commit messages, and follows the retention you choose.
Git backup is manual. Reactive Resume does not create commits, synchronize with a repository, or upload files to a remote. To set up a local repository and recover a committed export as a new resume, see Keep JSON backups in a local Git repository.

​
Which to use when