Hash Generator

Use it when your task matches one of these common needs: Create a quick SHA-256 digest for a text sample. Compare whether two pasted text values produce the same digest. It works best when you already know the text, code, URL, mode, format, or technical setting the page asks for.

In plain language: The tool uses TextEncoder to turn text into UTF-8 bytes, calls browser crypto.subtle.digest() with SHA-256, SHA-384, or SHA-512, then writes each digest byte as two lowercase hexadecimal characters. SHA-256 returns 32 digest bytes, SHA-384 returns 48, and SHA-512 returns 64. The examples on the page are there so you can compare your inputs with a filled-out example before copying the answer.

Algorithm: Choose SHA-256 for the common 32-byte digest, SHA-384 for a 48-byte digest, or SHA-512 for a 64-byte digest. Text to hash: Paste the exact text you want to digest. Case, spaces, punctuation, emoji, and line breaks all change the output. Input bytes: This is the UTF-8 byte length of your text before hashing. It can be different from the character count when the text includes emoji or non-English characters. Hex digest: The result is lowercase hexadecimal text. Two hex characters represent one digest byte.

Read the output next to your original input. If the tool changes format, units, encoding, spacing, or capitalization, compare a small sample before copying the whole result into another app.

A hash is not encryption, a login design, or proof of who created text. Do not use raw hashes for password storage, signatures, API secrets, or authenticity checks; those need salts, key-derivation functions, HMACs, signatures, and security-specific code. Also check the selected mode, input format, encoding, and whether the text includes private keys, passwords, or sensitive data.

No. Encryption is designed to be reversed with a key. A SHA-2 hash is a one-way digest, so this page cannot decrypt the output back into the original text.

Hash functions are built so small input changes create very different digests. Changing a capital letter, adding a trailing space, or changing a line break should produce a new hash.

SHA-256 returns 32 digest bytes. Hex uses two characters per byte, so 32 bytes become 64 lowercase hex characters. SHA-384 becomes 96 hex characters, and SHA-512 becomes 128.

No. Password storage needs a password-hashing design such as a modern salted key-derivation function with security parameters. A raw SHA digest is not enough.

No. This page is for text. File hashing needs a file picker, visible file-size limits, browser memory notes, and clear handling for large or binary files.

No. A matching digest can show that two exact text values match, but it does not prove the sender or owner. Authenticity checks need HMACs, digital signatures, or another trusted system.

No. The tool runs in your browser tab. Your recent answers stay only on the page while you use it, and they are not sent to a server.