The abc fixture
The SHA-256 digest of the three UTF-8 bytes abc is ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad. A trailing newline changes it.
Text is hashed exactly as entered, including spaces and newlines. No Unicode normalization is applied.
Uses the browser Web Crypto API over HTTPS. Text input is limited to 250,000 UTF-16 code units. Files are read into memory only when you generate a hash. A digest detects byte differences; authenticity requires a trusted expected digest. This tool does not encrypt data or provide password hashing.
Conversions run locally in your browser. This tool does not upload input or save it to browser storage.
How to use the Hash Generator
- 01
Choose text/encoded bytes or a local file up to 10 MiB.
- 02
Select the hash algorithm and, for text, the input encoding. SHA-1 is included only for legacy compatibility.
- 03
Generate the hash, then choose hexadecimal, Base64, or unpadded Base64url representation.
- 04
Optionally paste a full hexadecimal digest to compare, then copy or download the result.
Examples
Same bytes, different input formats
UTF-8 abc, hex 616263, and Base64 YWJj all describe the same three bytes and produce the same digest with the same algorithm.
A hash describes bytes
Text is encoded as UTF-8 unless another input encoding is selected. The tool adds no newline and applies no Unicode normalization. Browser text fields can normalize line endings, so the file mode is preferable when original file bytes must be preserved.
Output encoding is only a representation
SHA-256, SHA-384, and SHA-512 produce 256, 384, and 512 bits respectively. Hex, Base64, and Base64url display the same digest bytes in different alphabets. SHA-1 produces 160 bits and has broken collision resistance, so it is a legacy option.
What a matching digest establishes
A digest can help identify accidental byte differences. To check a download’s authenticity, obtain its expected digest through a trusted channel. An attacker who can replace both the file and its posted checksum can make them agree. Ordinary fast hashes are not password-storage schemes.
What to know
- 10 MiB file limit; files are read into memory. Text input limited to 250,000 UTF-16 code units.
- Requires a modern browser with Web Crypto over HTTPS. SHA-1 is legacy only.
Common questions
Does the tool upload a selected file?
No. The browser reads the file into memory after you press Generate hash and uses its local Web Crypto API. The tool does not send the file or its digest to a server.
Can I hash an empty string?
Yes. Empty input is a valid byte sequence with a well-defined digest. Clear the input and explicitly generate the hash.
Why is my checksum different from another tool?
Check the algorithm, input encoding, whitespace, line endings, byte-order mark, and Unicode composition. A hex string interpreted as text differs from the bytes it spells.