DocVerdict

Learn

Why converted PDFs lose their history

Run a PDF through an online converter, a compressor, or print-to-PDF, and you don't get your document back with a small change. You get a new file, rebuilt from scratch, wearing your document's appearance. The text and layout survive. The history doesn't: original producer, creation date, edit trail, any digital signature, and any XMP record, all replaced by the converter's own fresh stamp.

This matters in both directions. It's how honest files end up looking suspicious, and how altered files get laundered.

The honest case

Someone compresses a contract to get it under an email size limit. The output now says the compressor is the producer and today is the creation date. Nothing dishonest happened, but the file can no longer testify about its own past. If that contract is ever disputed, the compressed copy is a witness with amnesia, and the original file becomes the document that matters.

The laundering case

Now reverse it. Someone edits a bank statement in a PDF editor. The edited file's metadata would show the editor's name and the edit timestamps. So they run it through a converter or print it to PDF. The incriminating history is gone, replaced by a clean, fresh stamp. The result is a file with no edit trail at all.

This is why a generic or converter producer field on a financial document is one of the most reliable flags in document review. Banks, payroll platforms, and government systems generate PDFs with recognizable production signatures. When a statement claims to be from a bank but its bytes say it came from an online tool, the file in hand is not the file the institution produced. That mismatch doesn't prove fraud. It proves an unexplained step between the source and you, and on a money document, that step needs an explanation.

What survives a conversion

Not everything washes out. Embedded images can keep their own internal stamps. Font subsets can reveal the software family that originally set the text. Page dimensions and object structures sometimes carry tool-specific quirks through a rebuild. None of these alone identifies a culprit, but together they can contradict a file's fresh-start story, and contradictions are what examination is for.

FAQ

Is converting a PDF ever wrong to do?

No. Conversion is routine and legitimate. The point is evidentiary, not moral: a converted file can't vouch for its own history, so when a document matters, keep and request originals, the file as the source system produced it.

How can I tell if a PDF I received was converted?

Read the producer and creator fields and compare them to the claimed source. Converter names, print drivers, and online tool fingerprints in those fields mean the file was rebuilt after it left its origin.

Does converting remove a digital signature?

Yes. A signature covers the original bytes, and a conversion produces new bytes. A signed document that arrives unsigned, when the source normally signs, is a meaningful absence.

Check what a file admits to

Drop it on DocVerdict. The verdict reads the producer chain, dates, update history, and signature status, and says plainly whether the file's story holds together. Free, no account, files never stored.