128-bit hash, fast but cryptographically broken
160-bit hash, deprecated for security
256-bit hash, widely used and secure
512-bit hash, highest security
32-bit checksum, industry-standard for data integrity
Select text input, enter abc without quotation marks or a trailing newline, and enable SHA256. Generate the hashes and compare the complete digest with the example below. A digest identifies the exact bytes supplied, so adding a space or changing a letter produces a different result. Select additional algorithms only when you need their output for a particular comparison.
For a downloaded file, switch to file upload and select the file itself rather than pasting its name. Calculate the same algorithm used by the publisher, then compare every hexadecimal character with a checksum obtained from a trusted source. Keep that reference separately from the file. Matching an attacker-provided file against an attacker-provided checksum does not establish authenticity.
Keep the algorithm name with the digest when recording results; a checksum without its algorithm cannot support a reliable later comparison.
abc
SHA256 β ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad
Choose MD5, SHA1, SHA256, SHA512, or CRC32 to match the reference checksum. Different algorithms cannot be compared directly. MD5 and SHA1 are unsuitable for new security-sensitive checks; CRC32 detects accidental corruption without establishing authenticity. SHA256 and SHA512 have different digest lengths. A longer digest does not make an untrusted reference trustworthy.
Hashing uses bytes, not visual similarity. Text input is encoded as UTF-8, while file mode hashes the uploaded bytes. A newline, byte-order mark, different line endings or another Unicode representation can change a digest even when two editors display similar text. Compare the same input type and algorithm.
A general-purpose digest is not a password-storage system. This tool does not create a password database, generate per-user salts or configure a password-hashing cost. Use an established password-hashing implementation in your application instead. A checksum also does not prove who created a file or whether its contents are safe.
A single upload allows 100 MiB and is read into browser memory; smaller files can still strain a device. There is no directory scan, scheduled monitoring, or multi-gigabyte streaming workflow. Process one file at a time and keep the original. Downloaded results should retain algorithm names alongside digests so later comparisons remain meaningful.
Processing runs in your browser. Choosing Share uploads the selected tool state; anyone with the link can open it. Signing in to save sends content to your account library and records save history. Review the selection before either action. Closing the page does not delete those copies. Copying locally does not create a server share.