Undo PDF edits: what the history keeps, and where it stops

Edit PDFReal text editing, objects, annotations, forms. Free, runs on your device.Open

How the history works

Each thing you do in the editor becomes 1 entry in a list: “Added text”, “Moved a shape”, “Replaced “May” 23 times”, “Added a blank page”. Every entry knows how to do itself and how to undo itself. Undo takes the newest entry off the list and reverses it; Redo puts it back. The steps run one at a time, in order, so pressing Ctrl+Z twice quickly while an edit is still being written can never tangle them.

You can see the list. On a computer it sits under the properties on the right, headed Changes, newest first, each entry with the page it touched (“p3”). On a phone it is in More, then Changes. It is a record, not a menu: to get back to step 2, undo until you are there.

What undo covers

Everything that changes the document:

• Text: a retyped line, new text, a change of font, size or colour. When a retype needed a substitute font, undo swaps the original back exactly.
• Objects: moving, resizing, duplicating, pasting and deleting text, pictures and shapes. A deleted picture comes back where it was.
• Marks: highlights, underlines, notes, drawings, signatures, filled form fields and ticked boxes.
• Pages: moving, turning, copying, deleting, and adding a blank page, another PDF’s pages or pictures as pages.
• Find and replace: Replace all is 1 step, however many matches it changed. Our test replaced 500 matches in a 500-page file in about 2.3 seconds; 1 Ctrl+Z puts all 500 back.
• Redaction marks: boxes drawn with the Redact tool are only marks until you save, and they undo like anything else.

The keys: Ctrl+Z undoes, Ctrl+Shift+Z or Ctrl+Y redoes, and on a Mac use Cmd. The Undo and Redo buttons sit at the top of the editor on every screen size. One detail: while a text box is open and you are typing, Ctrl+Z undoes letters inside the box, as in any text field. Press Enter to place the text, and from then on it is 1 step in the history.

Redo, and what a new edit does to it

Undo 2 steps and Redo can bring both back, in order. But make a new change at that point, and the 2 undone steps are gone: the history is a single line, not a tree. That is how word processors behave too. If you are not sure whether you want those steps, redo them before you try something new; you can always undo again afterwards.

Saving does not end the history

Saving writes a copy of the document as it stands at that moment. It does not clear the list. So you can save, look at the result, undo 3 steps, and save again. Each save is a new file (the name ends in -edited, or -redacted when redaction marks were taken out), so the earlier copy stays where it landed.

Even redaction follows that rule inside the editor. Saving takes everything under the black boxes out of the saved file for good, but the document open in the editor keeps it, so you can still unmark a box and save a different copy. The saved file itself cannot be un-redacted, which is the point of redaction.

The hard boundary is closing. Close the file, and its history goes with it. The saved copy is then simply the file. That is why the habit worth keeping is the dull one: keep your original until you have opened the saved copy and checked it.

Why this beats the convert-to-Word routine

A common way to “edit” a PDF is to convert it to Word, change it there and export a new PDF. That route has no history worth the name: every export rebuilds the whole document, and each round trip moves things. Our own PDF to Word converter says before you start that it rebuilds the content, not a copy of the layout, so columns, exact positions and fonts are not kept; the trip back adds a second rebuild on top.

Editing in place touches only what you changed. A retyped date changes 1 line; the fonts, pictures and positions of everything else are untouched. And because every step is in the history, trying something costs nothing: try it, look, undo. When a whole section must be rewritten, Word is still the better place; PDF to Word, Excel and text explains when.

The honest part: what undo cannot do

• It cannot reach past the opening of the file. Undo goes back to the document as it was when you opened it, never to an older version of that file.
• It does not survive closing. Once the file is closed, there is no history to return to.
• A crash keeps your work, not your history. A moment after each change, the editor keeps a recovery copy in your browser’s own storage, on your device. After a crash or a closed tab, open the editor again and choose Recover: the file comes back with your changes, and a note says “Undo starts from here”. Files over 200 MB get no recovery copy, and a private window may keep none; the status line says which.
• There is no server copy to fall back on. Everything runs on your device and nothing is uploaded, so there is no account history to restore from. The recovery copy and your own saved files are all there is, and that is the same fact that keeps your documents private.

For everything else the editor does, start with the editing guide, and for changing the same word across a long file, find and replace.