SHA-256 Checker
Generate SHA-256 hashes for text and files, and verify any checksum - all in your browser
100% free. Runs entirely in your browser - your files and data never leave your device and nothing is uploaded to any server.
With a key the result is HMAC-SHA-256 - a keyed signature used by APIs and webhooks. The key never leaves this page.
Your 64-character hexadecimal hash will appear here.
SHA-256 is a one-way hash, not encryption. It proves data is unchanged; it does not hide or protect it.
Hash history
Only hashes and file names are kept, in this browser. Your text and files are never stored.
Hashes you generate, copy or download appear here.
SHA-256 commands
The same hash from the command line or code - useful for scripts, CI and API testing.
sha256sum "file.iso"
sha256sum * > SHA256SUMS
sha256sum -c SHA256SUMS
echo -n 'hello world' | sha256sum
SHA-256 vs SHA-1 vs SHA-512
| Algorithm | Output | Hex length | Today |
|---|---|---|---|
| MD5Collisions in seconds - only for non-security checks | 128-bit | 32 | Broken |
| SHA-1Practical collisions since 2017 - legacy only | 160-bit | 40 | Broken |
| SHA-256Default for checksums, TLS, code signing and Bitcoin | 256-bit | 64 | Secure |
| SHA-512Longer output, often faster on 64-bit CPUs | 512-bit | 128 | Secure |
Never store passwords as a plain SHA-256 hash - use bcrypt, scrypt or Argon2, which are slow on purpose.
SHA-256 examples
Known inputs and their hashes - handy for testing your own code. Click one to try it.
Free online SHA-256 hash generator and file checksum verifier
Generate a SHA-256 hash from text, JSON or any file, and check a checksum without opening a terminal. Type or paste text and the 64-character hash updates as you type; drop one file or a whole folder's worth and each one is hashed with its own progress bar, ready to copy, download as a .sha256 file or export as a SHA256SUMS manifest. The Verify tab compares any two hashes and tells you straight away whether they match - and paste a checksum list and every file is checked by name. Everything runs locally in your browser: files are read in chunks on your device, so even multi-gigabyte ISOs work, and nothing is uploaded.
How to use this tool
- Choose Text Hash, File Hash or Verify HashText Hash works on typed or pasted text and JSON, File Hash takes one file or a batch, and Verify Hash compares a hash with the checksum you expect.
- Add your text or filesPaste text exactly as it will be used - every space and line break counts. For files, drag them onto the box or click to browse; you can add as many as you like.
- Generate the SHA-256 hashText is hashed as you type; press Generate SHA-256 to save it to your history. Files are hashed one after another with a progress bar, then show their 64-character result.
- Copy, download or verifyCopy one hash or all of them, download a TXT or CSV checksum file, or switch to Verify Hash and paste the published checksum to get a clear match or mismatch.
What is SHA-256?
SHA-256 is a cryptographic hash function from the SHA-2 family, published by the US National Institute of Standards and Technology (NIST) in FIPS 180-4. It turns any input - one character or a 50 GB disk image - into a fixed 256-bit value, written as 64 hexadecimal characters.
The same input always gives the same hash, but changing a single bit gives a completely different one. No practical way is known to find two inputs with the same SHA-256 hash or to work back from a hash to the data, which is why it is used for download checksums, TLS certificates, code signing, Git and Bitcoin.
How SHA-256 works
The input is padded and split into 512-bit blocks. Each block passes through 64 rounds of bitwise operations - rotations, shifts, additions and logical functions - that mix it into eight 32-bit working values. The final eight values, joined together, are the 256-bit hash.
Because each round depends on every previous one, the output behaves like a fingerprint: it is quick to compute, always the same length, and impossible to predict without doing the whole calculation. That also makes it a one-way function - hashing is not encryption, and there is no key that turns a hash back into the original data.
How to generate a SHA-256 hash
For text, open Text Hash and type or paste your input - the hash appears as you type. Text is encoded as UTF-8 and every space, tab and line break is kept, so the result matches what code and command-line tools produce for the same bytes.
For files, open File Hash and drop one or more files. Each file is read in chunks on your device and gets its own 64-character hash, which you can copy, download as a .sha256 file or export with the others as a SHA256SUMS manifest or CSV.
- JSON: switch to JSON to validate it, and optionally minify it or sort its keys before hashing
- echo compatibility: turn on Add trailing newline to match echo without -n
- Windows text files: turn on Windows line endings to hash line breaks as CRLF
- API signatures: add a secret key to get HMAC-SHA-256 instead of a plain hash
How to verify file integrity with SHA-256
Find the checksum on the publisher's official download page, then hash the file you downloaded and compare the two. In the Verify Hash tab, pick File, drop the download and paste the published checksum; a green Match means the file is byte-for-byte identical, a red Mismatch means it is not.
For a whole release, drop the files together with their SHA256SUMS list on the File Hash tab - each file is matched by name. On the command line the same check is one command per system:
- Windows (Command Prompt): certutil -hashfile file.iso SHA256
- Windows (PowerShell): Get-FileHash file.iso -Algorithm SHA256
- macOS: shasum -a 256 file.iso
- Linux: sha256sum file.iso, or sha256sum -c SHA256SUMS to check every file in a list
SHA-256 vs SHA-1 vs SHA-512
MD5 (128-bit, 32 hex characters) and SHA-1 (160-bit, 40 hex characters) are broken: researchers can create two different files with the same hash, and a practical SHA-1 collision was published in 2017. They still catch accidental corruption but should not be trusted against tampering.
SHA-256 (256-bit, 64 hex characters) and SHA-512 (512-bit, 128 hex characters) are both secure members of SHA-2. SHA-256 is the most widely published checksum and the default in most tools; SHA-512 gives a longer output and is often faster on 64-bit processors. Use whichever one the publisher lists.
SHA-256 examples
These standard test values are useful for checking your own code. Note how a single trailing newline changes the result completely.
- Empty string: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
- abc: ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad
- hello world: b94d27b9934d3e08a52e52d7da7dabfac484efe37a5380ee9088f7ace2efcde9
- hello world with a newline (echo): a948904f2f0f479b8f8197694b30184b0d2ed1c1cd2a1ec0fb85d299a192a447
Key features
- Text hashing, batch file hashing and checksum verification in one free tool, with no account.
- Files are hashed locally in chunks, so large ISOs and backups work without uploading anything.
- Checks a whole SHA256SUMS list at once - every file gets its own match or mismatch badge.
- Comparison is case-insensitive and accepts sha256sum, shasum --tag and certutil output as pasted.
- Developer options: JSON minify or sorted keys, CRLF line endings, trailing newline and HMAC-SHA-256 with a secret key.
- Copy-ready commands for Windows, PowerShell, macOS, Linux, JavaScript, Node.js and Python.
Common uses
- Confirming a Linux ISO, Windows installer or firmware file downloaded correctly and was not tampered with.
- Producing a SHA256SUMS file to publish next to a release or share with a client.
- Checking that files copied to a USB stick, NAS or cloud drive are identical to the originals.
- Hashing a JSON request body or creating an HMAC-SHA-256 signature while testing an API or webhook.
- QA checks that a build artefact or export has not changed between two runs.
Tips for better results
- Always compare the full 64 characters. Checking only the first and last few is exactly what a crafted look-alike file relies on.
- Take the expected checksum from the official site over HTTPS - a checksum hosted next to a tampered file proves nothing.
- If your hash differs from a terminal result, check for a trailing newline: echo adds one unless you use echo -n.
- For webhooks, sign the raw request body exactly as received. Pretty-printed or re-serialised JSON gives a different result.
- Drop the SHA256SUMS file together with the files it lists and every file is verified automatically.
Mistakes to avoid
- Thinking a matching hash proves who made the file. It only proves the file is unchanged - use a signature or HMAC for origin.
- Using plain SHA-256 to store passwords. It is designed to be fast; passwords need bcrypt, scrypt or Argon2.
- Calling SHA-256 encryption. A hash cannot be decrypted - it is a one-way fingerprint of the data.
- Comparing a hash of the file name or path instead of the file contents.
- Treating a matching checksum as a virus scan. It proves the file is the one the publisher released, not that the publisher is trustworthy.
Frequently asked questions
Open File Hash and drop the file, or open Verify Hash, choose File and paste the checksum from the download page. The tool hashes the file in your browser and shows a green match or red mismatch. No terminal or software install is needed.
No fixed limit. Small files are hashed with the browser's built-in Web Crypto; larger files are read in 8 MB chunks and hashed as a stream, so memory use stays low even for multi-gigabyte ISOs. Speed depends on your device - typically 100-300 MB per second.
No. Files and text are processed by JavaScript running in your browser, and the hashing happens in a background worker on your device. Nothing is sent to our servers and nothing is stored - only the hashes you choose to keep in your local history, which you can clear at any time.
Yes. Drop or select as many files as you like. Each is hashed in turn with its own progress bar, and you can copy all hashes, download a SHA256SUMS text file or export a CSV with file names, sizes, types and hashes.
Drop the SHA256SUMS file together with the files, or open Verify against a checksum list and paste its contents. Each file is matched by name and marked Match, Mismatch or Not in list. GNU sha256sum, BSD shasum --tag and name-then-hash formats are all understood.
No. Hexadecimal hashes mean the same thing in upper or lower case, so the checker compares them case-insensitively and also ignores spaces and colons. You can display your results in lowercase or UPPERCASE to match another tool.
Almost always the bytes differ: a trailing newline (echo adds one), Windows CRLF line endings, extra spaces, or a different text encoding. Use the Options to add a trailing newline or CRLF line endings and compare again.
No. SHA-256 is a one-way hash, not encryption - there is no key and no way to turn the hash back into the data. Short or common inputs can be guessed by trying candidates, which is why plain SHA-256 must not be used to store passwords.
No. SHA-256 is designed to be fast, which helps attackers try billions of guesses. Store passwords with a slow, salted algorithm such as bcrypt, scrypt or Argon2.
HMAC-SHA-256 combines SHA-256 with a secret key. Only someone who knows the key can produce the same value, so it proves a message is authentic as well as unchanged. Stripe, GitHub, Shopify and many APIs sign webhooks this way. Turn on HMAC key in the Text Hash tab to create one.
The file is not byte-for-byte the one the publisher hashed. Usually the download was interrupted or corrupted, or the checksum belongs to a different version or edition. Download it again from the official source and re-check; if it still fails, do not run or install it.
Always 256 bits, which is 32 bytes, 64 hexadecimal characters or 44 Base64 characters - whatever the size of the input.