Hash Generator
Compute MD5, SHA-1, SHA-256, SHA-384, SHA-512, and CRC32 hashes for text or files. Verify checksums instantly.
All hashing runs locally using your browser's native Web Crypto API and inline implementations. No text or files are uploaded anywhere.
Hash Results
| Algorithm | Hash | Copy |
|---|
Verify Checksum
Paste an expected hash below — the algorithm is auto-detected by length.
Drop any file here
or click to browse — any file type, any size
—
—
Frequently Asked Questions
No. MD5 is cryptographically broken and should never be used for passwords or security-sensitive applications. Modern attacks can crack MD5 hashes extremely quickly using GPU-based brute force. Use bcrypt, scrypt, or Argon2 for passwords. MD5 is still acceptable for non-security checksums and data integrity verification where collision attacks are not a concern.
SHA-256 produces a 256-bit (32-byte) hash, while SHA-512 produces a 512-bit (64-byte) hash. SHA-512 provides higher theoretical security and can be faster on 64-bit processors due to its internal 64-bit word operations. SHA-256 is the most widely adopted standard for digital certificates, code signing, and general cryptographic use. Both are part of the SHA-2 family and are considered secure.
CRC32 is ideal for fast data integrity checks where security is not required, such as verifying file transfers, detecting accidental data corruption in network packets (used in Ethernet, ZIP, PNG), and checksumming data in databases. CRC32 is NOT cryptographically secure and should not be used for security purposes. It is extremely fast and produces a compact 8-character hex output.
There is no hard limit — this tool reads the entire file into browser memory using the FileReader API. Files up to several gigabytes can be hashed depending on available RAM. For files larger than 10 MB, a progress indicator appears. The hashing is done entirely in your browser; the file is never uploaded anywhere.
HMAC (Hash-based Message Authentication Code) combines a cryptographic hash function with a secret key to produce a message authentication code. Use HMAC when you need to verify both the integrity and authenticity of a message — for example, in API authentication (signing requests), JWT tokens, webhook signatures, and verifying that data has not been tampered with by someone who does not know the secret key.