All computation runs locally in your browser -- the file is never uploaded to any server

Drop the evidence file here, or click to browse

Audio · Video · Image · PDF · Document -- any file type

Select hash algorithms

hash_engine -- bash
Initialising...
Hash computation complete

Verify against a known hash

Generate Certificate -- The Schedule [See section 63(4)(c)]

Select which part you need to fill:

PART A

To be filled by the Party
Device owner / user / operator
Use this if you are submitting your own device's data (WhatsApp, calls, photos, DVR footage, etc.)

PART B

To be filled by the Expert
Forensic expert / cyber analyst
Use this if you are a certified expert who extracted/verified the evidence for court submission

Part A selected -- To be filled by the Party

Personal details
Device / Digital record source (tick mark)
Device was (select as applicable) -- by me
Algorithm used
Execution details

Part B selected -- To be filled by the Expert

Expert personal details
Device / Digital record source (tick mark)
Algorithm used
Execution details

Hash algorithms

MD5
128-bit · 32 hex chars
Fast integrity checks. Widely accepted in Indian courts.
SHA-1
160-bit · 40 hex chars
Common in older forensic tools and software.
SHA-256
256-bit · 64 hex chars
Recommended for modern legal filings. Strong collision resistance.
SHA-512
512-bit · 128 hex chars
Maximum strength for critical or high-value evidence files.
Legal basis: The Schedule [See section 63(4)(c)] of the Bharatiya Sakshya Adhiniyam, 2023 replaced Section 65B of the Indian Evidence Act, 1872. Part A is signed by the party producing the evidence; Part B is signed by the technical expert verifying it. Both require the hash value and algorithm to be stated. Attach the printed hash report to the signed certificate.
All hash computations run entirely in your browser using pure JavaScript (RFC 1321, FIPS 180-4).
No file data is transmitted. No server contact. No analytics. No cookies.