How values are calculated
Text is encoded as UTF-8. SHA uses the standard Web Crypto API, while MD5 and CRC run in a local browser implementation. Results use lowercase hexadecimal characters.
How to choose an algorithm
For a new integrity comparison, SHA-256 is usually the best default. MD5 and SHA-1 remain for legacy compatibility. CRC-32 and CRC-32C detect accidental transmission errors but do not protect against deliberate tampering.
Your text stays local
Input is processed in the browser and is not sent to the server, placed in the URL, or included in analytics. Text is limited to 5 MiB when encoded as UTF-8.
Frequently asked questions
How is a hash different from CRC?
SHA algorithms are cryptographic hashes. CRC is a fast checksum for detecting accidental corruption and must not be treated as protection against tampering.
Are MD5 and SHA-1 secure?
No. Their collision resistance is broken. Use them only for legacy compatibility and existing check values, not for signatures or other security-sensitive purposes.
Can the original text be recovered from a SHA hash?
There is no reverse operation, but short or predictable input can still be guessed by brute force or a dictionary.
Is this suitable for password storage?
No. Password storage requires a dedicated slow algorithm with a unique salt, such as Argon2id.