Generate SHA-256, SHA-384, or SHA-512 digests locally in the browser using Web Crypto.
Last updated: August 2026 | By Workshelve Team
SHA-2 output will appear here...
Input bytes
0
Hash chars
0
Digest size
256 bits
This tool hashes the UTF-8 bytes of the text you enter. SHA-256 outputs 32 bytes / 64 hex characters, SHA-384 outputs 48 bytes / 96 hex characters, and SHA-512 outputs 64 bytes / 128 hex characters.
SHA-2 hashing is deterministic and one-way: the same bytes always produce the same digest, even a one-byte change will ordinarily produce a completely different-looking digest, and the digest is not something you can decrypt back into the original text.
Hashing is performed locally with Web Crypto and this component does not send the input anywhere. Empty text is valid and has a defined digest, but raw SHA-2 is not appropriate for password storage and this tool hashes text only, not files.
SHA-2 is a family of cryptographic hash functions that turns input bytes into a fixed-length digest. This tool offers SHA-256, SHA-384, and SHA-512. The output is shown as lowercase hexadecimal, which is just a text representation of the raw digest bytes.
The tool hashes the UTF-8 bytes produced by JavaScript's TextEncoder. That matters because hashing depends on exact bytes, not visual appearance. Two strings that look similar can hash differently if they use different Unicode code points or normalization forms.
Hashing is one-way and deterministic. The same bytes always produce the same digest, but there is no reverse operation that recovers the original text from the hash. That makes SHA-2 useful for fingerprints, integrity comparison, and signing workflows, but not for storing passwords by itself.
Each SHA-2 variant produces a different fixed-size digest:
Example 1: SHA-256 of the empty string
This is the standard SHA-256 digest of an empty byte sequence. A hash generator must allow it rather than rejecting blank input as invalid.
Example 2: Built-in sample text across all three variants
Each algorithm hashes the same UTF-8 bytes but produces a different digest length.
The tool hashes the UTF-8 bytes of the text you enter. If two strings differ by whitespace, casing, Unicode normalization, or any other byte-level detail, their digests will ordinarily differ too; cryptographic hashes are designed for collision resistance, not a mathematical guarantee that different inputs can never share a digest.
No. Encryption is designed to be reversible with a key. SHA-2 hashing is one-way and does not provide a decrypt operation that recovers the original text.
Because SHA-2 is defined for every byte sequence, including a zero-length message. The empty string has a standard digest for SHA-256, SHA-384, and SHA-512.
No. Raw SHA-2 is too fast for password storage. Use a password hashing or key-derivation scheme such as Argon2id, scrypt, bcrypt, or PBKDF2.
Not directly. This component hashes text typed into the textarea. File verification needs a file-hashing workflow that reads raw file bytes instead of text input.
They are different members of the SHA-2 family with different digest sizes: 256, 384, and 512 bits respectively. Longer digests produce longer hexadecimal output strings.