Firmware Hash / Checksum Verifier
Calculate a trusted-reference checksum or compare two local files byte for byte, entirely on this device.
Use a trusted checksum when a publisher gives you a digest. Use two local files when you only need to know whether their bytes are exactly equal.
Choose a local file, then calculate its checksum.
Or drop one file anywhere in this workspace. Any file type, up to 50 MiB (52,428,800 bytes). Your file is never uploaded.
No file selected
Choose the same algorithm as the trusted value you are comparing against. Keep SHA-256 when no specific type is required.
Web Crypto reads the whole file into memory before hashing; this is not streaming. A separate worker keeps the page responsive. Cancel stops the worker, and Clear releases the selected file.
No file selected
No file selected
Each file may be up to 50 MiB. A worker reads both files in bounded 1 MiB chunks and stops as soon as it finds a difference. Unequal sizes are different without reading file contents.
Waiting for a file checksum
64 hexadecimal characters for SHA-256. Recognized SHA labels and two-character byte separators are normalized; ambiguous text is rejected.
No expected checksum entered. You can paste one to compare.
The download contains the hash only. Its extension matches the selected algorithm: .sha256, .sha384, or .sha512.
Waiting for two local files
“Byte-for-byte identical” means every byte and the file sizes match. It does not prove who created either file, whether either file is safe, or whether the contents are authentic.
ONE SMALL CHECK
Same bytes?
See for yourself.
Choose the comparison that matches your source.
For a publisher checksum, choose one file, use the published SHA algorithm, and paste the trusted digest. For two files already on your device, select both and compare their actual bytes. Changing modes or files discards old results; Cancel stops current work and Clear releases every selected file.
Equality is not authenticity.
A digest match checks a file against the value you supplied. A two-file match checks exact byte equality. Neither proves publisher identity or that a file is safe. MD5 and SHA-1 remain intentionally excluded from this verifier.
Web Crypto’s digest API requires the complete file in memory. Digest and exact comparison modes support empty files with a 50 MiB limit per file. Workers require a current browser over HTTPS.