SHA-256 and SHA-512 hash checker
Compute the SHA-256 and SHA-512 fingerprint of a file. It runs entirely in your browser, so the file never leaves your device.
Your file is hashed in your browser with the Web Crypto API. It is never uploaded.
What this does and does not tell you
This computes the SHA-256 and SHA-512 fingerprint of a file entirely in your browser. A fingerprint identifies the exact bytes of a file: the same bytes always produce the same hash, and any change produces a different one. It does not tell you anything about the content of the file, only its identity. SHA-256 is the mechanism US Federal Rule of Evidence 902(14) recognizes for tying a record to one exact file.
Common questions
Is my file uploaded anywhere?
No. The hash is computed locally with the browser's Web Crypto API, so the file never leaves your device. You can confirm this in your browser's network panel: no request is made.
Why two hashes?
SHA-256 is the common standard and is what ChronoVerify prints in every verdict and signed report. SHA-512 is included for workflows that require it.
How does this relate to a ChronoVerify report?
Every ChronoVerify verdict and signed report includes the SHA-256 of the analyzed file. Hash your copy here and compare it to the value in the report to confirm you are looking at the exact same file.
Is ChronoVerify C2PA conformant?
Yes. ChronoVerify is a C2PA Conformant Validator on the C2PA Conforming Products List, record 019f8a20-6452-7a43-b11b-59d0b0e4a84a, covering validation of JPEG, PNG, WebP and AVIF under C2PA specification 2.2. The list is public, so you can check the record yourself. It covers validation rather than generation: ChronoVerify reads and validates Content Credentials, it does not sign them.
A fingerprint pins the exact file. To see its capture time, provenance, and manipulation signals, run it through the full ChronoVerify verifier, or call the API to verify images at scale.
Try the free verifier