---
title: "Validating Documents"
space: "Frappe Sign Documentation"
url: "https://eben.isambane.co.za/frappe-sign-docs/validating-documents"
updated: "2026-08-06"
---


# Validating Documents

Anyone who receives a Frappe Sign document - a signed PDF, a certificate-signed final package, or the audit certificate itself - can independently confirm it's genuine, without needing any special access to the sending organisation's Frappe site.

Open the **Frappe Sign Validator** page (in the workspace sidebar) and upload the file:

![The Validate Signed PDF page: upload the signed document PDF, and optionally the audit certificate PDF](/files/fsign-validator-page.png)

The validator computes the uploaded file's hash **in memory** - it never needs to save the file - and checks it against Frappe Sign's own records:

```text
Frappe Sign Request.signed_pdf_hash
Frappe Sign Request.certificate_signed_pdf_hash
Frappe Sign File Hash.sha256_hash
Frappe Sign Certificate.signed_pdf_hash
Frappe Sign Certificate.final_pdf_hash
```

A match returns the full picture: which request it belongs to, its status, who signed it and when, the audit chain hash, and a breakdown of each individual check performed:

![Validation Passed - matched request details, signer list, and a table of individual validation checks all Passed](/files/fsign-validator-result.png)

If the file has been altered since it was generated, the hash simply won't match, and validation fails - which is exactly the same mechanism **Tamper Detection** uses automatically, on a schedule, for documents already stored in your own site.