---
title: "SHA3-256"
description: "The NIST SHA-3 sponge at 32 bytes with HMAC. Nothing in common with SHA-2 inside"
canonical_url: "https://hashes.agntn.dev/algorithms/sha3-256"
---
# SHA3-256

> The NIST SHA-3 sponge at 32 bytes with HMAC. Nothing in common with SHA-2 inside

<algorithm-facts name="sha3-256">



</algorithm-facts>

Keccak's sponge as NIST standardised it in FIPS 202. A completely different design from SHA-2, which is the point: if SHA-2 ever falls, this doesn't fall with it.

```ts
create("sha3-256").hash("").digest;
// "a7ffc6f8bf1ed76651c14756a061d662f580ff4de43b49fa82d80a4b80f8434a"
create("keccak256").hash("").digest;
// "c5d2460186f7233c927e7db2dcc703c0e500b653ca82273b7bfad8045d85a470"
```

Same permutation, same rate, one different padding byte, two unrelated digests. Ethereum froze its choice before NIST changed that byte, so an Ethereum hash is [Keccak-256](https://hashes.agntn.dev/algorithms/keccak256), and calling it SHA3 is a bug report waiting to happen.


## Sitemap

See the full [sitemap](https://hashes.agntn.dev/sitemap.md) for all pages.