Hash Generator
Generate MD5, SHA-1, SHA-256, SHA-512, SHA-3, CRC32 and HMAC hashes of text or files at once. Verify checksums locally — nothing is uploaded.
🔒 Runs entirely in your browser — nothing is uploadedWhat Hash Generator does
Hash Generator computes many digests of the same input in a single pass: MD5, SHA-1, SHA-224, SHA-256, SHA-384, SHA-512, SHA3-256, SHA3-512, Keccak-256, RIPEMD-160, BLAKE3 and CRC32. Developers use hashes to compare values, publish and verify download checksums, build cache keys and ETags, check webhook signatures, and create deterministic references in tests. Text is encoded as UTF-8 before hashing, so the result matches what sha256sum, md5sum or a server-side library produces for the same bytes.
Switch to File mode to hash any file — an ISO image, an installer, a ZIP archive or a database dump. The file is streamed in chunks, so even multi-gigabyte files work without freezing the tab. Paste the checksum published by a vendor into the compare box and the matching row lights up green, which is the quickest way to confirm that a download is complete and untampered. Output can be shown as lowercase hex, uppercase hex or Base64, which is the format used by Subresource Integrity attributes and many cloud storage APIs.
Private browser-based workflow
All processing happens with in-browser JavaScript and WebAssembly. The tool does not upload your text, files, keys or generated values to a server, and it does not require an account. That privacy model is important because small utilities often receive real API responses, configuration samples, logs, authentication data, or customer-shaped examples during troubleshooting. Keeping the work local reduces risk and also makes the tool feel instant because there is no network round trip.
Practical tips
SHA-256 is the best default for most new checksum and integration work. SHA-384 or SHA-512 may be required by specific protocols, SHA-3 is the newer NIST standard, and BLAKE3 is the fastest option for large files. MD5 and SHA-1 are still common for legacy checksums and cache keys, but collisions can be crafted, so never use them for signatures or passwords. CRC32 only detects accidental corruption. Keccak-256 is the pre-standard variant of SHA3-256 used by Ethereum, so the two give different results.
For webhook verification, enable HMAC, paste the shared secret and compare the HMAC-SHA256 output with the signature header your provider sends. Remember that general-purpose hashes are the wrong tool for storing passwords — use a slow, salted algorithm such as bcrypt, scrypt or Argon2 for that.
How to use
- Enter text or drop a filePaste the exact text to hash, or switch to File mode and choose any file.
- Pick algorithmsTick MD5, SHA-256, SHA-3, CRC32 or any other algorithm; optionally enable HMAC with a secret key.
- Copy or verifyClick a digest to copy it, or paste an expected checksum to see which algorithm matches.