Calculate MD5, SHA-1, SHA-256, SHA-384, SHA-512, CRC-32 and CRC-64 of text or a file at once. Results update as you type, and nothing leaves your browser. Use it to verify a downloaded file against a published checksum or to get a quick fingerprint of some data.
A hash function turns data of any size into a short, fixed-length value called a digest or checksum. The same input always gives the same hash, and even a one-byte change produces a completely different result, which makes hashes useful for checking that a file has not been corrupted or altered. This tool calculates seven common hashes and checksums for the text or file you provide, all at the same time.
To verify a download, drop the file and compare the value with the checksum published by the provider (for example the SHA-256 listed on a release page).
| Algorithm | Length | Notes |
|---|---|---|
| CRC-32 | 8 hex digits | Error-detection checksum used by ZIP, GZIP and PNG; not for security |
| CRC-64 (XZ) | 16 hex digits | The CRC-64/XZ variant used by the xz format; not for security |
| MD5 | 32 hex digits | Still common for file checksums, but broken for security purposes |
| SHA-1 | 40 hex digits | Used by Git; collisions are practical, avoid for new security uses |
| SHA-256 | 64 hex digits | The usual choice for checksums and signatures today |
| SHA-384 | 96 hex digits | SHA-2 family, truncated SHA-512 |
| SHA-512 | 128 hex digits | SHA-2 family, longest output |
For the text hello (UTF-8, no trailing newline):
3610a6865d41402abc4b2a76b9719d911017c592aaf4c61ddcc5e8a2dabede0f3b482cd9aea9434d2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824No. Hashes are calculated in your browser, so you can safely check private files. The file is read into memory, so very large files (several GB) may be slow or fail depending on your device.
The most common cause is invisible differences in the input, such as a trailing newline, Windows line endings (CRLF vs LF) or a different text encoding. Hashing the file itself instead of pasted text avoids most of these problems.
No. MD5 and SHA hashes are designed to be fast, which makes password guessing fast too. Use a dedicated password hashing algorithm such as bcrypt, scrypt or Argon2.
No. Hashes are one-way. Short or common inputs can still be found by guessing, which is why MD5 "decrypt" sites exist.