barecopy
Guide · updated 2026

Your PDF still contains the version before your edit

You deleted a page, replaced a paragraph, covered a figure, and saved. In most PDF editors that save did not rewrite the file — it appended the changes to the end and left the previous version sitting in front of them.

Why PDFs are saved this way

The format allows incremental updates: rather than rewriting the whole document, an editor appends the new objects and a small index pointing at them. It is fast, it is safe against corrupting a large file, and it is required for digital signatures, which have to leave the signed bytes exactly as they were.

The side effect is that the file now contains both versions. The reader shows you the latest one. Everything the previous one contained — the page you deleted, the text you replaced, the image you swapped — is still inside, and tools that walk the file rather than render it can read it back.

This is why "I removed that page before sending" is not always true, and why a file can be noticeably larger than its visible contents suggest. It compounds with covering things up: text you hid under a black box may survive twice over — once under the box, once in the revision before it.

How to check what your file carries

A rough signal you can see yourself: a PDF that has been saved once ends with a single %%EOF marker. Each incremental save appends another one. Opening the file in a text editor and counting them gives you a quick answer, though a "fast web view" file adds one legitimately.

Signed documents will always show more than one, by design — the revision before the signature is the document as it was signed.

How to save a copy with only one version

  1. Use Save As rather than Save in your PDF editor — it rewrites the document in one piece instead of appending.
  2. Or run the editor's optimiser (in Acrobat, Save as Other → Optimized PDF), which rebuilds the file.
  3. Or export the document again from the application that produced it.

Any of these produces a file with a single revision. Note that all of them also break an existing digital signature — unavoidably, since the signature covers the old bytes.

A check before you send, without uploading the file

Barecopy reads the PDF in your browser and reports how many earlier revisions it carries and how many objects are left over from them, alongside annotations, attachments and signatures. The file is never transmitted.

Do it now

See how many versions your PDF is carrying

Drop a PDF on Barecopy. It reports earlier revisions, comments, attached files and signatures, and Pro rewrites the file as a single revision.

Open Barecopy →

What Barecopy does about it

Detection is free. Removal is a Pro option: Barecopy rewrites the document as one revision and drops every object the catalog can no longer reach, so content from earlier saves stops travelling with the file. The visible document is unchanged.

If the PDF is signed, Barecopy says so before you clean it. Removing metadata rewrites the bytes and the signature can no longer validate — so either send the signed original, sign the clean copy again, or let Barecopy drop the void signature along with the signer's name, reason and location rather than leave one that reads as broken.

Frequently asked

Does every PDF contain earlier versions?

No — only ones that were saved incrementally at least once, which is what most editors do on a plain Save. A file exported fresh from Word or a browser has a single revision.

Can a recipient actually read the old version?

Not in a normal reader, which shows the latest one. But the bytes are there, and tools that parse the file rather than render it can extract them. Assume anything in the file is readable.

Will removing revisions change how my PDF looks?

No. The current version is what gets written out; the earlier ones are what gets dropped. What does change is that a digital signature, if there is one, stops validating — that is inherent to changing the bytes at all.