Hash Generator
SHA hashes via the Web Crypto API.
LocalYour data is processed locally in your browser and is not uploaded to Alphzen.
SHA algorithms use the Web Crypto API. MD5 is a legacy checksum, not a password hash. File hashing stays in this tab.
How to use
- Paste text, or choose a file. The file is read locally and is not uploaded.
- Select one or more algorithms.
- Hash, then copy hex or Base64.
Features
- SHA-1, SHA-256, SHA-384, and SHA-512 via crypto.subtle.digest.
- MD5 included only as a legacy checksum, with an explicit warning.
- Hex and Base64 output.
- Optional file hashing in the browser.
- Does not send the input to Alphzen.
Examples
(empty)
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
FAQ
Is hashing encryption?
No. A hash is one-way. You cannot get the original text back from SHA-256. Encryption is reversible with a key.
Should I hash passwords with this tool?
No. Password storage needs a slow, salted KDF such as Argon2 or bcrypt, done on a server you control. This page is for checksums and fingerprints.
Why is MD5 still here?
Some systems still publish MD5 checksums. It is not collision-resistant. Do not use it to prove authenticity.
Related tools
About this tool
A cryptographic hash maps arbitrary input to a fixed-size digest. SHA-256 and SHA-512 are the usual choices on this page. SHA-1 and MD5 remain because legacy checksums still exist, not because they are good password hashes.
Alphzen computes SHA family digests with the Web Crypto API. MD5 is implemented locally as a checksum and labelled as such.
The input stays in the tab. For JWTs, decoding is a different job — use the JWT Decoder.