How to Tell if a PDF Was Altered or Backdated
A plain-English guide to how digital forensic examiners detect whether a PDF has been changed or backdated, and when to bring in a professional.
A PDF can be shown to have been altered or backdated by examining its metadata and internal structure. Every PDF records when it was created and last modified, the software that produced it, and a history of changes. When these internal records conflict with the date a document claims, it is a common indicator of tampering.
A PDF quietly keeps a record of its own history
Most people see a PDF as just the page in front of them. But every PDF also carries hidden information about itself: when it was made, when it was last changed, and what software created it. Forensically, much of this lives in the file's metadata (its embedded “data about the data”). Because the person who made the document usually never sees these records, they are easy to overlook and hard to fake convincingly.
A PDF can record:[1]
- When it was created and when it was last modified, as two separate timestamps (the CreationDate and ModDate entries).[1]
- The software that produced it, for example a particular version of Adobe Acrobat, a “Save as PDF” from Word, or a scanner's own software. The PDF records this in the Creator and Producer fields, and the Producer field is updated by each tool that processes the file, leaving a running record of the last software to touch it.[3]
- A trail of edits. PDFs can be changed by appending a new section to the end of the file rather than rewriting it. This “incremental update” can leave earlier versions of the document intact inside the same file.[4]
- A richer set of metadata stored in an embedded XMP stream, which can hold additional dates and history beyond the basic entries.[2]
Common signs a PDF was altered or backdated
Each of these is a plain-language warning sign, and each points to something specific an examiner looks at:
- It was “last modified” after the date it was supposedly signed or finalized, meaning the file changed when it shouldn't have.
- It was made with software that didn't exist yet. A document dated 2015 that was produced by a 2020 version of a program can't have been created when it claims. (Examiners call this a “software anachronism.”)
- Leftover earlier versions inside the file show content was added after the document was supposedly finished. Because incremental updates append rather than overwrite, the file's cross-reference structure can preserve a record of what changed.[4]
- A digital signature that no longer matches the current file. When a signed PDF is modified by incremental update, the data covered by the original signature is preserved, so it is possible to compare the signed state against later changes.[5]
- Internal dates that disagree with each other across the document's own parts.
- Metadata that's been wiped clean, which can itself be a sign someone tried to hide the trail.
Why the date printed on a document proves nothing
The date you see on a document is just typed text, and anyone can put any date there. What's much harder to fake is the file's own internal record of when it was really created and changed. That is why a forensic examination looks past the visible page and into the file itself.
What an examination can, and can't, tell you
Being straight about the limits is part of doing this credibly. A metadata examination can establish when a file was truly created and last changed, what software touched it, and whether its contents were altered after a certain point. It generally cannot tell you who sat at the keyboard or why, only what the file's own records show. A qualified examiner is careful to claim only what the evidence supports.
If a PDF's authenticity matters to a legal or business dispute, a professional examination produces documented, defensible findings suitable for litigation. Inspecting the metadata yourself can also change the file and compromise it as evidence, so the safest step is to preserve the original and have it examined. Preserving original digital evidence and treating files as a forensic data source are core principles of established forensic practice.[6]
Why you need a forensics firm that specializes in metadata analysis
If you suspect a PDF was altered or backdated, the right professional is a digital forensics firm that specializes in metadata analysis. This is a distinct specialty. A traditional forensic document examiner focuses on handwriting, ink, and paper, and a general IT or computer forensics firm focuses on recovering data from devices and networks. Neither is necessarily trained to read the internal structure of a PDF and explain what its metadata does, and doesn't, show.
When choosing an examiner, look for:
- A metadata analysis specialty covering the specific file type in question.
- A forensically sound process that works from a preserved original and documents chain of custody.
- A written forensic findings report that states what the evidence supports and what it doesn't.
- Expert witness experience, so the findings can be explained in a deposition or at trial.
Suspect a PDF has been altered or backdated?
DeepData Forensics is a digital forensics firm that specializes in metadata analysis. We perform confidential digital metadata analysis and delivers written forensic findings reports, typically within 48 hours.
Contact us about your document →Who should I hire to find out if a PDF was altered or backdated?
Can you tell if a PDF was backdated?
Does opening or editing a PDF change its metadata?
Is PDF metadata analysis admissible in court?
How long does a PDF analysis take?
- ISO 32000-2 (PDF 2.0), Clause 14 — Document interchange, which defines the PDF document information dictionary and its CreationDate and ModDate entries. Published by the PDF Association: pdf-issues.pdfa.org/32000-2-2020/clause14.html. The Portable Document Format was created by Adobe and standardized as ISO 32000-1: iso.org/standard/51502.html
- Adobe, XMP (Extensible Metadata Platform) Specifications — the metadata framework embedded in PDFs and images, defining fields such as creation and modification dates. Published by Adobe (the format's creator) and also standardized as ISO 16684-1: developer.adobe.com/xmp/docs/xmp-specifications
- ISO 32000 defines the Creator field (the application that authored the original document) and the Producer field (the application that last processed or converted it). See ISO 32000-2, Clause 14 (document information dictionary): pdf-issues.pdfa.org/32000-2-2020/clause14.html
- ISO 32000-2, Clause 7 — Syntax, defining the cross-reference table (7.5.4) and incremental updates (7.5.6), the mechanism by which changes are appended to a PDF and earlier content can be preserved: pdf-issues.pdfa.org/32000-2-2020/clause07.html
- ISO 32000-2, Clause 12 — Interactive features (digital signatures). When a signed document is modified by incremental update, the byte range covered by the original signature is preserved, allowing the signed state to be reconstructed and compared. Standard overview via the PDF Association: pdfa.org/resource/iso-32000-2
- Scientific Working Group on Digital Evidence (SWGDE), Best Practices for Digital Evidence Collection, and NIST Special Publication 800-86, Guide to Integrating Forensic Techniques into Incident Response — on preserving original digital evidence and treating files (and their metadata) as a forensic data source: swgde.org — Digital Evidence Collection; csrc.nist.gov/pubs/sp/800/86