SHA-256 Hash Generator
Calculate the SHA-256 of text or a file, check a download against its published checksum, or sign with HMAC-SHA256. Runs on your device, no upload.
0 characters
Runs in your browser. Nothing you enter is uploaded.
How to use
This page calculates SHA-256, the hash most downloads, package managers and APIs rely on today: 64 hexadecimal characters that identify a text or a file.
- Type or paste under Text, or open the File tab and pick a file. Its SHA-256 shows straight away.
- Copy takes the hash. Choose Output for uppercase hex or Base64 when a system asks for those.
- To verify a download, paste the checksum from the project's site into Compare with an expected hash. A whole SHA256SUMS file works too: the page looks up the line with your file's name.
- For signing, switch on HMAC with a key, enter the secret as text, hex or Base64, and copy the HMAC-SHA256. That's what Stripe, GitHub and Slack webhooks use.
- Show the other hashes too adds SHA-512, SHA-384, SHA-1, MD5 and CRC32 for the same input.
A match means the bytes on your disk are the bytes the publisher hashed. It says nothing about the publisher: take the checksum from a page you trust, over HTTPS, and not from the same mirror the file came from.
SHA-256 is the right default for integrity checks and signatures. It is the wrong tool for storing passwords on its own, because it is built to be fast and a graphics card can try billions a second; password storage needs a slow scheme such as Argon2 or bcrypt.
Hashing happens on your device. A file isn't uploaded, and a key typed for HMAC is forgotten when the page closes.
Frequently asked questions
How do I verify a download with its SHA-256 checksum?
Open the File tab, choose the downloaded file, then paste the published checksum (or the whole SHA256SUMS file) into the compare box. "Match" means the file arrived complete and unaltered. No match usually means an interrupted download, so fetch it again.
How do I make an HMAC-SHA256 signature?
Put the message under Text exactly as it will be sent, turn on HMAC with a key, and enter the shared secret. Pick the output the API expects: most want lowercase hex, some Base64. One extra space or line break in the message changes the whole signature.
Should I store passwords as SHA-256 hashes?
No. SHA-256 is designed to run fast, which lets an attacker test billions of guesses a second against a stolen table. Use a password hashing function such as Argon2, scrypt or bcrypt, which are slow on purpose and add a salt for you.
Related tools
- MD5 hash generator Get the MD5 hash of text or of a file up to 1 GB, and compare it with a checksum you were given.
- Hash generator Get CRC32, MD5, SHA-1, SHA-256 and SHA-512 hashes of text or files, make HMACs, and check a download against its checksum or a SHA256SUMS file.
- JWT decoder Decode a JSON Web Token to see its header, payload and expiry, check its signature with a secret or public key (RS256, ES256), and sign a changed one.
More encoding tools
- Base64 encoder Encode text or files to Base64 and decode Base64 back to text or a file.
- URL encoder Percent-encode or decode URLs and query strings in your browser.