Signing guides
How to compare a signed PDF’s SHA-256 with its audit record
A file fingerprint helps check whether you hold the exact PDF bytes associated with a record. It does not identify the signer or decide whether a document is accepted. Use the correct completed file and the corresponding audit before comparing values.
DocAISign paid checkout is not currently enabled. Self-signing is free; check your available sends and the Pricing page before planning a request.
Select the signed file, not the original upload
The DocAISign audit can list fingerprints for the original file, the PDF before signing and the signed PDF. Compare the completed download with the Signed PDF entry. Comparing it with the unsigned-source fingerprint is the wrong test.
Save both records under a clear document reference. Keep working copies and originals separate so a similarly named attachment does not confuse the check.
Compute the fingerprint locally on Windows
Microsoft documents Get-FileHash for computing a file hash. In PowerShell, replace the sample path below with the exact completed PDF you downloaded. The command reads the file and reports its SHA-256; it does not upload the document or modify it.
Use the Hash value in the output, not the filename or path column. LiteralPath treats the supplied path as an exact filename, including characters such as square brackets.
Get-FileHash -LiteralPath 'C:\Documents\signed.pdf' -Algorithm SHA256Compare the complete value
Compare all hexadecimal characters with the audit’s Signed PDF value. Letter case does not change the value. A match indicates the same file content for this comparison, not formal identity verification, a certificate validation or a legal conclusion.
Keep the audit’s provenance in mind too. Two files supplied by an unknown person are not an independent trusted reference merely because a value matches. Obtain the records through the intended completion workflow.
A mismatch needs diagnosis, not an accusation
- Check the selected path and whether this is the completed version.
- Confirm the audit belongs to the same request.
- Compare against Signed PDF, not Original file.
- Check whether someone compressed, annotated, printed to PDF or resaved the copy.
- If available, download the original completed file again and repeat the local check.
Do not repair the original by resaving it
A visually identical PDF can have different bytes after processing. Preserve the completed original while investigating. Do not overwrite it with a reduced or edited version and expect the old fingerprint to describe the replacement.
If the document itself needs correction, use a clearly identified new version and the appropriate request process. If the problem is merely a changed working copy, keep that copy distinct from the original.
Keep the check private
A local hash command avoids uploading the PDF to an unrelated checker. When requesting support, start with the visible status and non-sensitive diagnostics. Do not post private signing links, document contents or an audit containing personal activity details in a public discussion.