Verify a signed PDF receipt
Check a PDFMergely signing receipt against its PDF, entirely in your browser.
How the check works
A PDFMergely signing receipt records the SHA-256 fingerprint of the signed PDF. This page recomputes that fingerprint from the file you provide and compares the two. A match proves the file is unchanged since it was signed. It is a self-certification made on the signer’s device, with nothing uploaded, so it establishes integrity and privacy, not identity, notarization, or a trusted timestamp.
Frequently asked questions
What does a match mean?+
It means the PDF is byte-for-byte the file the receipt was made for, so it has not changed since it was signed. The check recomputes the SHA-256 of the PDF in your browser and compares it to the value in the receipt.
Is anything uploaded?+
No. Both the PDF and the receipt are read on your device, the hash is computed locally with WebCrypto, and nothing is sent to a server.
Does a match prove who signed it?+
No. This is self-certified on the signer’s device: it proves integrity (the file matches its receipt), not identity. The timestamp is the signer’s own device clock, not a trusted timestamp authority, and there is no notarization.
What if it says no match?+
The file differs from the receipt. Either it was changed after signing, or the receipt is for a different file. Re-download the original signed PDF and its receipt and try again.
Where does the receipt come from?+
When you sign a PDF with PDFMergely you can download a .receipt.json alongside it. Keep the two together; this page checks one against the other.