Paste text or drop a file to hash it — hashing runs locally in your browser, so nothing is ever uploaded.
How it works
- The SHA-1 and SHA-2 algorithms (SHA-256/384/512) are computed with the Web Crypto API — the same implementation browsers use for HTTPS. MD5, CRC32 and the SHA-3 family (SHA3-256/512) are implemented in JavaScript since browsers don't expose them, and all are verified against official test vectors.
- File mode hashes the exact bytes of an uploaded file — handy for verifying a download wasn't corrupted or tampered with, by comparing against a hash published by the source.
- The verification field checks your pasted hash against all four computed hashes (case-insensitive) and tells you which one, if any, matches.
- MD5 is intentionally not offered: it's cryptographically broken and shouldn't be used for anything security-sensitive. Use SHA-256 or higher.
- Nothing is uploaded anywhere — files and text are hashed entirely in your browser.
Generate MD5, CRC32, SHA-1, SHA-256, SHA-384, SHA-512 and SHA-3 (256/512) hashes from text or files, right in your browser. Useful for checksums, integrity checks and fingerprinting — with nothing uploaded.
Frequently asked questions
Which hash algorithms are supported?
MD5, CRC32, SHA-1, the SHA-2 family (SHA-256/384/512) and the modern SHA-3 family (SHA3-256/512). SHA-256 is the usual choice for file integrity; SHA-3 is the newest NIST standard; CRC32 is a fast non-cryptographic checksum.
Is it safe to hash sensitive data here?
Yes — hashing happens locally in your browser and nothing is sent to a server, so passwords or private files never leave your device.
Should I use MD5 for security?
No. MD5 and SHA-1 are fine for non-security checksums and deduplication but are considered broken for security purposes — use SHA-256 or stronger for anything security-related.
Can I verify a file's checksum?
Yes — hash the file and compare the result to the published checksum. If they match character-for-character, the file is intact and untampered.
About the hash generator
A hash is a fixed-length fingerprint of some data — the same input always produces the same hash, but you can't work backwards from the hash to the input. This tool generates common hashes (like SHA-256) of text or files, and can compare a file's hash against an expected value.
It runs entirely in your browser; your input is never uploaded.
Common uses
- Verifying a downloaded file matches the checksum a site published.
- Generating a stable fingerprint for a piece of text.
- Checking whether two files are identical without comparing them byte by byte.
- Producing a hash for use in a script or system that expects one.
Use it carefully
A hash proves data hasn't changed; it does not encrypt or hide it. Also, older hashes like MD5 and SHA-1 are broken for security purposes — don't use them to protect anything that matters, only for quick non-security checks. For passwords, a general-purpose hash is never enough on its own.
Understanding your results
You get a fixed-length string of hexadecimal characters — SHA-256 is always 64 characters, regardless of how big your input was. Change a single character of the input and the whole hash changes completely.
When you paste an expected hash to compare against, the tool tells you plainly whether it matches — a green match means the file is exactly what you expected; no match means it differs, even by one byte.
What's the point of comparing hashes?
If a download's hash matches the one the publisher listed, you know the file wasn't corrupted or tampered with in transit.
Which hash should I use?
SHA-256 is a solid default. Avoid MD5 and SHA-1 for anything security-related.
Is my file uploaded to hash it?
No. The hash is computed in your browser.
Related guide: Understand hashes and checksums →
Why hashes became digital fingerprints
A cryptographic hash converts input of varying length into a fixed-size digest. This made hashes useful for integrity checks: even a tiny change to input is intended to produce a very different digest.
Hashing is not encryption
Encryption is designed to be reversible with the appropriate key. A cryptographic hash is designed as a one-way transformation; there is no normal 'decrypt hash' operation.