Why generate all hashes at once? ▾
Generating all hashes simultaneously is useful when: comparing a value against an unknown algorithm's output, generating multiple checksums for the same file in one operation, fingerprinting data across multiple identifiers, or testing how a particular input hashes across algorithms. Computing all 10 at once is no slower than computing them separately because the file is read into memory once.
Which of these hashes is the most secure? ▾
SHA-512 and SHA-384 provide the highest security margins (256-bit and 192-bit collision resistance respectively). SHA-256 and SHA-224 are secure for all practical purposes with 128-bit and 112-bit collision resistance. MD5 and SHA-1 are cryptographically broken — collisions are practically findable. CRC-32, Adler-32, FNV-1a, and DJB2 are non-cryptographic and provide no security.
Are the file hashes computed locally or uploaded? ▾
Computed locally — your file never leaves your browser. The file is loaded into memory using the FileReader API, then all 10 hash algorithms are applied to those bytes in your browser. No upload, no server processing, no logging. This makes the tool safe to use with confidential or sensitive files.
What is the maximum file size I can hash? ▾
There is no hard server limit because hashing is client-side. The practical limit is your device's available memory — the file is loaded into a single in-memory buffer. Most laptops handle files up to ~500 MB without issues. For multi-gigabyte files, you may hit browser memory limits; in that case use a command-line tool like sha256sum.
Why do I get different hashes for the same file on different systems? ▾
The hash should be identical for the same bytes on any correct implementation. Differences usually indicate: (1) Different files (one has trailing whitespace, line-ending differences CRLF vs LF, BOM markers, or different metadata). (2) Different algorithms accidentally selected. (3) Encoding differences for text input (UTF-8 vs UTF-16). To eliminate ambiguity, hash the raw file bytes (use the File tab here) and compare against sha256sum filename.
Can I use these hashes to verify Linux/Windows/macOS downloads? ▾
Yes. The SHA-256 produced here is identical to what sha256sum (Linux/macOS), CertUtil -hashfile SHA256 (Windows), or shasum -a 256 (macOS) would produce. Drop the downloaded file into the File tab, then compare the SHA-256 row with the published checksum. If they match exactly, the file is authentic.
What is the difference between the SHA-2 family algorithms? ▾
The SHA-2 family includes SHA-224, SHA-256, SHA-384, and SHA-512. SHA-256 and SHA-224 use 32-bit operations and share the same internal design (SHA-224 is SHA-256 truncated). SHA-512 and SHA-384 use 64-bit operations and share a different internal design (SHA-384 is SHA-512 truncated). On 64-bit CPUs, the 512-family is often faster. On 32-bit or hardware-accelerated systems, the 256-family may be faster. Security increases with output size: SHA-224 < SHA-256 < SHA-384 < SHA-512.