Hash Report Generator
Turn a set of checksums into a verification certificate you can file, send or archive.
What this does
Most hash tools give you a string to copy. This one also produces a document: hash any number of files at once, then export a timestamped report listing every file, its size, its algorithm and its digest, under a unique report ID. Attach it to an audit, a handover, a legal bundle or a change record.
[1] SELECT FILE(S) TO HASH
Select one or multiple files to hash from your system, or drag and drop files below
[2] CHOOSE YOUR HASH FUNCTION
[3] LAUNCH THE HASHING PROCESS
What the report contains
- ›A unique report ID, so the document can be referenced later
- ›Generation timestamp with time zone
- ›Every file name, size and computed digest
- ›The algorithm used, stated explicitly on each entry
- ›A success and error count, so partial runs are visible
- ›Optional title, purpose, operator name and organisation
How to generate one
- Select every file that belongs in the report. You can pick many at once.
- Choose an algorithm. SHA-256 is the right default for anything that must hold up to scrutiny.
- Press [CALCULATE HASH] and let every file finish.
- Press [GENERATE REPORT], fill in the title, purpose and operator fields.
- Pick a format and download. The file is produced in your browser.
Available formats
| Format | Best for |
|---|---|
| Filing, printing, attaching to an audit or legal bundle | |
| CSV | Loading the digests into a spreadsheet or asset register |
| JSON | Feeding another system or a verification script |
| HTML | Sharing a readable report by email or intranet |
| TXT | Plain records, diffing, appending to a log |
Who uses this
Evidence and handover
Record the state of a set of files at a moment in time, before they move between parties, so any later change is demonstrable.
Audit and compliance
Attach a checksum manifest to a control, showing which artefacts were reviewed and exactly which versions.
Release engineering
Publish a manifest alongside a build so downstream consumers can confirm they received the same artefacts.
Archival
Store digests next to long-term backups so silent corruption can be detected years later.
Your files stay on your machine
Hashing and report generation both run entirely in your browser. No file, digest or report field is transmitted anywhere. That is what makes this usable for confidential material, and it also means the report is produced offline once the page has loaded.
FAQ
Is a hash report legally valid evidence?
A hash report is a record you produced; it is not a notarised or independently witnessed document. It demonstrates that a given file matched a given digest when you ran it, which is usually what a chain-of-custody process needs, but the evidentiary weight depends on your jurisdiction and process. Check with whoever owns the process.
How many files can one report cover?
There is no fixed limit. Select as many files as you need in one go; each appears as its own row with its own digest, and the report records how many succeeded and how many failed.
Which algorithm should the report use?
SHA-256 for anything that may be scrutinised. MD5 only if you are matching a legacy checksum, since it cannot prove a file was not deliberately altered.
Does generating a report upload anything?
No. The PDF is assembled in your browser and saved directly to your downloads. Nothing reaches a server at any point.