Glossary
What does a signed PDF’s document hash do?
Short answer: A document hash is a digest calculated from a file’s bytes. It helps you detect whether a later copy differs when compared with a trusted reference digest using the same algorithm. Use the completed file and its verification record together when you need to check whether an archived copy changed.
Worked example: original PDF and edited copy
- A team saves a completed SealSimple PDF and adds a stamp to a duplicate.
- Original PDF. The SHA-256 fingerprint should match the fingerprint recorded at completion.
- Stamped duplicate. The changed file should return a different fingerprint.
- Record which file was checked and keep the original with its completion record.
Pair integrity with context
A matching digest supports file integrity against the reference you trust. A file fingerprint on its own does not establish signer identity, intent or signature level. Use the associated evidence to check what happened during signing. SealSimple offers a completion record and a public verification tool.
Related pages
Try Sealsimple free.
Sources
- NIST Secure Hash Standard (FIPS 180-4), checked 19 November 2026
- SealSimple pricing and product FAQ, checked 19 November 2026
- SealSimple verification, checked 19 November 2026