Input
Preparing your workspace…
How to use
- Enter a message and choose its encoding and hash algorithm.
- Select Generate, then choose Hex or Base64 output.
- Copy a digest, compare an expected value or download JSON.
Hash Generator
A digest is a fixed-length fingerprint of bytes. Use SHA-256 by default, select a specific algorithm, or inspect all five results together. Input encoding determines which bytes are hashed.
Copy a digest in Hex or Base64 and compare it with a complete expected value. These display choices do not alter the input bytes or require a new calculation.
Work with the input
Enter text, Hex or Base64. Choose the algorithm and output format; Sample fills a Unicode text example.
Select Generate. Copy a digest, compare it with an expected value, or download a result containing no secret input.
Hello, world! 👋a1c81e1c2c9dc291fa5fa6a35d8c77624e1d8f19d9f7ed6817739111dc699137Example data only. Never reuse sample secrets as real credentials.
Behavior and limits
This tool does not normalize text, remove whitespace or append a newline. Hex accepts byte-pair whitespace; Base64 uses the standard alphabet and strict padding. MD5 and SHA-1 are provided for legacy compatibility, not collision-resistant security or password storage.
Copy and reuse
Whitespace and line endings count. Use File Checksum when you need the hash of the original bytes of a file.
Copy all digests · Comparison uses the selected output format. With All algorithms, any matching digest is identified.
Input: 1 MiB; Secret key: 64 KiB; File: 1 GiB; Passwords: 4–128 (Length), 1–100 (Count); bcrypt: 1–72 UTF-8 bytes · cost 4–14 · default 10; AES: Plaintext 1 MiB, Passphrase 1 KiB, GCM / CBC / CTR / CFB / ECB, 128/192/256-bit; PBKDF2 / HKDF: Password / input bytes 64 KiB, Salt / info 1 KiB, Output length (bytes) 1–256; 1–256 output bytes · up to 2,000,000 PBKDF2 iterations · inputs stay on your device; Time: 30 s; File: 120 s.
Frequently asked questions
Can a hash be decrypted?
No. Hashing is not encryption and has no decryption key. A digest by itself does not authenticate the source of a message.
Why is my result different from a command-line hash?
Compare the exact input bytes. A final newline, BOM, encoding or CRLF/LF difference changes the digest.
Does changing Hex to Base64 require another calculation?
No. Output encoding changes the representation of the current digest bytes. Changing the input or algorithm requires Generate again.
Does JSON download include my message?
No. It includes the algorithm, digest, output format and input byte count, but not the source message.
Can I hash binary data?
Yes. Supply bytes as Hex or Base64, or use File Checksum for an original local file. Open text file accepts valid UTF-8 text only.