Sign with certificate
Add a verifiable digital signature from your .p12 or .pfx certificate.
Sign with certificate adds a digital signature (PAdES) from your .p12 or .pfx certificate file. PDF readers can confirm that what you signed hasn't changed, and anything added to the PDF afterwards is kept separate from it.
Your key stays in your browser
The certificate file and its password are handled in a sealed-off panel inside the dialog that can't reach the network. Your private key never leaves your browser and is never uploaded or stored: Vellum hands that panel a fingerprint of the document and gets back only the signature. The certificate locks again after each signature, and after 5 minutes of inactivity.
Signing a document
- 1Open the dialog
Open Share in the toolbar, choose Export and document tools, then Sign with certificate under Document, or find it with
⌘K. - 2Unlock your certificate
Choose your .p12 or .pfx file and enter its password (no certificate yet? See Create a certificate). If the certificate is self-signed, the dialog warns you: recipients' PDF readers show such a signature as untrusted, with the signer's identity unknown, unless they choose to trust your certificate.
- 3Choose the signature type
Approval, Certify: comments OK or Certify: no comments (see below). Optionally add a Reason and a Location.
- 4Choose the appearance
Text only (the default), Maine PE seal (enter your name and license number; it's drawn at 1.75 in with the date beside it), Seal image (a PNG or JPEG placed at 1.75 in) or Invisible. A seal also needs you to confirm that you are the licensed professional named on it; the box clears each time the seal changes. If the name on the seal isn't the certificate's name, the dialog says so: the signature identifies the certificate's holder. For a visible signature, pick the page and the corner.
- 5Choose what you sign
Turn on Include my markups as editable annotations to sign the PDF with your current markups in it, or leave it off to sign the PDF as uploaded.
- 6Sign & download
Vellum signs, checks the signature and downloads the signed PDF.
Create a certificate
No certificate yet? Click Create one under the password field to make a self-signed certificate. Enter the name to show on your signatures and, if you like, your organization and email. Choose how long it's valid (5 years by default) and set a password of at least 8 characters, using unaccented letters, numbers, spaces and keyboard symbols so a Mac can open the file too.
- Save the file before you sign with it. Click Save certificate file, then Use it to sign. Vellum doesn't keep a copy and can't recover the password: if you lose either, create a new certificate.
- The file is a standard .p12 digital ID, protected by your password, with a 3072-bit RSA key that can only sign. It's created inside the same sealed-off panel, so the key and password never reach Vellum.
- A self-signed certificate proves the document hasn't changed since you signed it, but nobody vouches for who you are. For signatures that recipients' PDF readers trust on their own, use a certificate from a certificate authority their PDF readers already trust.
Approval or certify
| Type | Use it when | What recipients can do afterwards |
|---|---|---|
| Approval | You approve this version, as when signing a drawing set. | Add markups and further signatures without breaking yours. |
| Certify: comments OK | You're the author and want to lock the content but allow review. | Fill forms, add comments and sign. |
| Certify: no comments | The document must not be marked up. | Fill forms and sign. Any comment or markup breaks the certification. |
Only the first signature can certify a document. If the PDF already has a signature, only Approval is offered, and your signature is added after the existing ones, which stay valid.
Signed documents in Vellum
When you open a signed PDF, a Signed pill appears in the toolbar. Click it to see each signature: who signed, when, the reason, the type and the issuer, with a status:
- Valid: the document is unchanged since it was signed and the signer's certificate checks out.
- Valid, signer not verified: the document is intact, but Vellum can't confirm who signed (for example, a self-signed certificate).
- Changed after signing: later revisions were added to the file; the pill says what they contain.
- Invalid: the signature doesn't match the document.
Exporting a signed PDF
Vellum never breaks a signature silently. What you get depends on the export:
- Editable export: your markups are added after the signatures, which stay valid. On a document certified with no comments, markups can't be added without breaking it, so you get an unsigned copy.
- Nothing new to add: you get the signed original, unchanged.
- Flattened export, print, headers and footers, watermarks, flattened form fields or changed pages: these change what was signed, so the result is an unsigned copy. Before a flattened export or a print, Vellum asks first.
An unsigned copy has its signatures removed (their appearance stays, so the sheet still reads the same), and every page is labelled UNSIGNED COPY: changed after signing with the signers' names. Its file name ends in _unsigned-copy. The signed original isn't changed.
A PDF reader shows a signature from a certificate it doesn't already trust as untrusted, or of unknown validity, until the recipient trusts that certificate. To make that easy, unlock your certificate, choose Save public certificate (.cer) and send them that file: it holds no key. The document itself is intact.