Is a signed PDF legally binding? (What actually counts)

Yes, a signed PDF can be legally binding — but the signature itself is rarely what makes or breaks it. In the UK and EU, and in the US under ESIGN and UETA, an electronic signature on a PDF is capable of forming a valid contract. The real question is not "is it signed?" but "can you prove it?" A typed name or a pasted signature image on a PDF is legally an electronic signature, yet on its own it carries almost no evidence of who signed, whether they intended to, or whether the file was altered afterwards. This article explains when a signed PDF holds up, when it is weak, and how to make one genuinely provable.

A signed PDF is legally an electronic signature

Under UK and EU law (the eIDAS framework and, in the UK, the Electronic Communications Act 2000 and the Electronic Signatures Regulations), and under US federal ESIGN and state UETA rules, a signature will not be denied legal effect simply because it is electronic. A name typed into a PDF, a signature drawn with a mouse or finger, an image of your handwritten signature pasted into the document, or clicking "I agree" can all count as an electronic signature.

So in principle a signed PDF is binding for the vast majority of everyday business agreements — engagement letters, statements of work, NDAs, supplier terms, consultancy contracts and the like. If you want the underlying legal position in plain English, see our guide on whether electronic signatures are legally binding.

But "capable of being binding" is not the same as "will survive a challenge." Legal effect and evidential weight are two different things — and a PDF is often strong on the first and weak on the second.

Typed names and pasted images: binding, but fragile

Imagine the two most common ways people "sign" a PDF:

• Typing a name into a form field, or adding it as text.
• Pasting an image of a handwritten signature — often the same scanned JPEG reused on every document.

Both are electronic signatures. Both can form a contract. The problem is what happens if the other side later says "I never signed that" or "those weren't the terms I agreed to." Ask yourself:

• Who actually applied it? Anyone with the file can type a name or drop in a signature image. There is nothing tying it to a specific person.
• Did they intend to sign? A name in a document does not, by itself, show the person meant it as their signature to those exact terms.
• Has the document changed since? A plain PDF can be edited. Text can be swapped, a page substituted, a figure altered — often with no visible trace.
• When was it signed? File timestamps can be changed and prove little on their own.

None of this makes a typed or pasted signature worthless. In a friendly, undisputed deal it may never matter. But if there is money, a deadline or a fallout involved, a bare signed PDF gives you very little to stand on. The same weakness applies to a scanned wet signature: scanning a signed page turns ink into pixels, and a pixel image is trivial to lift and reuse. It is legally a signature, but evidentially thin.

When a signed PDF holds up — and when it's weak

A signed PDF tends to hold up when:

• Both parties acknowledge the agreement and behave as though it is in force.
• There is a clear surrounding trail — emails, invoices, delivery, payment — showing the deal was real and acted upon.
• The stakes are low enough that neither side has reason to dispute the mechanics.

A signed PDF tends to be weak when:

• One party denies signing, or claims someone else did it without authority.
• The terms themselves are disputed and the file could plausibly have been edited.
• There is no record of the signing event — no log of who opened it, from where, or when.
• The signature is a reused image that appears, identically, across many unrelated documents.

The pattern is clear: what protects you is not the visual signature, but the evidence around it.

The missing piece: provable evidence

A signature that stands up to challenge answers four questions with evidence, not assertion:

• Identity — who signed, verified in some way rather than simply asserted.
• Intent — a clear, recorded act of agreeing to these specific terms.
• Integrity — proof the document has not changed since signing (tamper-evidence).
• Audit trail — a time-stamped record of the whole event: when it was opened, viewed, and signed, and from where.

This is the difference between a simple electronic signature and a properly evidenced one. It is also the difference people often mean when they compare an electronic signature with a digital signature — the latter uses cryptographic techniques to seal the document so any later change is detectable. A plain PDF with a pasted image has none of that sealing; a properly audited e-signature does.

How to make a PDF signature genuinely provable

If you want a signed PDF that will actually help you if it is ever questioned, build in evidence from the start:

• Capture a clear act of intent. The signer should take a deliberate step to agree to the specific document, not just have their name appear on it.
• Verify the signer. Even lightweight verification — a unique link to a named person, confirmation of their email, a record of the device and location — is far stronger than an anonymous typed name.
• Seal the document against tampering. Once signed, the file should be locked so that any later change is detectable. This is the tamper-evidence that turns "trust me" into "check for yourself."
• Keep a complete audit trail. Record every step — sent, opened, viewed, signed — with timestamps, and store it with the document.
• Produce a certificate of completion. A summary that travels with the agreement, setting out who signed, when, and how, gives you something concrete to point to.
• Make it independently verifiable. The strongest position is one where anyone can confirm the document is genuine and unaltered without taking your word for it.

This is exactly the gap Signet is built to close. Clients sign in one tap with no account and no login, and every agreement comes with a tamper-evident audit trail, a certificate of completion, and a publicly verifiable seal anyone can check. It is aligned with eIDAS, ESIGN and UETA, with UK and EU data residency, and your documents are never used to train AI — you can read more on our security page. If you prefer to work with plain PDFs, our walkthrough on how to sign a PDF online covers the basics.

The bottom line

A signed PDF is legally capable of binding you — but a typed name, a pasted image or a scanned signature is only as good as the evidence behind it. When nobody disputes the deal, that may be plenty. When someone does, the signature you can prove is worth far more than the signature you can merely see. If an agreement matters, sign it in a way that captures identity, intent, integrity and a full audit trail from the outset.

This is general information, not legal advice. For your specific situation, consult a qualified professional.

Signet is in private beta, request early access and send your first sealed agreement free.