Generate MD5, SHA-1, SHA-256, and SHA-512 digests from text in your browser. This tool does not read files or provide password hashing.
Input text
Enter text above…
Enter text above…
Enter text above…
Enter text above…
All hashing happens locally in your browser. Your text is never sent to a server.
A cryptographic hash function takes any input and produces a fixed-length output (the hash or digest). The same input always produces the same hash. A tiny change to the input produces a completely different hash. It's a one-way function and you cannot reverse it to get the original input.
MD5 produces a 128-bit (32 hex character) hash and was once widely used for passwords and security. It's now considered cryptographically broken. Collisions (two different inputs with the same hash) can be generated quickly. Use MD5 only for checksums and data integrity, not for security.
SHA-256 is a general-purpose 256-bit hash used in many protocols and checksum workflows. It is not a password-hashing method; password storage should use a dedicated, deliberately slow algorithm such as Argon2id, scrypt, bcrypt, or PBKDF2 with appropriate parameters.
This tool hashes text you enter; it does not open or hash downloaded files. To verify a file, use a file-hashing tool and compare the result with a checksum obtained from the publisher through a trusted channel. A checksum match alone does not prove who published the file.
Do not store passwords as plain text or as a raw SHA-256 digest. Use a dedicated password-hashing function with a unique salt and parameters appropriate to your platform; this text-hash tool does not provide password storage or password verification.
A collision is when two different inputs produce the same hash. For MD5, collisions are computationally trivial. For SHA-256, no practical collision has ever been found. SHA-3 (Keccak) is the newest NIST standard, designed with a completely different internal structure as insurance against SHA-2 weaknesses.
Generate supported MD5, SHA-1, SHA-256, and SHA-512 digests from text. This tool does not read files or provide password hashing.
Input: "hello"
MD5: 5d41402abc4b2a76b9719d911017c592 | SHA-256: 2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824
Input: "Hello" (capital H)
Completely different hash — demonstrates sensitivity to input changes
Input: an entire book
Hash length is always fixed — SHA-256 always produces exactly 64 hex characters regardless of input size
Comparing digests for sample text
The same input and algorithm produce the same digest; different input produces a different digest. This does not authenticate a file or publisher.
MD5 was designed by Ron Rivest in 1991. By 2004, researchers had demonstrated practical collision attacks (two different inputs producing the same hash), making it unsuitable for security. SHA-256, part of the SHA-2 family designed by the NSA and published in 2001, remains the current standard and underpins Bitcoin's proof-of-work mining system.
This page calculates a digest from text entered into its input; it does not read downloaded files. The same text and algorithm produce the same digest. A hash is not encryption and cannot be decoded into the original.
Use the algorithm required by the system, protocol, or publisher you are working with. SHA-256 is a common general-purpose integrity choice. Older algorithms such as MD5 and SHA-1 can still appear in legacy checksums, but they are not suitable for new security designs because collision attacks are known.
A plain hash is not a safe password-storage design. Passwords need a slow, salted, purpose-built password hashing method such as Argon2, scrypt, or bcrypt, with rate limiting around login attempts. Use this page for learning and integrity checks; never paste a real password, private key, or confidential document into an online tool.
No. This tool accepts text, not files. Use a file-hashing tool for the downloaded file, then compare the full digest with a checksum from the publisher through a trusted channel. A match supports integrity checking but does not prove the publisher's identity.