Tool 006 / dev / free / runs locally
Hash Generator
Type any text and get its SHA-1, SHA-256, SHA-384, and SHA-512 hashes as hexadecimal strings. Hashing uses the built-in Web Crypto API, so your input is processed entirely in your browser and never uploaded.
Hash will appear here.
Hash will appear here.
Hash will appear here.
Hash will appear here.
How it works
This tool computes cryptographic hashes of any text using the browser's Web Crypto API (crypto.subtle.digest). It generates SHA-1, SHA-256, SHA-384, and SHA-512 at the same time, so you can compare algorithms side by side. A hash is a fixed-length fingerprint of the input: the same text always yields the same hash, and changing a single character changes the entire output.
Your text is encoded to UTF-8 bytes, hashed natively by the browser, and the resulting bytes are shown as lowercase hexadecimal. SHA-256 produces 64 hex characters (256 bits), SHA-512 produces 128. Hashing is one-way: you cannot recover the input from the hash, which is why hashes are used for integrity checks and as building blocks in signatures.
All four digests are computed in your tab and nothing is uploaded. Note that SHA-1 is included for compatibility with legacy systems but is considered broken for collision resistance; prefer SHA-256 or stronger for anything new.
How to use it
- Type or paste the text you want to fingerprint into the input box.
- Watch all four hashes (SHA-1, SHA-256, SHA-384, SHA-512) compute instantly.
- Find the algorithm you need and click its Copy button.
- Compare against a known hash to verify integrity, or store it as a checksum.
Worked examples
Input: abc
Output: SHA-256: ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad
This is the well-known SHA-256 test vector for the string abc.
Input: Hello, Tools Nimbus
Output: Four different fixed-length hex strings, one per algorithm, all from the same input.
Each algorithm produces a different length: 40, 64, 96, and 128 hex characters.
Edge cases and limits
- This hashes text, not files. To checksum a file you would hash its raw bytes; this tool takes typed or pasted text encoded as UTF-8.
- Whitespace counts. A trailing space or a newline changes the hash entirely, which is the whole point of a hash but a common surprise.
- SHA-1 is here for legacy verification only. Do not rely on it for security-sensitive collision resistance.
- These are plain hashes, not password hashes. For storing passwords use a slow, salted function like bcrypt or Argon2 instead.
Common mistakes
- Comparing a hash you generated from text against a checksum that was computed over file bytes, including a trailing newline the file had and your text did not.
- Expecting to reverse a hash back to the original text. Hashes are one-way by design.
- Using SHA-256 of a password as if it were secure storage. Fast hashes are easy to brute-force; use a dedicated password hash.
Frequently asked questions
Why is there no MD5 option?+
Browsers do not expose MD5 through the native Web Crypto API, and MD5 is considered broken for security. We provide SHA-1, SHA-256, SHA-384, and SHA-512, which are the algorithms the browser supports natively.
Which hash should I use?+
Use SHA-256 for general purposes like checksums and fingerprints. Use SHA-384 or SHA-512 when you want a longer digest. SHA-1 is included for legacy compatibility only.
Can I reverse a hash back to the original text?+
No. Cryptographic hashes are one-way functions. You cannot recover the original input from the hash, which is exactly why they are used for integrity checks.
Related tools
More Developer tools that run entirely in your browser.