Home / Blog / Tutorials

"Document Altered or Corrupted Since It Was Signed": What Broke It

Form filling, PDF/A conversion, compression and "Save As" can all break a PDF signature. How signatures protect bytes, how to find what changed, and the safe order of operations.

Few PDF errors cause more alarm than a red X next to a signature and the message "Document has been altered or corrupted since it was signed". Sometimes it really is tampering. Far more often, a perfectly normal step in the workflow (filling a form field, converting to PDF/A, compressing the file, saving it again in another tool) rewrote bytes that the signature protects. This post explains how PDF signatures protect a file, which everyday operations break them, and the order of operations that avoids the problem.

How a PDF signature protects the file

A PDF signature does not sign "the document" in the abstract. It signs an exact range of bytes, called the ByteRange: everything in the file except the gap where the signature value itself sits. When Acrobat validates the signature, it hashes those same bytes again. If even one byte inside the range differs, the hash no longer matches and you get the red X.

So how can a PDF be signed by three people in turn? Through incremental updates. Each later change is appended to the end of the file, leaving the earlier bytes untouched. The first signature still covers exactly the bytes it covered before, and Acrobat then looks at what the appended updates changed and decides whether those changes were allowed.

That gives two very different outcomes:

What happened after signingWhat Acrobat shows
Changes appended incrementally and permitted (another signature, form fill where allowed, a comment)Valid signature, often with a note that the document has been changed since signing, listing the changes.
Changes appended incrementally but not permitted (for example content edited on a certified document set to "no changes")Signature flagged as invalid or with problems because of disallowed changes.
File rewritten from scratch by a tool (full save)Red X: "altered or corrupted since it was signed". The original bytes are gone.

Step 1: find out what changed

In Acrobat, open the Signature Panel, expand the failing signature and click View Signed Version (also available by right-clicking the signature). Acrobat opens the file exactly as it was when that signature was applied. You can then use Compare Files (Acrobat Pro) against the current file to see the difference. If the signed version will not open or looks broken, the file was rewritten rather than appended to.

The usual culprits

1. A tool saved the whole file again

Many programs do not know how to append. They parse the PDF and write a fresh copy. Typical examples:

  • "Save As" or "Save As Other > Optimized PDF" / "Reduce File Size" in a PDF editor.
  • Online compressors, mergers, page reorderers and watermarking tools.
  • "Print to PDF" (this produces a new, unsigned PDF; the signature appearance is just a picture).
  • Document management or email gateways that stamp a footer, add a barcode, or "sanitize" attachments.
  • Scripts that open and save the file with a PDF library in normal (non-incremental) mode.

Fix: make signing the last step. If something must happen after signing, the tool must support incremental save. For example, most PDF libraries have an "append" or "incremental" save mode that must be enabled explicitly when working with signed files.

2. Converting to PDF/A after signing

PDF/A conversion (preflight "fixups") embeds fonts, changes colour spaces and rewrites the document structure. On a signed file that necessarily invalidates the signature, and Acrobat may refuse to convert a signed or certified file at all. The correct order is:

  1. Create the final document.
  2. Convert it to PDF/A and validate it.
  3. Sign it. A signature added with an incremental update keeps the file PDF/A compliant as long as the signing tool writes a PDF/A compatible signature (embedded fonts in the appearance, no forbidden features).

3. Filling form fields after a certification signature

There are two kinds of PDF signatures. An approval signature is the normal kind. A certification signature (the "Certify" option in Acrobat, only one per document and it must be the first) also sets permissions for what may change afterwards. The PDF specification defines three levels:

  • No changes allowed: any later change, even another signature, breaks it.
  • Form fill-in and signing: filling existing fields and signing existing signature fields are fine.
  • Form fill-in, signing and annotations (commenting): comments are also allowed.

If a workflow certifies a contract with "no changes" and then sends it to the counterparty for their signature, the first signature will show as invalid after the second person signs. Fix: certify with "Form fill-in and signing allowed", or use ordinary approval signatures throughout.

4. Adding or changing fields after the first signature

Adding a new form field, deleting pages, rotating pages, or changing the value of a field that a signature locked are all modifications to signed content. Even when appended incrementally, Acrobat reports them as changes that invalidate the earlier signature. Fix: in a multi-signer document, create all fields and signature fields before the first signature, and let each signer only fill their own fields and sign their own signature field.

5. Corruption in transit

Less common, but real: FTP in ASCII mode, a script that reads the PDF as text and re-encodes line endings, or a system that strips trailing bytes. The fix is to transfer PDFs as binary and compare a hash (for example Get-FileHash file.pdf in PowerShell) before and after transfer.

6. A known enterprise Reader quirk

There is a report on the Adobe community forums of valid ECDSA signatures shown as altered on some enterprise builds of Acrobat Reader where the registry value bEnableCryptoComplyLibrary is set to 1, and validating normally when it is 0. If the same file validates on one machine and not another, compare Acrobat versions and this setting before suspecting the file.

The safe order of operations

  1. Finalize the content (text, pages, attachments).
  2. Convert to PDF/A if required.
  3. Add every form field and signature field that anyone will need.
  4. Fill the fields that belong to the first signer, then sign (or certify with form fill and signing allowed).
  5. Each later signer fills only their fields and signs, each time as an incremental update.
  6. After the last signature, nothing else rewrites the file. Archive it as is.

What you cannot do

A broken signature cannot be repaired. The only fix is to go back to an unsigned copy, apply the change, and sign again. If the signed file is all you have and you need a change, ask the signer to sign the corrected version. Keep unsigned originals for exactly this reason.

How OneSigner handles it

OneSigner appends every signature as an incremental update, so earlier signatures stay valid, and one signing profile can apply several signatures to the same document. In the eSign portal, all fields are placed before sending; each signer adds a new revision, fields for later signers are drawn as annotations that do not alter signed content, and the server re-verifies every signature after each step. The practical rule still applies: make OneSigner the last step in your pipeline, after any merging, compression or PDF/A conversion. See multiple signatures on one PDF and the eSign portal walkthrough.

Have a question about this?

Email the team that wrote it, and we will reply directly.