Compute MD5, SHA-1, SHA-256, SHA-384, and SHA-512 hashes for text or files. Compare hashes to verify checksums — all in your browser.

Input
Drag & drop a file here, or click to browse

Compare Two Hashes

Paste two hashes above to compare
MD5 128-bit
Waiting for input...
SHA-1 160-bit
Waiting for input...
SHA-256 256-bit
Waiting for input...
SHA-384 384-bit
Waiting for input...
SHA-512 512-bit
Waiting for input...

How to Use This Tool

Step 1
Enter text or drop a file
Type or paste text in the input area. Switch to File mode to drag-and-drop any file and hash its raw contents.
Step 2
View all hashes at once
MD5, SHA-1, SHA-256, SHA-384, and SHA-512 are computed simultaneously. Toggle uppercase for hex output.
Step 3
Copy any hash
Click the Copy button next to any algorithm to copy that specific hash to your clipboard.
Step 4
Compare hashes
Switch to Compare mode to paste two hashes side-by-side and instantly verify if they match — great for checksum verification.

Hash Algorithm Comparison

Quick reference comparing the most common hash algorithms by output size, security status, and typical use cases.

AlgorithmOutputHex CharsSecurityCommon Uses
MD5128-bit32BrokenFile checksums, non-security deduplication
SHA-1160-bit40WeakLegacy systems, Git commit IDs
SHA-256256-bit64SecureTLS certs, Bitcoin, digital signatures, API auth
SHA-384384-bit96SecureTLS 1.2+, government systems (Suite B)
SHA-512512-bit128SecureDigital signatures, high-security applications

Frequently Asked Questions

What is a cryptographic hash function?
A cryptographic hash function takes any input — a single character, a paragraph, or an entire file — and produces a fixed-size output called a digest or hash. The same input always produces the same hash. Even changing a single bit of input produces a completely different hash (the "avalanche effect"). Hash functions are one-way: you cannot reverse a hash to recover the original input. These properties make them essential for data integrity checks, digital signatures, and password storage.
Is MD5 still safe to use?
MD5 is cryptographically broken — practical collision attacks have been demonstrated since 2004, and chosen-prefix collisions are now fast and cheap. It should never be used for digital signatures, certificate verification, or password hashing. However, MD5 is still widely used for non-security purposes like file download verification, cache key generation, and deduplication where accidental (not malicious) collision is the only concern.
What is the difference between SHA-1 and SHA-256?
SHA-1 produces a 160-bit (40 hex character) hash and is considered cryptographically weak — Google's SHAttered project demonstrated a practical collision in 2017. All major browsers and certificate authorities have deprecated SHA-1. SHA-256, part of the SHA-2 family, produces a 256-bit (64 hex character) hash and is currently considered secure. SHA-256 is the standard for TLS certificates, Bitcoin's proof-of-work, and most modern digital signature schemes.
Can I use hash functions for password storage?
Raw hash functions like SHA-256 should not be used directly for password storage because they're designed to be fast — an attacker can try billions of guesses per second. Instead, use purpose-built password hashing functions like bcrypt, scrypt, or Argon2. These are intentionally slow (with configurable work factors) and include a random salt to prevent rainbow table attacks.
Is my data sent to a server?
No. All hashing happens entirely in your browser using the Web Crypto API (for SHA algorithms) and a JavaScript implementation (for MD5). Your text and files never leave your device.