Hash Generator
SHA-256 by default, plus SHA-384, SHA-512, and SHA-1. Hash UTF-8 text or the bytes of a file you pick locally. Hex or Base64 output.
Tool input stays in your browserDid you know · Data
A UUID is 128 bits, usually printed as 32 hex digits in five hyphen-separated groups.
Text
you edit—Web Crypto, not a custom SHA
Digests come from crypto.subtle.digest. That is the same implementation the rest of the platform uses for SRI and certificate work. Text is encoded as UTF-8 before hashing, so a character that is not ASCII is not hashed as Latin-1. A file is hashed as raw bytes — the same checksum shasum would print for that file.
There is no MD5 here. Browsers do not expose MD5 through Web Crypto, and adding a third-party MD5 would only encourage a broken algorithm. If you need to verify an ancient checksum, use a dedicated local tool.
Hex versus Base64
Hex is the usual checksum form (lowercase). Base64 is what Content-Security-Policy sha256- hashes and some JWT-adjacent tooling expect. Switching output does not re-hash; it only reprints the same digest bytes.
SHA-1 is offered because git objects and older SRI still use it. Prefer SHA-256 or SHA-512 for anything new.
Why it is private
Hashing runs as JavaScript inside this page. Open DevTools, switch to the Network tab, and hash a secret or a file: no request carries that input. The file never leaves the machine; FileReader loads it into this tab's memory.
Hash generator FAQ
SHA-256 hash online, file checksums, SHA-1 vs SHA-256, hex vs Base64, and why there is no MD5.
What is a hash generator?
A hash generator computes a fixed-length digest of text or a file (checksum). This hash generator uses the Web Crypto API for SHA-256, SHA-384, SHA-512, and SHA-1. Output is hex (usual checksums) or Base64 (CSP sha256- style). There is no MD5.
How do I get a SHA-256 hash online?
Paste UTF-8 text or open a local file, leave the algorithm on SHA-256, and copy the hex. That is a SHA-256 checksum of the exact bytes (text encoded as UTF-8). The file is read with FileReader in this tab only.
What is the difference between SHA-256 and SHA-1?
SHA-1 is 160 bits and is obsolete for security; it remains for git objects and old SRI. SHA-256 (and SHA-384/512) are the modern choices. Prefer SHA-256 or SHA-512 for anything new. This page still offers SHA-1 for verification of legacy checksums.
Hex or Base64 hash output?
Hex is what shasum prints. Base64 is common in Content-Security-Policy hashes. Switching encoding reprints the same digest bytes without hashing again.
Why is there no MD5?
Browsers do not expose MD5 through Web Crypto, and MD5 is broken for collision resistance. Use a local CLI if you must match an ancient MD5. SHA-256 is the default here.