Interactive · Web Crypto API · Nothing is uploaded

Hash & Encoding Toolkit

The conversions you reach for every day — MD5 and SHA hashes, Base64, URL encoding and hex — generated live as you type, and a hash identifier that names any digest.

Runs entirely in your browser, so you can hash an API key or a password without pasting it into a website you do not control.

MD5
SHA-1
SHA-256
SHA-384
SHA-512

Type in either box — the other updates. Unicode-safe.

Guesses the algorithm from a digest's length and format — MD5, SHA family, bcrypt, NTLM, Unix crypt and more.

Hashing vs. encoding — they are not the same

A hash (MD5, SHA-256) is one-way: you can compute it from data, but you cannot get the data back. It is for checksums, integrity and password storage. Encoding (Base64, URL, hex) is two-way: it just represents the same bytes in a transport-safe form, so it always decodes. Encoding is not encryption and provides no secrecy.

Which hash should I use?

Use SHA-256 for integrity and general-purpose hashing. Avoid MD5 and SHA-1 for anything security-sensitive — they are broken against collisions — but they are still everywhere in legacy checksums, which is why they are here. For passwords, use a slow, salted hash like bcrypt or Argon2, never a raw hash.

Why do this in the browser?

Because the values you most want to hash or decode — a token, a secret, a config string — are exactly the ones you should not paste into a random online converter that posts them to a server. Everything here runs locally through the Web Crypto API and plain JavaScript, so nothing you type leaves the page.

Can you reverse a hash here?

No. Hashes cannot be decrypted — that is the point of them. The Identify tab tells you which algorithm produced a digest; cracking one means guessing inputs until a hash matches, which is a different job entirely.