Workflow, step by step

Sign a PDF and email it: what holds up and what does not

Yes, you can sign a PDF and email it — in both the EU and the US the law refuses to treat a signature as invalid merely because it is electronic. The question that actually matters is what the emailed file can prove about itself.

The evidence gap in a plain emailed PDF

A PDF that was printed, signed by hand, scanned and emailed carries no binding between the signature and the file's contents: nothing proves which bytes the signer agreed to, nothing proves the file was not edited after signing, and nothing dates the act except mail headers. Identity rests on 'the email came from their address' — an assertion anyone who has seen a spoofed email will discount.

Admissibility is not the standard you should optimise for. The standard is: can you prove it, cheaply, when it is contested?

What a sealed envelope's email carries

When the signing happened through a service rather than a scanner, the delivered email can carry a materially different file: a PDF with the signer's PAdES signature over the exact signed bytes, an RFC 3161 trusted timestamp when an authority is configured, the certificate chain, and — at B-LT — the validation data embedded in the file. Plus a verification link whose code is printed in the evidence certificate, so any recipient can check the whole pack without an account.

The email then becomes delivery confirmation rather than the proof itself: the file it carries does its own proving.

Check a returned PDF before you rely on it

Whichever way a signed PDF reaches you, the check is the same and takes minutes: open it in a PAdES-aware validator (Adobe Reader's signature panel, or the EU's open-source DSS validator), see whether the signature covers the whole document, whether the chain validates, and whether the timestamp is present. If a document will matter later, those three facts are worth confirming on receipt — before the dispute, not during it.

Sources

  • Regulation (EU) No 910/2014, article 25 — CELEX 32014R0910.
  • ESIGN Act, 15 U.S.C. §7001(a) — govinfo.gov.
  • ETSI EN 319 142-1 — PAdES digital signatures; cited by name, paywalled standard.
  • RFC 3161 — TSP Time-Stamp Protocol (Adams, Cain, Pinkas, Zuccherato, 2001).

This is an explanation of workflow and law, not legal advice.

Read next

How to verify a signed PDF — and read the verdict

The check, step by step, verdict by verdict.

Acrobat shows an unacceptable signature banner? Install the Signattio trust root once

When the validator asks about the signing root — the one-time fix.

How Signattio works: from draft to verifiable PDF

What happens between 'send' and the sealed file.