About the Hash
The hash generator computes cryptographic digests of any text you enter, producing SHA-1, SHA-256, SHA-384 and SHA-512 hashes at once. It uses the browser's built-in Web Crypto API, so the results match standard implementations you would get from command-line tools.
Use it to verify file or string integrity, generate checksums, compare against a known hash, or quickly produce a digest while developing. Everything is computed locally in your browser, so the text you hash never leaves your device.
How to use it
- Type or paste the text you want to hash into the input box.
- Let the tool compute the digests automatically as you type.
- Read the SHA-1, SHA-256, SHA-384 and SHA-512 results.
- Copy the hash you need.
- Compare it against an expected value to verify integrity.
Examples
- Hash the string hello and get its SHA-256 digest 2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824.
- Generate a SHA-512 checksum of a config snippet to compare against a value published by a vendor.
- Produce a SHA-256 hash of an API payload while debugging a signature mismatch.
Frequently asked questions
What hash algorithms are supported?
The tool computes SHA-1, SHA-256, SHA-384 and SHA-512 digests of the text you enter, all at the same time using the browser's Web Crypto API.
Is my text sent to a server?
No. Hashing runs entirely in your browser via the Web Crypto API, so the text you enter is never uploaded or stored anywhere.
What is the difference between SHA-256 and SHA-512?
Both belong to the SHA-2 family but produce different digest lengths: SHA-256 outputs 256 bits and SHA-512 outputs 512 bits. SHA-512 is longer and uses 64-bit operations, while both are considered secure.
Should I still use SHA-1?
SHA-1 is offered for compatibility and checksums, but it is no longer considered secure against collision attacks. Prefer SHA-256 or stronger for anything security-sensitive.
Can I hash a file with this tool?
This tool hashes text input. To check a file, you would typically paste its contents or use a command-line tool, since the digests here are computed from the text you provide.
Why might my hash differ from another tool's output?
Differences usually come from hidden characters, trailing newlines, or text encoding. The Web Crypto API hashes the exact bytes of your input, so make sure the input matches precisely.