The Difference Between a Signature Image and a Legally Binding E-Signature

"Sign the PDF" means two genuinely different things depending on who's asking, and conflating them is where a lot of confusion — and occasional real legal risk — comes from. One meaning is cosmetic: draw or type your name, place it where a signature line would normally go, done. The other is cryptographic: apply a digital signature that mathematically binds a specific identity to the exact bytes of that document at that moment, in a way that can be independently verified and that breaks visibly if the document is altered afterward. These are not two strengths of the same thing. They're different tools that happen to look similar on a printed page.

What a drawn or image signature actually is

Placing a signature image on a PDF — whether it's a scan of your handwritten signature, a typed script-font rendering of your name, or a mouse/touch-drawn squiggle — is, structurally, identical to what happens when you drop a company logo onto a page. It's a raster or vector image object, referenced by the page's content stream, placed at a set of coordinates. Nothing about the PDF format treats that image differently because it happens to resemble a signature. There's no built-in verification, no cryptographic binding to your identity, and critically, no tamper-evidence: someone could copy that same signature image out of the PDF and paste it onto a completely different document, and there would be nothing in the file format itself that flags this as fraudulent. The image doesn't know what document it's "supposed" to be attached to.

That doesn't make it useless — it makes it exactly as trustworthy as a signature on a faxed form, which is to say: fine for a huge range of everyday situations. Initialing an internal approval form, signing a low-stakes agreement between parties who already trust each other, acknowledging you've read a policy document — these don't typically require cryptographic non-repudiation, they require a visible mark showing intent, and an image-based signature does that job well.

What a PAdES digital signature adds

PAdES (PDF Advanced Electronic Signatures) is a real cryptographic signing standard built on top of the same public-key infrastructure used for HTTPS certificates. Signing a document this way involves a certificate — issued by a trusted authority, or in enterprise settings by an internal PKI — that's cryptographically bound to your identity, and the signing process produces a hash of the document's exact contents at signing time, encrypted with your private key and embedded into the PDF itself as a proper signature object (not an image). Anyone with the right verification tooling can then confirm two separate things: that the signature really was produced by the private key belonging to the claimed identity, and that the document hasn't changed by so much as a single byte since the moment it was signed. Alter the document afterward — even something as small as a typo fix — and the signature verification fails outright, flagged clearly by any compliant PDF viewer.

This is the mechanism behind "this document has been modified since it was signed" warnings that show up in tools like Adobe Acrobat on properly-signed contracts. It's also why PAdES signatures typically embed a timestamp from a trusted timestamp authority — proving not just who signed, but exactly when, independent of the signer's own system clock, which matters a great deal in disputes over contract precedence or deadline compliance.

Where the legal line actually falls

Frameworks like the U.S. ESIGN Act and eIDAS in the EU generally recognize a spectrum rather than a single bright line: a "simple" electronic signature (which can be as basic as a typed name or a checkbox confirming intent) is legally valid for most everyday contracts, precisely because contract law has always cared more about demonstrated intent than about the specific mechanism of assent. But certain categories — real estate transfers in many jurisdictions, some wills and powers of attorney, court filings, and high-value regulated financial agreements — often require a higher assurance tier, sometimes explicitly mandating a "qualified" electronic signature backed by a certificate issued through a formally accredited process. The practical rule of thumb: if the document would traditionally have needed a notary or witness, an image-based signature almost certainly isn't sufficient on its own, and you should be looking at a proper digital signing service rather than a drop-an-image tool.

Why this site's signature tool is the cosmetic kind

The Add Signature to PDF tool on this site draws, types, or places an uploaded signature image onto a page — it does not issue a certificate, does not perform cryptographic signing, and does not produce anything that would satisfy a PAdES verification check. That's a deliberate scope decision, not an oversight: cryptographic signing requires a certificate authority relationship and identity verification that a browser-only, no-account tool structurally can't provide, and pretending otherwise would be actively misleading for exactly the high-stakes documents where it matters most. For initialing a form, approving an internal document, or any agreement where both sides are comfortable proceeding on a visible mark of intent, a placed signature image is the right, proportionate tool. For anything where you'd traditionally reach for a notary, that's a strong signal you need certificate-based signing instead.