Hash Generator
Hash text or a file with MD5, SHA-1, SHA-2, SHA-3, CRC32 or xxHash, and compare the result with an expected checksum. Files are read in chunks on your device and never uploaded.
Runs in your browser — nothing is uploaded.
Read on your device in 4 MB slices; up to 4 GB.
·
MD5, SHA-1, CRC32 and xxHash are not secure hashes: do not use them for passwords or to prove authenticity. Use SHA-256 or better for security, and bcrypt or Argon2id for passwords.
Paste a checksum to compare. Case, spaces and colons are ignored.
How to use it
- Type or paste text, or choose a file. Hashes of the selected algorithms appear straight away.
- Tick or untick the algorithms you want. Copy any hash with its button.
- To verify a download, paste the published checksum in “Expected hash”: the page tells you if it matches and which algorithm.
Frequently asked questions
Is my text or file uploaded?
No. Hashing runs in your browser with WebAssembly. A file is read in 4 MB slices inside a background worker, so large files do not freeze the page and never leave your device.
Can I use MD5 or SHA-1 for passwords or security?
No. MD5 and SHA-1 are broken for security purposes (collisions can be made on purpose), and none of the algorithms here is suitable for storing passwords because they are fast. Use bcrypt or Argon2id for passwords. MD5, SHA-1, CRC32 and xxHash are fine for spotting accidental corruption.
Which algorithm should I pick?
SHA-256 for checksums and integrity; SHA-3 if you specifically need it. CRC32 and xxHash are fast, non-cryptographic checksums for detecting transmission errors, not tampering.
Why is the hash of a text different from the file with the same text?
Text is hashed as UTF-8 exactly as typed; editors often add a trailing newline or use a different line ending or encoding in the file.
How big a file can I hash?
Up to 4 GB. Memory use stays small because the file is processed in slices.