SECURITY WORKSPACE
Hash Generator
Hash exact text bytes.
Input is processed on this site only when you run the tool. The application does not save inputs or results.
input.txt
Result result.txt
A little clarity goes here.
Run the tool to see your result.
Result preview
UTF-8 text, at most 262144 bytes per input. Tab leaves the editor. Plain text disables syntax colors. Browser textareas may normalize line endings to LF.
{"hash":{"inputMode":"text","options":{"algorithm":{"type":"enum","values":["md5","sha1","sha256","sha512"],"default":"sha256"}}}}{"hash":{"input":"hello","output":"2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824","options":{"algorithm":"sha256"}}}A QUICK WALKTHROUGH
A familiar workflow,
with room to focus.
Enter the exact UTF-8 text to hash, including intended whitespace.
Choose SHA-256, SHA-512, or an explicitly labeled legacy algorithm.
Generate the lowercase hexadecimal digest.
When to use Hash Generator
Compute a checksum for exact text, or compare an expected digest using the same encoding and algorithm.
Read the result
Changing a space or newline changes the digest. SHA-256/SHA-512 are available alongside explicitly legacy MD5/SHA-1; a plain hash is not a password-storage scheme or encryption.
SEE IT IN PRACTICE
Worked examples
Sample input. A result you can inspect.
Hash example
Input
hello
- Algorithm
- SHA-256
Expected result
2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824
Formats, limits and common errors
Different whitespace, line endings or Unicode sequences produce different digests. Compare exact bytes.
- MD5 and SHA-1 are legacy choices unsuitable for modern security-sensitive use; selecting either produces a warning.
- Hashing is one-way, not encryption or password storage. No HMAC, salt, password hashing or file uploads.
- Empty input is supported. PHP hashes the submitted bytes exactly. Browser textareas can normalize pasted line endings to LF; there is no additional server normalization.
- Input: 262,144 UTF-8 bytes per text field. Output: at most 524,288 UTF-8 bytes; serialized responses have a separate 1 MiB ceiling. Size/work failures return no partial result.