About this tool
A hash maps data of any length into a fixed-length "fingerprint". The same input always yields the same result, yet changing even a single byte produces a completely different output. This tool computes MD5, SHA-1, SHA-256 and SHA-512 of text or files — most commonly to verify that a download is complete and untampered, or to generate a unique identifier for a piece of content.
The SHA family is computed with the browser’s native Web Crypto (crypto.subtle), and file hashes are read and computed locally, so content is never uploaded. To be clear: these are integrity-checking hashes, not a scheme for storing passwords. MD5 and SHA-1 in particular are broken for collision resistance and must never be used for security (signatures, password storage). Store passwords with purpose-built slow, salted algorithms like bcrypt, scrypt or Argon2.
How to use
- Choose your input: paste text, or select/drop a file.
- Pick the algorithm(s) to compute (MD5, SHA-1, SHA-256, SHA-512 — view several at once).
- The tool computes and shows the hash as a hex string instantly.
- To verify a file, compare the value character-for-character against the official checksum.
- Copy the hash with one click for records, comparison or a checksum field.
When to use it
- After downloading software or an image, check the SHA-256 checksum to confirm the file is complete and untampered.
- Generate a fingerprint for an uploaded file to deduplicate, or to test whether two files are byte-identical.
- Verify a transfer did not corrupt data by comparing the hash on both ends.
- Record a unique identifier for a specific version of content in a doc or ticket.
- Quickly check whether two blocks of text are identical (equal hashes mean equal content).
FAQ
Can I use MD5 to store passwords?
Never. MD5 is extremely fast and long broken, making it trivially vulnerable to rainbow tables and brute force. Store passwords with slow algorithms designed for it — bcrypt, scrypt or Argon2 — plus a random salt. MD5/SHA are only suitable for integrity checks.
Should I pick SHA-256 or SHA-512?
For integrity both are secure; SHA-256 has a shorter output (64 hex chars) and is more common, so it is the usual default. SHA-512 has a longer digest and can be faster on 64-bit platforms. Match whichever algorithm the published checksum uses.
Can I hash large files? Are they uploaded?
Files are read and hashed locally in your browser, never uploaded, so private files are safe. Very large files are bounded by browser memory and processing time, so it may take a moment — let the progress finish.
Does the same content always produce the same hash?
Yes — hashes are deterministic. Given the same algorithm and the exact same input bytes, the result is always identical. Conversely, different hashes mean the content differs, even by a single space or newline.