Skip to main content

PDF Edit Checker Was this PDF edited after it was made?

Finds later saves, changes after signing and dates or software that disagree. It shows what the file records, not who changed it.

Drop your PDF here to check for edits

or click to browse files

PDF files up to 50 MB

Reading the file...

Looking for saved versions, signatures and metadata

This reads what the file records about itself. Printing to PDF or re-saving through a converter can erase that history, so a clean result does not rule out earlier edits.

  • Saved versions inside the file
  • Changes made after signing
  • Dates and software that disagree

Was this PDF edited? What a check of the file can show

Upload a PDF to see whether it carries traces of later saves, changes made after it was signed, or dates and software names that disagree. A clean result means no edit traces were found in this file. It does not rule out earlier edits, because printing or re-saving through some tools erases the history this check reads.

How can a PDF show that it was edited?

Many programs do not rewrite a PDF when you save a change. They add the changed parts to the end of the file and leave everything before it as it was, so the earlier version stays inside the file. The checker looks for those saved versions, counts them and reads what each one wrote: page content, form fields, comments or document details.

It also reads the created and modified dates, the program that wrote the file, the save history that some programs store in the XMP metadata, and a few structure details, such as the same font embedded under several subset names. It weighs these together and gives one of three results.

What do the three results mean?

Each result comes with the reason it was given, and the limits that apply are shown beside it.

  • No edit traces found: no later edits, changes after signing, or dates and software names that disagree were found. It does not rule out edits made before the file was last rebuilt.
  • Edit traces found: the file shows a strong indicator, such as a later saved version or a change after a signature, or two different moderate indicators together. It does not show who made the change or whether it was legitimate.
  • Can't tell from this file: there is one moderate indicator or three or more weak ones, the file was written by a print or conversion tool that keeps no earlier versions, it has no metadata, or it is encrypted in a way that hides its dates and names.

How do I read the result page?

  • The result comes first, with the reason, the number of saved versions, the number of signatures and what later saves changed.
  • What was found lists each finding with a strength label and what was found, with the saved version where one applies. Strong and moderate findings also say what they can mean, and most findings say what they do not mean. Small details that many unedited files also show are listed under "Small details and notes".
  • Saved versions appears when the file has more than one. Each row gives what that version wrote, the software and date it recorded where it wrote them, a mark on the versions that hold an edit trace, and the signatures it carries.
  • What this result cannot tell you stays beside the result and lists the limits that apply to this file.

Does a later saved version mean someone changed the document on purpose?

No. Issuers also add to their own files. Filling in a form, adding a comment or a stamp, or passing a document through an approval step is often saved as a later version. The checker reports a later version as a trace, because it is one, and leaves it to you to ask the issuer what changed and why.

A later version that only adds a signature or signature checking data is not counted as an edit, because signing workflows commonly produce one.

What happens when a signed PDF is saved again?

A digital signature covers the bytes of the file up to the point where it was applied. When a later version changes anything other than signatures, the checker reports that the file was saved again after signing and names the version and what it changed. Some certified documents allow form filling or comments after signing, so a change after signing is not always a breach of what the signer agreed to.

The checker reads where each signature's byte range falls in the file. A signature field that was prepared but never signed is not counted as a signature. The checker does not check the signature's cryptography, whether the certificate can be trusted, or revocation and timestamps. Use Adobe Acrobat or your e-signature provider for that.

Which indicators does the checker weigh?

Every indicator has a strength. One strong indicator is enough for "Edit traces found", and so are two different moderate ones. A single moderate indicator, or three or more weak ones, leave the result open.

Examples of indicators and an ordinary reason for each
Indicator Strength Ordinary reason
A later saved version Strong An issuer filled in a form, added a comment or stamp, or approved the document
A change saved after a signature Strong A form or comment that the signature's certification allows, or a second signer
A signature range that does not fit the file Strong A damaged file, or a signed file saved again by a program that rewrites it
Fewer form fields than the version before Strong The issuer flattened a completed form
A modified date more than a minute after the created date Moderate The file was saved again in the program that made it, or optimized
Document properties and XMP metadata that disagree Moderate A program updated only one of the two
A different producer in a later version Moderate A signing tool rewrote the document properties
A known PDF editor named as the producer Weak The same editor is used legitimately every day
The same font embedded under several subset names Weak Some generators subset fonts per page or per run

What can this check not see?

A clean result means only that this file shows no edit traces. The checker cannot see:

  • Files that were rebuilt. Printing to PDF, "Save as PDF", Ghostscript and some other converters and libraries write a new file and drop the earlier versions. The checker recognizes some of these tools by the producer name and then answers "Can't tell from this file". A rebuilt file from a tool it does not recognize can still show "No edit traces found".
  • Edits made before the file was printed, scanned or flattened.
  • Who made a change, or whether it was allowed.
  • What is on the pages. It does not compare the words or pictures of two documents.
  • Whether a signature is valid or its certificate is trusted.
  • Dates and software names that someone changed on purpose. Anyone with the right software can write them.

What should I do with the result?

  • If edit traces were found, ask the sender or the issuer what changed and ask for the original file. A later version is a reason to ask, not a finding of fault.
  • If the result is "Can't tell from this file", ask for the file as it came from the system that created it, before anyone printed, converted or saved it again.
  • If no edit traces were found, treat that as one fact about the file. When money or rights depend on the document, confirm it with the issuer.

File limits and privacy

You can check one PDF at a time, up to the upload limit of your plan. Guests can check one file. Each successful check uses one of the 100 monthly uploads on a verified free account. The file is uploaded to our server and read while the request runs. The edit checker does not copy it into storage and does not save the result, which is shown in your browser only. A file that is password protected, damaged or too complex to read is not checked and leaves the upload available.

Last updated . Written from the checker's source code and from synthetic test PDFs built for the purpose: files saved once, saved again by an editor, signed and then changed, and rebuilt by Ghostscript.

Do more with a free account

Keep your report history, share reports by link, check several PDFs at once and use the API.