A practical guide to cryptographic hashes
What is a hash?
A hash function maps input bytes to a fixed-length digest. The same bytes and algorithm produce the same digest, while even a small input change normally produces a very different result. Hashing is not encryption: it has no decryption key, and a digest does not provide a reversible representation of the original message. The output is usually shown as hexadecimal characters.
This tool converts the entered text to UTF-8 bytes before hashing it. SHA-256 and SHA-512 are members of the SHA-2 family. SHA-1 and MD5 are included for compatibility with older systems, but both are broken for collision resistance. Do not use either for digital signatures or security-sensitive integrity checks. Changing uppercase or lowercase changes only the hexadecimal display, not the digest bytes.
Common developer uses
Developers compare hashes to detect accidental changes, check data against a trusted checksum, or integrate with protocols that specify a particular digest. A digest can also help identify a precise test fixture or compare outputs across environments. These uses depend on choosing the correct algorithm and on obtaining the expected value from a trustworthy source.
Select an algorithm and type or paste text. The digest updates as the input changes, including for empty text. Use the uppercase control for the required representation and Copy to transfer the result. SHA algorithms use the browser's Web Crypto API, which normally requires HTTPS or localhost. MD5 is implemented locally for legacy interoperability.
Troubleshooting common errors
If a digest does not match, first confirm the exact algorithm and text encoding. A trailing newline, different capitalization, extra whitespace or a different Unicode representation changes the input bytes. A text box also cannot stand in for arbitrary binary file bytes; use a file-aware hashing tool to check a downloaded file. Compare hexadecimal values without confusing letter case with a change to the actual digest.
If SHA output is unavailable, check that the page is served over HTTPS or from localhost and that the browser supports Web Crypto. Older browsers, insecure origins or restrictive environments can make the API unavailable. This page reports the problem rather than sending your input to a server as a fallback.
Security and privacy
A plain hash does not prove who produced a message. Use an appropriate keyed construction or digital signature when authenticity is required. Passwords should be protected with a dedicated, salted password-hashing scheme, not a fast general-purpose digest. Hashing here happens in your browser and the application does not submit input to its server, but browser extensions, clipboard access and the device itself remain part of your security boundary.