Input text

Algorithm

Uppercase HEX output

HEX

Base64

Real input and output

Input

hello

Output

2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824

Input

hello (SHA-256)

Output

HEX     2cf24dba5fb0a3...938b9824
Base64  LPJNul+wow4m6DsqxbninhsWHlwfp0JecwQzYpOLmCQ=

Same digest, different notation. Match whatever the verifying side expects.

Errors you will hit

Hashing is a one-way function, not encryption. There is no decryption. The only way back is guessing candidates and comparing digests.

SHA functions are deliberately fast, which makes brute force cheap. Use bcrypt, scrypt, or Argon2, which add salting and a tunable work factor.

Check for a trailing newline. Copying from a file or editor often carries the final line break, producing a completely different hash.

Tools that pair well

When this hash tool is genuinely useful

Compare SHA values for downloaded files or build outputs to confirm whether two artifacts are actually identical.

Test how whitespace, line breaks, or field ordering change a digest before you wire the same input into a backend signature flow.

Short comparison strings stay in the browser, which is safer than pasting them into random online converters during debugging.

Questions that come up often

No. Hashing is a one-way digest used for comparison or integrity checks, while encryption is designed for later decryption.

SHA-256 is usually the practical default for integrity checks. Use SHA-512 when your policy, ecosystem, or output-length requirements call for it.

The digest is computed with the browser Web Crypto API. You should still account for extensions, device security, and your own operating environment.