Hash Generator

For integrity checking of downloads, SHA-256 is the default answer and what I would recommend for almost every scenario. It is cryptographically secure, widely supported, and still fast enough to hash a multi-gigabyte file in seconds. MD5 and SHA-1 are both included because you still see them in older systems, for example Git uses SHA-1 internally and many legacy checksums use MD5, but neither should be used for security-sensitive work because both have been broken by researchers. Use them only when you need to match an existing hash someone else published. SHA-512 is worth reaching for when you are dealing with extremely large files or high-security contexts like archival signatures, since the longer output makes collisions even more statistically implausible. For most daily tasks, SHA-256 is the right choice.

No, and this is genuinely one of the best reasons to use this tool over a random online hasher. Your file never leaves your device at any point. The entire hashing process runs in your browser using the Web Crypto API, which is the same cryptographic engine that browsers use for HTTPS connections, so it is both secure and fast. You can verify this yourself by opening the Network tab in your browser DevTools before dropping a file in. You will see exactly zero upload requests during the hash calculation. This matters for files you would not want sitting on a random server, things like source code, private documents, or anything containing personal information. It also means the tool works fully offline once the page has loaded, and there is no file size limit imposed by server bandwidth or upload caps.

Drop your downloaded file into the tool and it will instantly compute MD5, SHA-1, SHA-256, and SHA-512 hashes for you. Compare the hash value against the one published by the original source, usually on the download page or in a file called SHA256SUMS or similar. If even a single character differs, the file has been modified or corrupted and you should not trust it. This is the standard way to verify Linux ISOs, software releases, and firmware images have downloaded correctly and have not been tampered with. The match has to be exact, byte for byte, with no capitalization differences ignored. Copy-paste both hashes into a diff tool if your eyes are getting tired after staring at hex strings too long.