Skip to content

SHA-256 Hash Generator

Hash any text with SHA-256 and get the 256-bit digest as hex or Base64 in real time.

Processed locally in your browser

Options
0 chars · 0 lines
The result will appear here.

What is SHA-256 Hash Generator?

SHA-256 is the most widely used member of the SHA-2 family. It turns an input of any size into a 256-bit digest (64 hex characters) that is practically impossible to reverse or to collide. It underpins TLS certificates, Git object storage in newer repositories, Bitcoin, package lock files and software download checksums.

This tool converts your text to UTF-8 bytes (or reads hex bytes), hashes them with a WebAssembly SHA-256 and shows the digest in hex or Base64, with the input size. For files, use the File Hash Calculator.

How does it work?

  1. Type or paste your text; the hash is computed as you type.
  2. Select the input type (UTF-8 or hex bytes), the output encoding (hex or Base64) and the letter case.
  3. Copy the digest. The SHA-256 of "abc" starts with ba7816bf8f01cfea.

Common use cases

  • Comparing a text or a token with a published SHA-256 fingerprint.
  • Creating deterministic IDs or cache keys from strings.
  • Checking Subresource Integrity values (SRI uses Base64 SHA-256/384/512).
  • Reproducing a digest from documentation to validate your own implementation.

Examples

Try this input in the tool above:

Input
The quick brown fox jumps over the lazy dog
Output
d7a8fbb307d7809469ca9abcb0082e4f8d5651e46d3cdb762d02d0bf37c9e592

Privacy

SHA-256 Hash Generator runs entirely in your browser. The text or files you provide are processed on your device and are not uploaded, logged or stored on our servers.

Limitations

A plain SHA-256 is fast by design, so it is not suitable on its own for storing passwords: use a slow, salted password hash such as Argon2, scrypt or PBKDF2.

Frequently asked questions

Is SHA-256 encryption?

No. It is a one-way hash: you cannot get the original text back from the digest. Encryption, by contrast, is reversible with a key.

Why do I get a different hash than another site?

Usually because of invisible differences: a trailing newline, different line endings, or text encoded in something other than UTF-8. Compare the byte length shown here with your source.

How do I get the Base64 form used in SRI attributes?

Set the output encoding to Base64. Prefix it with "sha256-" in an integrity attribute.

More tools in Hash & Checksum →