Hidden Edit History - Free Online Browser Tool

Count the incremental save revisions a PDF hides, report each save date, and flag earlier content still recoverable from the bytes.

Choosing “save” in most PDF software does not overwrite the file — it appends a new revision to the end and leaves the old bytes in place. A document you believe was corrected can therefore still physically contain the text that was removed. This tool reads those bytes and reports the save history: how many revisions the file holds, which date each one recorded, and which signals (superseded object copies, free-listed objects whose bytes remain) mean an earlier version could be recovered by a specialist tool.

This hidden edit history utility runs completely inside your web browser. Your document is opened locally and processed on your own device using JavaScript and WebAssembly, so your file is never uploaded to any server. There is no signup, no watermark and no limit on how many documents you can handle.

  • 100% client-side - files never leave your device
  • Instant processing, no upload wait
  • Works on desktop, tablet and mobile
  • Free forever, no account required

Common next steps: Repair PDF, Extract Metadata, Sanitize Tracking IDs, Inspect PDF Page Boxes.

How to Use the Hidden Edit History Tool

Four steps, and the whole thing runs locally on your own device.

  1. Select the PDF

    The file is scanned as raw bytes, so its save history survives even when a normal viewer would only show the newest version.

  2. Read the revision list

    Each cross-reference section the file contains is listed with the byte range it occupies and the creation or modification date recorded at that save.

  3. Check the recoverability flags

    Superseded object copies, free-marked objects still present, and the byte count held by earlier saves show whether older content physically remains.

  4. Export the report

    Download JSON for the full detail, CSV for a log of every revision, or readable text to attach to an email or a ticket.

Frequently Asked Questions

Can this tool recover the earlier version of my document?

No — and that is deliberate. It reports which signals mean recovery is possible; actually rebuilding the old revision needs a tool that walks the older cross-reference chain, which means writing a file. This page only reads.

My file looks clean. Why does it still show several revisions?

Because viewers only show the current state. Every app abandonment, annotation save or automatic backup performed with an appending tool adds one revision, and none of them are visible in the reader.

What does “superseded object” mean?

An object that exists in more than one copy because a later save replaced it and kept the old bytes. The oldest copy is the one an earlier version of the page can be reconstructed from.

Does an encrypted PDF hide its history?

The save dates in the trailers remain readable even when object content is scrambled, so the revision count is still reported — with a note that the underlying content is encrypted.

Why does a file with no dates still show a revision count?

Revision markers and dates are stored separately, and some writers never fill the date fields. The count is read from the structure; missing dates are reported as not recorded rather than guessed.

Is any of this sent to a server?

No. The scan runs in your browser tab on the file you chose, and the exported report is written by the same tab. Nothing is uploaded and the source PDF is not modified.