Hashing, encoding, and encryption explained
Learn what hashing, encoding, and encryption mean, what each one does, and when each one is useful.
Hashing, encoding, and encryption may sound like different names for the same thing, but they solve different problems. The easiest way to tell them apart is to ask whether you need to change a format, compare information, or lock it.
Encoding and hashing do different jobs
Base64, URL encoding, ASCII numbers, and uuencode change how text is written so another program can read it. Anyone with the right decoder can change it back. Do not use encoding to hide a password, message, or other private information.
A hash turns text into a fixed-length fingerprint, sometimes called a digest. The same text produces the same hash, while even a small change usually produces a very different one. Every character matters. These tools read pasted text as UTF-8 and do not upload files, so a result from a file-checking program may differ if the file contains different line breaks or other unseen information.
MD5 and SHA-1 are old and should not be used for modern security work. A plain SHA hash is also not a safe way to store passwords. Websites and apps should use a password-storage system made for that job.
Encryption locks information with a key
Encryption protects information so someone with the correct key can unlock it later. Hashing does not work that way, and encoding does not provide that protection at all. The tools on this site do not encrypt, decrypt, or crack information.
Uuencode is an older format that some systems still use. Our combined tool returns the encoded text without a filename or the usual beginning and ending wrapper, so check what the receiving program expects.