File Hash / Checksum Generator (SHA-1, SHA-256, SHA-384, SHA-512)

No. The checksum is computed entirely in your browser with the Web Crypto API. The file is read locally with the FileReader/ArrayBuffer APIs and its contents never leave your browser, are never sent to a server, and are not logged. You can even use the tool offline once the page has loaded.

A checksum is a fixed-length cryptographic fingerprint of a file's exact bytes. Publishers list a checksum next to a download so you can confirm the file you received is bit-for-bit identical to the one they released. If a download is corrupted, truncated, or tampered with, even by a single byte, the checksum will not match.

SHA-256 is the common default and what most projects publish. SHA-384 and SHA-512 give a wider security margin and are also from the SHA-2 family. SHA-1 is included because some older releases still list it, but it is considered weak for security and should not be relied on for verifying authenticity.

The browser Web Crypto API does not expose MD5, and MD5 is cryptographically broken, so a matching MD5 no longer proves a file is untampered. For corruption checks prefer SHA-256; for authenticity always use SHA-256 or stronger.

Paste the checksum the publisher provided and the tool compares it, case-insensitively and ignoring surrounding spaces, against the matching algorithm it computed. A green badge means the values are identical; a red one means they differ, so the file is not the one you expected.

The whole file is read into memory as an ArrayBuffer and then hashed, so very large files are limited by your device's available memory and may take a moment. For typical downloads, archives and installers it is effectively instant.

This tool hashes one file at a time. To compare two files, hash the first, copy its digest, then hash the second and paste the copied value into the compare field. Identical files always produce identical checksums for the same algorithm.