SHA3-256 Hash Generator

Type or paste text, or choose a file, and press Generate SHA3-256 hash. Paste an expected hash to check whether they match. Everything runs in your browser.

Try an example
The file’s bytes are hashed in your browser; nothing is uploaded.

About this SHA3-256 generator

SHA3-256 is the 256-bit hash of the SHA-3 standard (FIPS 202), written as 64 hexadecimal characters. It is built on the Keccak sponge, which works differently from SHA-1 and SHA-2, so it is not affected by weaknesses found in those designs. Use it when a specification asks for SHA-3, or as a second, independent hash next to SHA-256. Hash text or a whole file here and paste a published checksum into Expected hash to confirm your copy is exact. Browsers have no built-in SHA-3, so this page uses its own implementation on your device.

How to generate a SHA3-256 hash

  1. Add text or a file. Type or paste text, press an example, or press Hash a file to hash a file’s exact bytes.
  2. Pick the format. Lowercase hex is the usual format; choose uppercase hex or Base64 if your system expects it. Paste an expected hash to compare.
  3. Press Generate SHA3-256 hash. The hash appears below, with a match or no-match message when you pasted an expected hash.
  4. Copy the hash. Press Copy hash, or copy it in another format from the list.

Frequently asked questions

Is SHA3-256 the same as Keccak-256?

No. They share the same sponge, but SHA-3 adds a different padding byte, so the hashes differ. Ethereum uses the original Keccak-256, which will not match this tool’s output.

How is SHA3-256 different from SHA-256?

They are unrelated designs: SHA-256 belongs to the SHA-2 family, while SHA3-256 uses the Keccak sponge. Both give 256-bit hashes, but the same input never produces the same value.

What is the SHA3-256 hash of an empty input?

It is a7ffc6f8bf1ed76651c14756a061d662f580ff4de43b49fa82d80a4b80f8434a. Leave the input empty and press the button to see it.

How long is a SHA3-256 hash?

Always 256 bits: 64 hexadecimal characters, or 44 characters in Base64, whatever the input size.

Why does my SHA3-256 differ from another tool?

Every byte counts. Text is hashed as UTF-8 with LF line breaks, including spaces and a final line break, so a trailing space or a Windows line break elsewhere changes the hash. Also check that the other tool is not computing Keccak-256.