Verifying a downloaded file
Before
Downloaded a Linux ISO from a mirror
After
SHA-256 hash matched the official checksum
Confirmed the file wasn't corrupted or tampered with. Always do this for large downloads.
I use this for file integrity checks and verifying that downloaded builds match what the developer published. Paste the text, see all four hashes at once. SHA-256 and SHA-512 use the browser's Web Crypto API — the same source trusted by security tooling.
Your files are processed in your browser and never uploaded to any server.
A mistake I see often: people use MD5 or SHA-1 for passwords. Don't. Both are broken for password storage. Use bcrypt, Argon2, or PBKDF2 for passwords, and use this tool for checksums and file verification. MD5 is still fine for detecting accidental corruption, just not for anything security-related.
— Mirza Noman Baig
These are actual measurements from using this tool, not estimates.
Before
Downloaded a Linux ISO from a mirror
After
SHA-256 hash matched the official checksum
Confirmed the file wasn't corrupted or tampered with. Always do this for large downloads.
Before
Same input produced different cache hits
After
Hashed the input — found trailing whitespace was changing the hash
The bug was invisible until I compared the hashes. Fixed by trimming the input.
Before
Webhook signature verification kept failing
After
Computed SHA-256 of the raw body and matched the header
The bug was that the framework was parsing the JSON before hashing. Raw body hash matched the expected value.
MD5, SHA-1, SHA-256, and SHA-512 — see them all at once.
SHA-256 and SHA-512 use the browser's trusted crypto library.
Hashes update as you type. No button to press.
Nothing gets uploaded. Safe for API keys, tokens, and sensitive strings.
No. MD5, SHA-1, SHA-256, and SHA-512 are all too fast for password storage. Use bcrypt, Argon2, or PBKDF2 instead — they're designed to be slow.
Yes, much better. MD5 is cryptographically broken and can be deliberately collided. SHA-256 is the current standard for integrity checks.
No. Everything runs in your browser. Nothing gets sent to a server.
For general integrity checks, SHA-256. For maximum security margin, SHA-512. MD5 and SHA-1 only for legacy compatibility.
No. The tool only reads your input and produces output. Your original text is unchanged.