Developer
Encoders, converters & dev utilities
SHA-256 Hash Generator
Generate the SHA-256 hash of any text or file. SHA-256 (from the SHA-2 family, FIPS 180-4) is a 256-bit digest, printed as 64 lowercase hex characters, computed in your browser with the Web Crypto API. It is the modern default for integrity checks, download checksums, digital signatures, blockchain, and certificate fingerprints, with no known practical collision. Worked example: SHA-256("abc") = ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad (the FIPS-180 test vector). You can also paste a publisher-provided checksum and get an instant match / no-match verdict. All hashing is client-side, so your input never leaves the page. Free, no login.
SHA-256 (SHA-2, FIPS 180-4) = a 256-bit digest → 64 lowercase hex characters; the recommended default
- Byte-exact test vector: SHA-256("abc") = ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad
- In the browser: crypto.subtle.digest("SHA-256", bytes) — native Web Crypto, no library needed
- No known practical collision — safe for checksums, signatures, and certificate fingerprints
- One-way, not encryption; for PASSWORDS use bcrypt/scrypt/argon2, not a fast hash; 100% client-side
Frequently asked questions
How do I generate a SHA-256 hash?
Paste text or drop a file and the tool computes its SHA-256 digest — a 256-bit value shown as 64 hex characters — using the browser Web Crypto API (crypto.subtle.digest). For example SHA-256("abc") is ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad, the published FIPS-180 test vector. It runs entirely in your browser, so nothing is uploaded.
How do I verify a file with its SHA-256 checksum?
Drop the downloaded file into the tool to compute its SHA-256, then paste the checksum the publisher provided; the tool compares the two and tells you match or no-match. If they are identical the file is intact and untampered; if they differ the download is corrupt or has been modified. Because the hash is computed client-side over the file bytes, you never upload the file to check it.
Should I hash passwords with SHA-256?
No. SHA-256 is a fast hash, which is exactly what makes it wrong for passwords — an attacker who steals the database can try billions of guesses per second. Passwords should be stored with a slow, salted, memory-hard algorithm designed for the job: bcrypt, scrypt, or argon2. Use SHA-256 for integrity, checksums, and signatures, not for password storage.