Base64 encoder & decoder
Convert readable text to Base64 and back. Unicode text is encoded as UTF-8 before the Base64 step, so accented letters and emojis can round-trip.
Base64 encoder & decoder
Runs on your deviceEncoding does not hide a message
Base64 represents bytes using a limited alphabet. It is commonly used when a text-based channel needs to carry binary-like data. Anyone who has the encoded value can decode it; no secret key is involved. Do not use Base64 as password protection, encryption, or a reason to share information you would otherwise keep private.
UTF-8 comes before Base64
JavaScript strings and raw bytes are different things. This tool first turns input text into UTF-8 bytes, then encodes the bytes. Decoding reverses those steps and reports an error if the result is not valid UTF-8 text. That makes the tool suitable for text examples but not for inspecting arbitrary binary files, compressed content, or image bytes as readable characters.
Standard and URL-safe alphabets
Standard Base64 uses plus and slash characters and may end in equals-sign padding. The URL-safe version substitutes hyphen and underscore and omits trailing padding on encoding. Choose the version expected by your application. Decoding ignores whitespace, accepts omitted padding where possible, and rejects invalid characters. It does not parse tokens, verify signatures, or make claims about the trustworthiness of decoded content.
Worked examples
| Text | Standard Base64 | Decoded text |
|---|---|---|
| Hello | SGVsbG8= | Hello |
| café | Y2Fmw6k= | café |
Good questions.
Is Base64 encrypted?
No. It is reversible encoding without a secret key.
Can I decode an image into readable text?
Usually not. This tool expects the decoded bytes to be valid UTF-8 text.
Why do URL-safe strings look different?
They replace plus and slash with hyphen and underscore and commonly omit padding.
References & further reading
Updated 5 November 2026 · Methods & corrections