Reproduce a SHA-256 digest and diagnose a mismatch

Select SHA256 and type abc with no spaces or line break. Compare all 64 hexadecimal characters with the known result below. This gives you a small reproducible check before comparing a longer text.

Add a newline or change a to A. The digest should change. When two systems disagree, first compare the input bytes, text encoding, line endings, and algorithm rather than assuming the hash implementation is broken.

Input: abc
SHA-256: ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad

Where this workflow can go wrong

A digest can detect a difference only if the expected digest comes from a trusted source. It does not prove who sent the message. Use a keyed authentication mechanism when you need message authentication. MD5 and SHA-1 are legacy choices and should not be used where collision resistance is required. The CryptoJS option labelled SHA3 uses Keccak and is not interchangeable with standardized SHA3-512.

Check your result

This page hashes UTF-8 text, not file bytes, and shows no result for empty input. For password storage, use a dedicated password-hashing scheme rather than a fast general-purpose digest. Do not paste real production secrets into debugging examples.

Read the full guide · Technical reference

About this tool

Computes one selected digest of UTF-8 text: MD5, SHA1, SHA256, SHA512, CryptoJS SHA3 (Keccak), or RIPEMD160. This page does not hash files or verify who sent a message.

How to use

Select SHA256 and type abc, without a newline. The result starts ba7816bf and ends f20015ad; the worked example below gives the full value. Change the algorithm to calculate a different digest; results for all algorithms are not displayed simultaneously.

Tips & Notes

An extra space or newline changes the digest. A hash does not protect a weak password from guessing. The SHA3 option is CryptoJS Keccak and must not be treated as standardized SHA3-512.