SHA-256 Hash Generator

Paste text or drop a file and get its SHA-256 digest instantly. Hashing happens in your browser; the input never leaves your device.
Client-side · verifiable
How this tool works

SHA-256 is a member of the SHA-2 family standardised by NIST in FIPS 180-4. It pads the input to a multiple of 512 bits and pushes each block through 64 rounds of mixing to produce a 256-bit digest, shown as 64 hex characters. The same input always gives the same digest, a single changed bit flips about half the output bits, and there is no known way to run the process backwards.

This page calls crypto.subtle.digest("SHA-256", bytes), the hashing primitive built into every modern browser. Files are read in 4 MB chunks and hashed incrementally, so a large disk image works without loading it into memory.

Typical uses:

  • verifying a download against the checksum on the publisher’s page
  • fingerprinting documents, images and container layers
  • the hash inside HMAC-SHA256 signatures, JWT HS256 tokens and Bitcoin mining

What it is not for: storing passwords. SHA-256 is fast by design, and attackers can test billions of candidates per second against a leaked hash. Use bcrypt or Argon2 for that.

Security note

What leaves your browser

Text is hashed in memory with the Web Crypto API; files are read in chunks with the File API and hashed in WebAssembly. There is no upload endpoint on this page. Open DevTools → Network and hash something: no request appears.

FAQ
Is SHA-256 still secure in 2026?

Yes. No practical collision or preimage attack exists. It anchors TLS certificates, code signing, Git's new object format and most blockchain systems.

What is the difference between SHA-256 and SHA-512?

Output length (256 vs 512 bits) and internal word size (32 vs 64 bits). SHA-512 is faster on 64-bit CPUs; SHA-256 is more widely supported and plenty strong.

How do I verify a downloaded file's checksum?

Switch to the File tab, drop the file, then paste the publisher's checksum into the compare box. A green match means the file is byte-for-byte identical.

Can a hash be decrypted?

No. Hashing is not encryption; there is no key and no inverse function. The only way to find an input is to guess candidates and compare hashes, which is exactly why password hashes must be slow.

Why does the same text give a different hash on another site?

Usually a trailing newline, different line endings, or a different text encoding. Hash the exact bytes and the results agree everywhere.