Verify File Integrity
Compare a file's hash against a published checksum to confirm it hasn't been tampered with or corrupted during download.
Generate SHA-1, SHA-256, SHA-384, and SHA-512 hashes from any text using the Web Crypto API. Input is never stored or sent anywhere. No signup, no ads, 100% private.
Enter text above to compute hashes.
Compare a file's hash against a published checksum to confirm it hasn't been tampered with or corrupted during download.
Uses crypto.subtle.digest() — the browser's native cryptographic engine. No third-party libraries, no dependencies.
SHA-1, SHA-256, SHA-384, and SHA-512 in one place. Switch algorithms instantly or view all four hashes simultaneously.
Your input text never leaves your browser. Nothing is logged, stored, or transmitted. Works completely offline.
Deprecated for security use. Collision attacks are practical. Still used for Git commits and legacy checksums.
Avoid for new security applicationsThe current standard for most security applications including TLS certificates, code signing, and blockchain.
Recommended for general useHighest security margin. Faster than SHA-256 on 64-bit hardware. Use for password hashing and high-security applications.
Best for high-security use casesProduces a 40 character hex string representing 160 bits of output.
40 hex charsProduces a 64 character hex string representing 256 bits of output.
64 hex charsProduces a 128 character hex string representing 512 bits of output.
128 hex charsA hash function takes input data of any size and produces a fixed-length string. The same input always produces the same output, but even a tiny change in input produces a completely different hash.
No. Hashing is one-way — you cannot recover the original text from a hash. Encryption is two-way and requires a key to decrypt. Hashes are used for integrity verification, not secrecy.
Use SHA-256 or SHA-512 for security purposes. SHA-1 is considered weak against collision attacks and should be avoided for security. MD5 is broken for security use but still common for checksums.
No. Hashing is performed entirely in your browser using the Web Crypto API (crypto.subtle). Your text never leaves your device.
Hash functions are deterministic. This property is what makes them useful for verifying integrity — if two hashes match, the inputs were identical.