Base64 Encoder
Turn text into Base64 on this page. The encoder converts the text to UTF-8 bytes first, then uses the browser's Base64 function.
About this tool
The page encodes with TextEncoder and btoa. btoa alone only accepts binary strings, so the UTF-8 bytes are turned into that form in chunks before encoding. The alphabet is the standard Base64 alphabet with +, /, and = padding. This is not URL-safe Base64: + and / are not replaced.
A successful result is Base64 text, not the original prose. Case conversion and line sorting do not accept it. The Base64 Decoder is the inverse, so the next-step list leaves it out on purpose. Paste the result into the decoder when you want to check the round trip. That paste still stays in the browser.
The chain can still carry plain text into this encoder from a text tool. A refresh can discard that handoff. Nothing is uploaded.
How to use it
- Paste the text you want to encode. The tool reads it as UTF-8, so characters outside ASCII are included.
- Encode it. The result is standard Base64 with padding.
- Copy the result or download it. The decoder is listed under Reverse, because it undoes this step rather than continuing the edit.
Limitations
- The encoder uses UTF-8 bytes. It does not wrap the result or emit a data URL.
UTF-8 bytes written in the standard alphabet
Text is encoded as UTF-8, then as Base64
The paste is UTF-8 bytes, then the standard alphabet. A JavaScript string is turned into bytes with a UTF-8 encoder, and those bytes are turned into Base64 with the usual A–Z, a–z, 0–9, plus, and slash alphabet, with equals signs for padding. The result is one line. The encoder does not wrap at 76 characters the way some mail formats do. An empty string stays empty. The work is reversible by the decoder when the bytes are valid UTF-8, which they are, because this page always starts from text.
This is not encryption. The alphabet is public. Anyone who has the Base64 text can recover the UTF-8 bytes and the string without a key. Do not put a secret here and treat the result as hidden. Do not call the output a password hash. A hash page is a different tool and is one-way. Base64 exists so binary-safe channels can carry bytes. On this page the bytes are the UTF-8 form of the text you typed, not a file’s original byte layout if that file was not UTF-8 text.
What does not belong in the box
Pasting characters is not the same as uploading raw bytes. A string has already been decoded as text before the UTF-8 encoder runs. If you needed a particular byte that is not valid Unicode, this page cannot hold it. The decoder later insists on UTF-8. The security tools that hash or encode for other alphabets are separate. URL-safe Base64, which uses minus and underscore, is not what this encoder writes. The decoder rejects those characters. Stay with the standard alphabet if you plan to decode on the matching page.
Padding and whitespace
The encoder emits padding when the byte length requires it. You do not add the equals signs yourself. Spaces are not inserted. If a downstream system wraps the line, the decoder on this site strips whitespace before it checks the alphabet, so a wrapped copy can still decode. Use this page to produce a standard Base64 spelling of UTF-8 text. Use the decoder to read that spelling back.
Privacy
Your text is processed in your browser and is not uploaded to UtilChain. The text and the Base64 are not included in analytics.

