Developer Utilities

Hash Generator

Compute SHA-256, SHA-384 and SHA-512 hashes from local text or files with Web Crypto and compare hexadecimal results.

Browser processing · No account required

Hash local data

Text is hashed as UTF-8, including spaces and line breaks. Empty text has a valid hash.

Web Crypto digest is not streaming. The file limit bounds the full input buffer. Hashes do not encrypt data and are unsuitable as direct password storage.

Hash result

Add your input, then run the tool to see results.
WORK WITH CONFIDENCE

Understand your results

For developers comparing the bytes of local text or files.

Web Crypto calculates SHA-256, SHA-384 or SHA-512 from UTF-8 text or a selected file buffer. Hexadecimal results can be compared case-insensitively with an expected digest. Nothing is uploaded.

How to use this tool

  1. Choose Text or Local file and select an SHA algorithm.
  2. Generate the hash and inspect the number of input bytes.
  3. Copy the hexadecimal digest or paste an expected digest to compare it.

What the observations mean

A matching digest confirms equality under the selected comparison, subject to the algorithm’s properties. It does not prove who supplied the expected value.

Worked example

Hash UTF-8 text without a trailing newline.

hello · SHA-256
Expected digest:
2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824

The result contains 64 hexadecimal characters representing the 32-byte SHA-256 digest. Adding a newline changes the input bytes and the hash.

Limits and processing

Local Web Crypto only. Files up to 16 MiB and text up to 1,000,000 characters. Digest is not streaming or a password-storage scheme. An active computation can finish after the UI changes, while its stale result is suppressed.

Common problems and practical fixes

A comparison mismatches
Check the algorithm, file version, whitespace and encoding.
The expected value is rejected
Use a hex digest of the same length without a filename or algorithm prefix.
Web Crypto is unavailable
Use a supported HTTPS browser and try a smaller local file.

Best practices

Use the original file bytes for integrity checks and publish or obtain expected digests through a trustworthy source.

Practical tips

  • Compare digests only when the same algorithm and exact bytes were used.
  • Confirm the expected digest through a trusted channel if using it for an integrity check.
A LITTLE MORE CLARITY

Frequently asked questions

Practical answers for using the Hash Generator.

Is hashing encryption?

No. A digest is a fixed-length fingerprint and does not provide reversible encrypted storage.

Why can’t I select a very large file?

subtle.digest is not a streaming API. The 16 MiB cap bounds its full-input memory requirement.

Why do matching words have different hashes?

Encoding, spaces, line endings and other byte differences change the digest.