Verify Signature
Open the app: Sign or verify a PDF → (products.documentize.app)
In one sentence
Verify Signature opens a PDF, finds its digital signatures, and tells you whether each signature is still intact — that is, whether the file has stayed unchanged since it was signed.
What makes it unique
- It is a mode of the Sign page, not a separate page: on the Sign page choose Verify instead of Sign. (Behind the scenes it is its own job, which is why it has its own chapter, CLI plugin and MCP tool.)
- It needs no certificate and no password from you. You only upload the signed file.
- Besides the verdict it shows a small document card (title, author, subject, keywords, creation date, producing application, PDF producer, page count, PDF version, file size, whether it is encrypted and whether it is PDF/A). This is handy for a quick sanity check of an unfamiliar file.
- It is honest about what it checks: integrity of the signature. It does not show who the signer is or whether you should trust them (see Quality & limits).
When to use it / when not to
- Use it to check a contract you received, or your own signed file after processing.
- Use it as a gate in a chain: after any step that might rewrite the file.
- Not to find out who signed. The result lists signature field names, not the signer's identity or certificate details.
- Not to judge whether a certificate is trustworthy. Use your PDF viewer's signature panel for that.
- Not to check a Word document. Only PDFs are taken.
Before you start
- Have the PDF exactly as you received it. Do not re-save, print-to-PDF or compress it first, or you destroy the thing you are testing.
- If the file is encrypted, unlock it first, but note that unlocking may itself invalidate the signature. Check the original in your viewer in that case.
- Verify one file at a time. If you upload several, only the first is reported (verify on the live app).
Step by step
- Open the Sign page and drop the PDF.
- Switch the mode to Verify. The certificate field is not needed for this mode.
- Press the button. The page shows a result panel.
- Read the verdict, then the document card below it.
- Press Validate another file to check the next one.
📷 Screenshot placeholder: a green "All signatures are valid" panel and a red failure panel.
Options explained
| Option | What it does | Default | Recommended |
|---|---|---|---|
| Mode: Verify | Checks signatures instead of adding one | Sign is preselected | Choose Verify |
There are no other options.
What you get
No file to download — the answer appears on the page.
- Green: "All signatures are valid", followed by the list of verified signature names.
- Red: "Document is not signed!" when the PDF has no signature at all.
- Red: "Document signature '…' is not valid." naming the first signature that failed. Usually the file was edited after signing, or damaged in transit.
- The document card in every case. Your file is not changed or stored as a new document.
Quality & limits
- It checks that each signature still matches the content it covers. Valid means "unchanged since signing", nothing more.
- It does not tell you the signer's name, whether the certificate was issued by a trusted authority, whether it had expired, or when it was signed. For those, open the file in a full PDF viewer.
- A file that is "not signed" is not necessarily forged; it may simply never have been signed. A file that fails may be broken rather than tampered with.
- A single failing signature gives a failing verdict; you are told which one.
- Results are processed on the server; standard retention (about two days) and time limits apply.
Works well with
- Use before: nothing; usually the last step.
- Use after: Sign (self-check), or any edit step in a chain to confirm it did not break the signature.
- Recipes: Contract round-trip.
Common mistakes & fixes
- "It says not signed but my viewer shows a signature." The mark may be a picture of a signature, not a cryptographic one.
- "It says invalid right after I compressed." Expected. Compression rewrites the file; sign afterwards.
- "I verified a printed-and-scanned copy." A scan has no signature. Verify the original digital file.
- "Valid, so I trust the sender." Valid only means unchanged. Confirm the signer's identity separately.
Same thing elsewhere
- CLI plugin: Documentize.VerifyESign (one PDF in the input folder; no password).
- MCP tool: VerifySignature (file URL).
- API: the
verify_esignendpoint used by the web page. See Beyond the browser.
Try it
Sign a PDF with Sign and verify it: green. Now take the signed file, open it in an editor that re-saves PDFs (or run it through Compressor), verify again, and see the red message. This two-minute experiment teaches the whole point of signature order.