The standard SHA-256 text vector
abc · SHA-256 · hexadecimal
Produces ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad, making it easy to check browser and integration behavior against a well-known test value.
🔐Hash GeneratorReady
Local, one-shot hashing. Text and selected files are read only in this browser and are not uploaded by this tool. A digest is useful for an integrity comparison, not encryption, a signature, malware scanning, or password storage.
256-bit digest. The usual choice for modern integrity checks.
Ctrl/Cmd + Enter to hash
Empty text is a valid input and has a digest. The one-shot browser limit is 25.00 MB after UTF-8 encoding.
Use a trusted expected digest. A matching checksum says these two values match; it does not authenticate the place where the checksum came from. For passwords, use a dedicated password-hashing system with a unique salt and work factor—fast SHA digests are deliberately the wrong primitive.
Capability checkedVerified September 9, 2026
What works
- Encode pasted text with the browser UTF-8 TextEncoder or read one selected file as raw browser-memory bytes
- Calculate one selected SHA digest through the browser Web Crypto digest API without making a network request
- Strictly parse a raw expected checksum before comparing its decoded bytes to the computed digest
Important limits
- A matching digest only shows that two byte sequences match; it does not establish that the expected checksum came from a trustworthy publisher or that a file is safe
- Fast SHA digests are not password hashing and do not add a unique salt, work factor, memory cost, authentication, encryption, or digital signature
What the Hash Generator does—and does not do
Exact supported inputs, outputs, limits, and primary sources for the current implementation.
Accepted input
- Pasted Unicode text, including an empty value, encoded as UTF-8 up to 25 MiB after encoding
- One locally selected or dropped file up to 25 MiB, hashed as its exact raw bytes
- One raw expected digest in canonical hexadecimal, Base64, or Base64URL form for the selected algorithm
Produced output
- A SHA-1, SHA-256, SHA-384, or SHA-512 digest in selected lowercase hexadecimal, Base64, or unpadded Base64URL form
- A labelled copy value containing all three output encodings
- A clear match, mismatch, or malformed/incorrect-length expected-checksum result
Operational limits
- Web Crypto digest is a one-shot operation here, so text and one file are capped at 25 MiB and streaming or multi-file hashing is not provided
- The browser Web Crypto SHA interface provides SHA-1, SHA-256, SHA-384, and SHA-512; SHA-3, BLAKE, MD5, and custom algorithms are not available in this workbench
- Expected comparison accepts the digest alone, not a whole checksum manifest line, filename, signed release metadata, or detached signature
Known limitations
- A matching digest only shows that two byte sequences match; it does not establish that the expected checksum came from a trustworthy publisher or that a file is safe
- Fast SHA digests are not password hashing and do not add a unique salt, work factor, memory cost, authentication, encryption, or digital signature
- The workbench uses the visitor's browser implementation and does not claim a FIPS-validated cryptographic module or replace a system's required verification procedure
Standards and primary sources
Continue the workflow
Capability claims last reviewed September 9, 2026. Review dates describe the implementation audit, not content freshness by itself.
Use the Hash Generator with the right expectations
A useful hash page makes the byte boundary and the trust boundary visible. This workbench hashes pasted text as UTF-8 or a chosen file as exact raw bytes, lets you choose one browser-supported SHA algorithm instead of silently emitting several, and keeps SHA-1 behind a legacy-only warning. It also recognizes a canonical expected checksum in hexadecimal, Base64, or Base64URL, checks that it has the right digest length, and compares decoded bytes rather than merely comparing a display string.
When it is the right tool
- Checking a downloaded file against a SHA-256 checksum from a trusted publisher
- Seeing exactly how Unicode text becomes UTF-8 bytes before it is hashed
- Converting one SHA digest between hexadecimal, Base64, and Base64URL representations
- Comparing an inherited SHA-1 checksum while keeping it out of a new design
A deliberate choice
Tooleras keeps this page specific to the job above instead of claiming support for adjacent formats, platforms, or edge cases it cannot verify. Open the capability guide for the exact inputs, outputs, limits, and sources.
Checked examples
A publisher checksum
release.zip + one raw SHA-256 value from the publisher
Reads the local file bytes, validates that the expected digest has the correct SHA-256 length and canonical encoding, then reports an exact match or mismatch without opening or uploading the file.
Need a different tool?
Browse the full catalogue — all free, with data handling documented per tool.