SHA-256 Hash Generator

Generate SHA-256 hashes from text, hex bytes, or files in your browser. Get hex and Base64 output, Bitcoin double SHA-256 in both byte orders, HASH160, and paste an expected checksum to verify a download. Nothing is uploaded.

Input

11 bytesHash updates as you type

Examples

Output

SHA-256

32 bytes · 64 hex characters — the standard checksum and Bitcoin's core hash

b94d27b9934d3e08a52e52d7da7dabfac484efe37a5380ee9088f7ace2efcde9

SHA-256 (Base64)

Same digest in Base64 — used for Subresource Integrity (sha256-…) and APIs

uU0nuZNNPgilLlLX2n2r+sSE7+N6U4DukIj3rOLvzek=

Bitcoin hashes

Double SHA-256 (SHA-256d)

SHA-256 of the SHA-256 — Bitcoin block hashes, txids, and Base58Check checksums

bc62d4b80d9e36da29c16c5d4d9f11731f36052c72401a76c23c0fb5a9b74423

Double SHA-256, reversed byte order

How block explorers display block hashes and transaction IDs

2344b7a9b50f3cc2761a40722c05361f73119f4d5d6cc129da369e0db8d462bc

HASH160 (RIPEMD-160 of SHA-256)

20 bytes — the payload inside P2PKH (1…) and P2WPKH (bc1q…) addresses when the input is a public key

d7d5ee7824ff93f94c3055af9382c86c68b5ca92

Verify a checksum

What the SHA-256 output means

SHA-256 turns any input — a word, a transaction, or a 2 GB installer — into a fixed 32-byte fingerprint, written as 64 hex characters. The same input always gives the same hash, and changing a single bit changes the whole output, so matching hashes prove two files or messages are identical. Bitcoin is built on SHA-256: block hashes and transaction IDs are double SHA-256 (shown reversed by explorers), proof-of-work miners search for a header whose double SHA-256 is below the target, and addresses use HASH160 — RIPEMD-160 of the SHA-256 of a public key. Use the verify box to confirm a wallet download matches the checksum its developers publish.

How it is computed

Text mode UTF-8-encodes your string; hex mode parses raw bytes; file mode reads the file’s bytes locally. SHA-256 (FIPS 180-4) pads the message to a multiple of 512 bits and runs 64 compression rounds per block, producing 256 bits. Base64 = the same 32 bytes encoded in Base64. Double SHA-256 = SHA-256(SHA-256(input)). Reversed = the double hash with byte order flipped, as Bitcoin displays block hashes and txids. HASH160 = RIPEMD-160(SHA-256(input)), 20 bytes. Text and hex hashing uses the audited @noble/hashes library; files use your browser’s built-in WebCrypto.

Worked examples

  1. SHA-256 of “hello world”

    Text input: hello world (11 bytes, UTF-8)

    SHA-256 → b94d27b9934d3e08a52e52d7da7dabfac484efe37a5380ee9088f7ace2efcde9

    Change it to “Hello world” and every character of the hash changes — that avalanche effect is why hashes detect tampering.

  2. The empty string

    Text input: nothing (0 bytes)

    SHA-256 → e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855

    A well-known constant — if you see it, the thing you hashed was empty.

  3. Bitcoin’s genesis block hash

    Hex input: the 80-byte block header of block 0 (version, previous hash, merkle root, time, bits, nonce).

    Double SHA-256 → 6fe28c0a…68d6190000000000; reversed byte order → 000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f

    That reversed value is the genesis block hash shown on every block explorer — the leading zeros are the proof of work.

Frequently asked questions

What is SHA-256?
SHA-256 is a cryptographic hash function from the SHA-2 family, published by NIST. It maps any input to a 256-bit (32-byte) output. It is one-way — you cannot recover the input from the hash — and no practical collisions are known.
How is SHA-256 used in Bitcoin?
Bitcoin uses double SHA-256 for block hashes, transaction IDs, the merkle tree, and Base58Check address checksums. Mining is a search for a block header whose double SHA-256 is below the difficulty target. Addresses use HASH160, which is RIPEMD-160 applied to the SHA-256 of a public key.
How do I verify a file’s SHA-256 checksum?
Switch to File, choose the downloaded file, and paste the checksum published by the developer into the verify box. A green match means the file is byte-for-byte identical. On the command line: sha256sum file (Linux), shasum -a 256 file (macOS), or certutil -hashfile file SHA256 (Windows).
Can SHA-256 be reversed or decrypted?
No. Hashing is not encryption — there is no key and no way to decrypt. Short or common inputs can be guessed by brute force or lookup tables, which is why passwords need a slow, salted hash like Argon2 or bcrypt rather than plain SHA-256.
What is the difference between SHA-256 and Keccak-256?
They are different algorithms with different outputs. SHA-256 (SHA-2 family) is used by Bitcoin; Keccak-256 (the pre-standard SHA-3) is used by Ethereum and Solidity. Use our Keccak-256 generator for Ethereum selectors and topics.
Is my text or file uploaded?
No. Everything is hashed in your browser — text and hex with @noble/hashes, files with the built-in WebCrypto API. Nothing you type or choose is sent to our servers.

Related crypto tools

How it works

  • Choose Text, Hex, or File and enter your input — or load an example like the Bitcoin genesis block header.
  • We compute SHA-256 locally (the @noble/hashes library for text and hex, WebCrypto for files) and derive double SHA-256 and HASH160 from it.
  • Copy any output with or without a 0x prefix, or paste a published checksum to confirm the input matches.

For education only — not financial advice. Past performance does not guarantee future results.