Quick reference
| Setting | Value / behavior |
|---|---|
| SHA-256 | 64 hex characters |
| SHA-384 | 96 hex characters |
| SHA-512 | 128 hex characters |
How to use the result
A cryptographic hash maps input bytes to a fixed-size digest. This tool converts text to UTF-8 and uses the browser Web Crypto implementation to compute SHA-256, SHA-384 or SHA-512. Output is lowercase hexadecimal, with two hex characters for each digest byte. SHA-256 therefore produces 64 characters. A tiny change in the input, including a trailing newline or a different Unicode representation, usually produces a completely different digest.
Limits and interpretation
A plain digest is not encryption and cannot be decrypted to recover the original message. It is also not a suitable password-storage scheme: passwords need a salted, deliberately expensive password-hashing construction in a trusted implementation. This page hashes text only, not uploaded files, and it does not implement HMAC or a digital signature. When comparing checksums, ensure both sides used the same algorithm and the same exact bytes, including line endings and normalization.
Check against your destination
Run the supplied example first, then replace it with a representative input from your own workflow. Change one parameter at a time so the effect is easy to inspect. Copy or download the output and compare it with a small known case before using it in a larger system. A successful calculation establishes only the behavior described on this page; it cannot check the assumptions or access rules of a remote application. Errors are shown next to the workspace rather than silently returning an empty success.
Local processing and data handling
This tool runs in the browser and does not transmit the entered content to a processing service. No input is saved to local storage, added to the URL or synchronized to an account. The clear control removes the current field and displayed result from this page. Clipboard contents and downloaded files remain under your operating system’s control. Keep original inputs when exact byte preservation matters, and avoid including sensitive tokens or private text in screenshots that you later share.
Frequently asked questions
Does the tool contact my server?
No. It processes the provided input locally and does not execute commands on your systems.
Can I download the result?
Yes. Use the Download result control after a successful run.
What happens to my input?
It remains in this page until cleared or closed. It is not saved by the tool.
About this tool
Built and maintained by Mihai at Void Fabric. This page documents the behavior of the current implementation. Found an error or an unclear assumption? Send a reproducible example with sensitive values removed.
Reference: Void Fabric field notes · Testing and editorial policy