SHA3-256 hash generator.
Paste text or drop a file and read its SHA3-256 digest as you type. SHA3-256 is SHA-256's security from a different design, the Keccak sponge NIST standardised in 2015; everything runs in your browser and nothing is uploaded.
SHA3-256 hash generator.
Need the UI around it? With Pro, your AI agent builds the form, the result card and the rest of the page from a prompt.
Get ProHow it works
4 steps, no account. It runs in your browser and nothing is uploaded.
Enter text or a file
Type or paste anything, or drop a file onto the input. The digest updates with every keystroke.
Pick the algorithm and format
SHA3-256 is the default; switch to SHA3-224, SHA3-384 and SHA3-512, and read the digest as hex or Base64.
Key it, when you need a signature
Turn on HMAC and enter a secret to sign the input instead of hashing it.
Verify, copy or download
Paste a published digest to confirm a download, or copy and download your own.
SHA-3 against SHA-2 and Keccak
SHA-3 is the standard in reserve. A different construction from SHA-2, chosen so a break in one would not take both; slower in software, immune to length extension.
SHA3-224
224 bits, 56 hex characters. A capacity of 448 bits: the 112-bit security level in the SHA-3 family.
SHA3-256
256 bits, 64 hex characters. Capacity 512 bits, 128-bit security. The SHA-3 size to reach for by default.
SHA3-384
384 bits, 96 hex characters. Capacity 768 bits, 192-bit security. Rarer, for policies that ask for more than 128 bits.
SHA3-512
512 bits, 128 hex characters. Capacity 1024 bits, 256-bit security. The slowest per byte: the sponge absorbs only 72 at a time.
Keccak-256
256 bits. The same permutation as SHA3-256 with the pre-standard padding, so different digests. What Ethereum means by sha3.
SHA-256
256 bits, 2001. A Merkle–Damgård chain: open to length extension, so HMAC exists to close the hole. Everywhere, and fast.
SHA-512
512 bits, 2001. Also Merkle–Damgård, on 64-bit words. Faster than SHA3-512 in software by two or three times.
BLAKE3
256 bits, 2020. A tree hash: parallel, several times faster than SHA-3 in software, and also immune to length extension.
Related tools
More hash generators. Every one free, in the browser.
Pricing
Build it with Pro
The tool is free. Pro adds 6,000+ blocks, premium templates and the MCP server, so your AI editor builds the product around it.
4.9/5 out of 5 · 150+ reviewsfrom 150+ founders and developers.
- Secure checkout via Stripe
- Code lives in your repo
- Keep what you've shipped if you cancel
- License terms
Questions and answers
Before you trust the result: what to know about the format, the limits, your data and the tools next to it.
SHA3-256 is the 256-bit member of SHA-3, the standard NIST published as FIPS 202 in 2015 after a five-year public competition won by Keccak. It gives the same 64-hex-character digest length and the same 128-bit security as SHA-256 from an entirely different design, a sponge rather than a Merkle–Damgård chain.
SHA-3 is a sponge. A 1600-bit state absorbs the input a block at a time, running the Keccak-f permutation (24 rounds) after each block, then squeezes the digest out of the first part of the state. The part never exposed, the capacity, is twice the digest length, which is what sets the security level. The state is never fully output, so there is no length-extension attack, unlike SHA-2.
Yes, with a larger margin than most: the best attacks reach a handful of its 24 rounds. Because a sponge never exposes its full state, SHA3-256 is also immune to length extension, so H(key || message) is safe with it where it is not with SHA-256. NIST calls SHA-2 and SHA-3 equally approved.
Equal security, different design. SHA-256 is faster in software and has hardware instructions on most CPUs; SHA3-256 is two to three times slower in software but simpler in hardware and immune to length extension. SHA-3 exists so a break in SHA-2's structure would not take every hash down with it.
Only in the padding. NIST appended two bits to the message before the Keccak padding when it standardised SHA-3 in 2015, so SHA-3 digests differ from the original Keccak's for every input. Ethereum adopted Keccak-256 before the change and kept it, so what Solidity calls sha3 or keccak256 does not match SHA3-256. This tool gives you both families; pick the one the other side uses.
Nothing leaves your browser. The hash is computed on your machine, by the browser's Web Crypto API or a WebAssembly build of the algorithm loaded on first use, and the page makes no request with your input. You can load the page, go offline and keep hashing.
Drop the file onto the input or choose it with the button, and the tool reads it in your browser and hashes the bytes. Files up to 1 GB work; past that the browser would need the whole file in memory, so the tool declines. Paste the published digest into the Verify field to compare.
Hex is the common form: 64 characters from 0 to 9 and a to f, the same value in upper or lower case. Base64 writes the same 32 bytes in fewer characters, and Base64url swaps + and / for - and _ with no padding. Switch the output and the digest is re-encoded, not recomputed.
Text is hashed as UTF-8 bytes, which is what every language and command line does by default. A trailing newline changes the digest, so `echo -n` or this tool's input, with no newline added, matches a command-line tool run on a file without one.
Turn on HMAC and enter the secret: the tool computes HMAC-SHA3-256 over the input with that key, the standard RFC 2104 construction, so the value matches what a server-side HMAC library produces. The key is hashed as UTF-8 text.
No. The SHA3-256 hash generator is free and opens without a sign-in, an account or an install.
Nothing. The SHA3-256 hash generator holds your input in the page's memory, so closing or reloading the tab clears it, and it saves nothing in this browser.
The toolbar switches to SHA3-224, SHA3-384, and SHA3-512 without leaving the page. Each one reads the same input, so you can compare digests side by side.
SHA3-256 is computed by a WebAssembly build from the hash-wasm library, which the page loads the first time you hash something and reuses after that.
Yes: the File to SHA3-256 page has the same algorithms and options and opens on the file pane. Files are read in your browser and never uploaded.
Not on its own. SHA3-256 is built to be fast, and fast hashes are cheap for an attacker to guess against. Passwords need a salted, deliberately slow hash: use Argon2id, Argon2d, and bcrypt from the hash generators, which draw a fresh random salt each time.
Closest to the SHA3-256 hash generator: File to SHA3-256, SHA-256 hash generator, Keccak-256 hash generator, BLAKE3 hash generator. Each opens on its own page, free and in the browser.
The SHA3-256 hash generator is one of 64 in its group. The group's page, /tools/hash, lists them all.
The tool is free. Its interface is built from shadcn.io's own components (Button, Input, Slider and the rest of the registry under /ui), which come in React, Vue, Svelte and Solid. Pro adds the blocks and templates for the product around it.
4.9 out of 5 from 150+ developers
Build the product around it
Every block, template and icon, installed by your AI agent in your theme. The tools stay free.
Get Pro



