Loading tool…
Loading tool…
Compute SHA-256, SHA-1, and MD5 hashes for text and files.
Was this tool useful?
Does this hash generator upload my text or files to any server?
No. All hashing is performed locally in your browser using JavaScript and the Web Crypto API. Your text, files, and hash results never leave your device.
Why does the tool warn that MD5 and SHA-1 are insecure?
MD5 and SHA-1 are considered cryptographically broken and should not be used for password storage or security systems. They are provided here only for checksums, debugging, and compatibility with legacy systems.
Can I hash files as well as text?
Yes. You can switch between Text mode and File mode. In File mode, the tool reads your selected file and computes the chosen hashes entirely in the browser without uploading anything.
What is the difference between hex and Base64 output?
Hex encodes each byte as a two-character string, which is common for checksums. Base64 is a compact text encoding useful for APIs and data URIs. Both represent the same underlying hash value.
Why can I choose lowercase or UPPERCASE hex?
Hexadecimal characters are case-insensitive, but different tools and systems prefer different casing. This option ensures compatibility with whatever format you need.
Why do I need to select at least one algorithm?
The tool supports MD5, SHA-1, SHA-256, and SHA-512. If no algorithm is selected, hashing cannot proceed. You may enable any combination of the four.
Why does hashing fail in some older browsers?
SHA algorithms require the Web Crypto API (`crypto.subtle`). Older browsers, in-app browsers, or some privacy-focused browsers may not support it, preventing SHA hashing. MD5 text hashing will still work because it is implemented in pure JavaScript.
Why is the hash different when I hash text vs a file?
Files are hashed as raw bytes, whereas text is hashed after being encoded with UTF-8. Even visually identical content may differ at the byte level, which produces different hash values.