Signature requests

A signature request sends a PDF to up to 10 people to sign. The PDF is encrypted in your browser and uploaded once; each person gets their own link by email, confirms their address with a code, and signs in their browser. We never see the document or anyone's signature.

Sending a document

1. Choose the PDF. Up to 50 MB and 500 pages. A password-protected PDF cannot be sent; one that already carries a digital signature can, but signing makes a new copy that the old signature no longer covers.
2. Add the signers, one email address each, yourself included if you sign too. Choose Sign in this order to have each person sign only after the one before; otherwise everyone can sign at once.
3. Place the fields. Pick a signer and a kind of field (signature, initials, date, text or tick box), click where it goes, then drag it into place. To give a placed field to someone else, select it and choose them under Signer. Each signer needs at least one signature field.
4. Send. Choose how long the request stays open and whether to remind people who have not signed. Each signer is emailed their own link; it carries the document's key, as a shared file's link does.

From code and AI assistants

The command line sends a PDF for signature from your computer (share sign), placing the fields from tags in the PDF, from page coordinates, or at the end of the last page. An AI assistant can prepare a request for you, through the online connection or the tool on your computer, but never send one: it waits until you check the document and the fields in the browser and press Send. Code reads who has signed, reminds and cancels through the API. The document is encrypted where the request is made, so neither we nor the assistant ever see it.

What a signer does

The link opens a page that asks for a code sent to the signer's address, so a forwarded invitation opens nothing. The signer reads the document and fills in their fields one at a time: Start and Next, beside the document, take them to each one and count what is done. They make their signature once, then press each signature field to put it there; dates fill themselves in. Finish takes them to their name; they agree to sign electronically, and sign. Their browser checks that the document is exactly what the previous signer signed before it lets them sign. Reminders and the "your turn" email carry no link: they name the invitation to open.

A signer can decline instead, with an optional reason that only you and the signers can read. Declining ends the request for everyone, and the document is deleted.

Once everyone has signed

You and every signer can download the signed PDF and its completion certificate for at least 14 more days. The certificate lists who signed, when, from which IP address and browser, and the document's fingerprint before and after each signature, signed by us and stamped by an independent timestamp service.

Anyone can check a completion certificate, and that a PDF is the signed one, on the verify page, in their own browser, without an account.

What we can see

Who was asked to sign, in what order, and when each step happened, with each signer's IP address and browser. We cannot see the document, its name, where the fields sit, what anyone entered or any reason for declining. The label you add, if any, is the one thing about the document we can read.

What kind of signature this is

These are simple electronic signatures, valid for most agreements under the EU eIDAS Regulation and, in the United States, the ESIGN Act and UETA. Some documents need a handwritten, witnessed, notarised or qualified signature instead; check what yours needs.

Plans and limits

Pro sends 10 signature requests a month, Studio 100 and Business 500. A request whose upload was stopped is not counted. The document counts toward your storage while the request is open.