Account

What new tool do you want?

PDF Tools

eSign a PDF with Multiple Signers (Free, No Upload)

Send a PDF for signature to several people: place signature boxes for each signer, then everyone signs in turn in their browser. When the last person signs, a signing certificate with an audit trail and SHA-256 fingerprints is added. No account, nothing uploaded.

How to use

  1. 1Open the PDF, add each signer, and click on the pages to place a signature box for each of them.
  2. 2Download the prepared PDF and send it to the first signer (by email or any file-sharing service).
  3. 3Each signer opens the file here, signs their boxes and sends the downloaded file to the next person. After the last signature, a certificate page is added automatically.

Frequently asked questions

Is my document uploaded anywhere?

No. Preparing and signing both happen in the browser. The signer list and history travel inside the PDF itself, so you pass the file along yourself.

Is this legally binding?

In the US (ESIGN Act, UETA), the EU (eIDAS simple electronic signature) and the UK, electronic signatures are valid for most contracts if everyone agrees to sign electronically. Wills, some real-estate deeds, court filings and certain notices need other formalities.

Can someone tamper with the signed file?

The certificate records a SHA-256 fingerprint of the document at each step, so anyone can check a copy against it with our Hash Generator. It's not a certificate-based digital signature, so it can't stop edits — it lets you detect them.

Can people sign in any order?

Yes — untick 'Sign in order' when preparing. With it ticked, only the next person in the list can sign.

Sources

How signing without a server actually works

There's no central account or database tracking who's signed — the envelope's state (the title, signer list, placed signature boxes, sequencing rule, and a unique ID) is embedded directly inside the PDF itself. Preparing the document writes this envelope data into the file; each signer who opens it with this tool reads that embedded state back out, adds their own signature, and the file is passed along by whatever means you choose — email, a shared drive, a messaging app. The tool is stateless between sessions; the PDF itself is the only record of where the signing process stands.

What 'sequential' actually restricts, and what it doesn't

When Sign in Order is checked, the tool's canSign logic only allows the next unsigned person in the list to sign — if signer 2 tries to sign before signer 1 has, the interface won't let them proceed, enforcing order at the application level. This is a workflow control, not a cryptographic one: it governs what this specific tool lets you do when opening the file through it, not a tamper-proof technical barrier against someone editing the embedded envelope data directly. Unticking it allows any remaining signer to sign in whatever order the file happens to reach them.

The honest limit: detecting tampering, not preventing it

Each signing step records a SHA-256 hash of the document's state in the certificate, so anyone can independently verify a given copy matches what was actually signed at each stage, using a hash comparison tool. This is fundamentally different from a certificate-based digital signature (the kind that uses a trusted certificate authority and PKI) — this tool's own FAQ states plainly that it cannot stop someone from editing a copy after the fact, it can only let a verifier detect that an edit happened if they check the hash. For documents where tamper-prevention rather than tamper-detection is required, a certificate-based signing service is the more appropriate tool.

Example: a 3-party freelance agreement signed in sequence

A freelance agreement needs signatures from the freelancer, the client, and the client's manager, in that specific order, since the manager's signature is meant to be a final approval after the client has already agreed. Preparing the envelope with all three names, placing one signature box per person on the signature page, and leaving Sign in Order checked produces a file that only lets the freelancer sign first — if the manager somehow received the file early and tried to sign, the tool would show them as 'Waiting' rather than letting them proceed out of turn. After the freelancer signs and forwards it, the client sees 'Can sign now' next to their own name, signs, forwards again, and only then can the manager finalize it — at which point the completed file gains its certificate page with all three SHA-256 fingerprints and the signing timestamps.

Related tools

More: PDF Tools