ConverterBase64 Encode
Encode text at the byte boundary: Unicode text becomes UTF-8 bytes before RFC 4648 Base64 encoding. Choose the alphabet required by the destination.
Encode UTF-8 Text As Base64
Text First Becomes UTF-8 Bytes
Base64 represents bytes, not characters. The same visible text can produce different bytes under a different character encoding, so this profile explicitly uses UTF-8.
Standard Base64 uses + and / with terminal = padding. Base64url uses - and _ here and omits padding. They are related alphabets, not silently interchangeable strings.
Reference Outputs
| Text | Standard Base64 | Boundary note |
|---|---|---|
| Hello | SGVsbG8= | Five ASCII/UTF-8 bytes |
| ✓ | 4pyT | Three UTF-8 bytes |
| 😀 | 8J+YgA== | Four UTF-8 bytes |
What Encoding Does Not Provide
- No confidentiality or encryption.
- No integrity or signature.
- No guarantee the output belongs in every URL, header, log, or protocol field.
Questions About This Tool
No. Anyone with the encoded value can reverse it; Base64 provides no secrecy or authenticity.
UTF-8 uses a variable number of bytes per Unicode code point. Base64 encodes those bytes.
Use the alphabet required by the protocol. Base64url is common in URL-oriented formats such as JWT compact segments.