Sign
Open the app: Sign or verify a PDF → (products.documentize.app)
In one sentence
Sign applies a digital signature to your PDF using your own certificate file (.pfx) and its password, so that anyone can later check that the file is unchanged since you signed it.
What makes it unique
- It is a certificate-based digital signature, not a "draw your name" tool. There is no pen pad, no typed-name stamp, no image of a handwritten signature. The signature is cryptographic.
- You bring the certificate. Documentize does not issue certificates and does not keep yours. The
.pfxfile and its password are used to sign and are not part of what you download. - The same page also verifies signatures (a switch next to the Sign button). That mode has its own chapter: Verify Signature.
- It differs from Protector: a password hides a file; a signature shows it and makes later changes detectable. A signed file can be read by anyone, and does not need a password.
When to use it / when not to
- Use it to approve a contract, report or invoice as the last step before sending, so the recipient can detect any later edit.
- Use it with a company or personal certificate you already hold (a PKCS#12 /
.pfxfile). - Not when you only need a visual "signed by" mark or a scribble on the page. A cryptographic signature is not a picture of your handwriting.
- Not to collect signatures from several people in turns with invitations and reminders. This app signs with one certificate per run.
- Not for files you still need to edit. Any change after signing breaks the signature.
Before you start
- You need two things: the PDF (page set for up to 10 files per run; verify on the live app) and one
.pfxcertificate file with its password. - The signature will be placed by the app; you cannot choose its position (see below).
- Finish all editing, flattening and compression first. See "Works well with".
- Keep the file unencrypted if possible. The quick signing path is used only when the PDF has no open-password on it; for a protected file, unlock first (verify on the live app).
Step by step
- Open the Sign page and drop the PDF.
- Under Certificate, choose your
.pfxfile. - Type the certificate's password in the password field. Both the certificate and the password are required; the page stops with a message if either is missing.
- Keep the mode on Sign (the other choice, Verify, is described in Verify Signature).
- Press Sign, then download the signed PDF. Sign other files starts again.
📷 Screenshot placeholder: certificate picker, password field and the Sign / Verify switch.
Options explained
| Option | What it does | Default | Recommended |
|---|---|---|---|
| Certificate | Your .pfx (PKCS#12) file that holds your signing key | – (required) | Use your real, valid certificate |
| Password | Opens the certificate file | – (required) | The certificate's own password |
| Mode: Sign / Verify | Decides whether the page signs or checks | Sign | Sign for this chapter |
There are no options for page, position, reason, location or look. The code signs with a visible signature field on the first page (a 400 × 200 box starting at the page's lower-left corner). Check where it lands before sending (verify on the live app).
What you get
- A PDF identical in content to the original plus the signature. Several inputs come back as a ZIP ("Signed_Documents"); every file is signed with the same certificate.
- Your original is never changed; you get a new file.
- Anyone can open it. Tools such as Acrobat (and Verify Signature) can check it.
Quality & limits
- Signing does not touch the page appearance beyond adding the signature box.
- What a signature guarantees: the file has not changed since signing, and it was made with that certificate's key. What it does not guarantee: that the certificate is trusted by the recipient. A self-made certificate will be reported as untrusted by viewers such as Acrobat. Trust comes from who issued your certificate.
- No timestamp or long-term validation settings are offered here.
- Wrong certificate password gives an error and no output.
- Server time limits and a ~2 day retention of results apply, as for every app.
Works well with
- Use before: everything else. The safe order is edit → Flatten → Compressor → Protector → Sign, with the caveat in combos about protected files.
- Use after: Verify Signature, right away, as a self-check.
- Recipes: Contract round-trip.
Common mistakes & fixes
- "I signed, then compressed — now the signature is invalid." Compression rewrites the file. Sign last.
- "The certificate is rejected." The password may be wrong, or the file is not a
.pfx/PKCS#12 certificate with a private key. - "The recipient sees 'untrusted signer'." Normal for a self-signed certificate. Use one issued by a recognised authority, or have recipients trust it.
- "I wanted my handwritten signature image." This app does not do that.
Same thing elsewhere
- CLI plugin: Documentize.ESign: one PDF and one
.pfxin the input folder, plus the password. - MCP tool: SignDocument (file URL, input type). Check the tool's guide for how the certificate is supplied (verify).
- API: the
esignendpoint used by the web page. See Beyond the browser.
Try it
Make a test certificate with your operating system's or your company's tools (any .pfx file you control). Sign a one-page PDF with it, open the result in a viewer and find the signature box on page 1. Then run it through Verify Signature and confirm it says valid.