This hash generator computes four common digests of the same text at once. Everything runs in your browser: the input is never uploaded, and the result updates as you type.
Your data is processed locally in your browser and is not uploaded to our server.
Hashing is unavailable in this browser context. Use a secure (HTTPS) page.
MD5 and SHA-1 are not secure for passwords or signatures. Use SHA-256 or SHA-512 for integrity checks.
Digest = H(message)
A cryptographic hash maps any input to a fixed-length digest. The same input always produces the same digest, while a tiny change produces a completely different one.
MD5 = 128 bits; SHA-1 = 160 bits; SHA-256 = 256 bits; SHA-512 = 512 bits
The hexadecimal output is twice the bit length in characters: 32, 40, 64 and 128 characters. MD5 and SHA-1 are considered broken for security purposes.
A checksum is needed for a short test string.
The results are deterministic. Hashing the same string again always returns the same digests.
A published SHA-256 checksum must be compared with a local file.
This text tool hashes text; for large files, use a file-aware checksum tool to avoid copying the whole file into the page.
MD5 and SHA-1 are fast and broken for security. Even SHA-256 is not a password hash on its own; use Argon2, bcrypt or scrypt with a salt for credentials.
A hash cannot be decrypted. It is a one-way fingerprint used for integrity checks and identifiers, not for hiding recoverable data.
The same characters encoded differently produce different bytes and therefore different hashes. This tool hashes the UTF-8 bytes of the text you enter.
Use SHA-256 or SHA-512 for integrity checks. MD5 and SHA-1 are included for compatibility with legacy checksums but are not secure against collisions.
No. A hash is one-way. Short or common inputs can be guessed with a dictionary, which is why unsalted password hashes are unsafe.
Hidden whitespace, different line endings or different Unicode normalization change the bytes. Compare the exact input, not the rendered text.
No. Hashing runs locally; SHA algorithms use the browser Web Crypto API and the text never leaves the page.
Many older systems publish SHA-1 checksums. It is useful for verifying those values, but it should not be chosen for new security designs.