Skip to content
en
All tools

Categories

Developer ToolsEncoding & DecodingJSON & DataHash & ChecksumText ToolsDate & TimeNetwork ToolsFile ToolsMarkdown & Diagrams

SHA-3 Hash Generator

Choose SHA3-224, 256, 384 or 512 and hash your text with the Keccak-based NIST standard.

Processed locally in your browser

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

What is SHA-3 Hash Generator?

SHA-3 is the 2015 NIST standard (FIPS 202) built on the Keccak sponge construction. It is not a replacement for a broken SHA-2 but a structurally different alternative: it is immune to length-extension attacks and gives a second, independent family should SHA-2 ever weaken.

Pick a digest size (224, 256, 384 or 512 bits), enter text or hex bytes, and the tool shows the digest in hex or Base64. Note that Ethereum uses the original Keccak-256 padding, which produces different output from the standardised SHA3-256 computed here.

How does it work?

  1. Select the digest size: SHA3-224, SHA3-256, SHA3-384 or SHA3-512.
  2. Type or paste your text (or switch the input type to hex bytes).
  3. Copy the digest as hex or Base64. SHA3-256 of "abc" is 3a985da74fe225b2…

Common use cases

  • Interoperating with a system or spec that mandates SHA-3.
  • Testing a SHA-3 implementation against standard vectors.
  • Choosing a hash that is not vulnerable to length-extension for a keyed-hash design.
  • Comparing SHA-2 and SHA-3 digests of the same data.

Examples

Try this input in the tool above:

Input
The quick brown fox jumps over the lazy dog
Output
69070dda01975c8c120c3aada1b282394e7f032fa9cf32f4cb2259a0897dfc04

Privacy

SHA-3 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

SHA3-256 differs from Keccak-256 (used by Ethereum) because of a different padding byte, so their digests do not match. SHA-3 is also fast, so it is not a password hash.

Frequently asked questions

Is SHA-3 better than SHA-2?

Not necessarily. SHA-2 is not broken and is faster in software; SHA-3 offers a different design and resistance to length extension. Both are approved by NIST.

Why does my Ethereum hash not match SHA3-256?

Ethereum uses the pre-standard Keccak-256 with different padding. The standardised SHA3-256 gives a different digest for the same input.

Which size should I choose?

SHA3-256 matches the 128-bit security level most applications target; use SHA3-512 only when a protocol requires the longer digest.

Related tools

More tools in Hash & Checksum →