Quick answer
Key points
- Encoding is reversible by a public format rule and is not a security boundary.
- Encryption uses a key so unauthorized readers cannot recover plaintext.
- Cryptographic hashing is designed to be one-way, not decoded back to the source.
Three techniques, three different goals
Encoding makes data compatible with a representation or channel. Everyone who knows the format can decode it. UTF-8, Base64, and the app’s Binary display are examples.
Encryption protects confidentiality. A modern encryption system uses a key; recovering plaintext without the authorized key should be computationally infeasible. Hash functions instead map input to a fixed-style digest and are designed so the original input is not recovered by “decoding” the digest.
- Encoding: compatibility or representation; no secret key; reversible by the format.
- Encryption: confidentiality; uses a key; authorized parties decrypt.
- Hashing: fingerprinting or integrity building block; no normal reverse operation.
How Encode Keyboard classifies its 12 codecs
Base64, Base64URL, Base32, and Base16 follow RFC 4648; URL Percent follows an RFC 3986 canonical profile; Morse starts from ITU-R M.1677-1. Binary UTF-8 is an app profile built on standard UTF-8. These labels separate a published standard from an implementation profile.
ROT13 and Personal Code are conventions. Emoji, Kaomoji, and Leetspeak are expressive transformations whose reverse direction may be interpretive or unavailable. None of these categories implies encryption.
The same message under different transformations
For “Hello”, Base64 produces SGVsbG8= and ROT13 produces Uryyb. Both can be reversed instantly with public rules. Binary exposes the UTF-8 bytes as bits. Morse maps supported characters to public signal patterns.
Real encryption output also looks unfamiliar, but unfamiliar appearance is not the test. The important properties are a defined security goal, sound algorithms, key management, and correct implementation.
Choose the technique by your actual goal
Use Encode Keyboard for expression, learning, interoperability experiments, and reversible transformations of non-sensitive text. Use the exact/normalized/interpretive labels to understand what a round trip can preserve.
If your goal is to protect a password, financial detail, identity document, recovery phrase, or confidential message, do not put it through Base64, Binary, Morse, ROT13, or Personal Code and call it protected. Use established security products and protocols built for that risk.
Frequently asked questions
Is Base64 encryption?
No. It is a public reversible encoding with no secret key.
Is ROT13 secure?
No. Applying ROT13 a second time restores the original, and anyone can do it.
Can a hash be decoded?
A cryptographic hash is designed without a reverse operation. Attackers may still guess inputs and compare hashes, which is why secure password storage needs specialized salted password-hashing schemes.
Is Personal Code encryption?
No. It is a shared phrase mapping for expression and coordination, not a cryptographic security system.
Primary sources
This guide prioritizes documentation from the organizations responsible for the standard or platform.