TextArray
100% local

Base64 encode and decode

Convert text to Base64 and back, with full UTF-8 and URL-safe support.

Input
Output
Related tools
URL encode and decodeEncoding & conversionHTML entities encode and decodeEncoding & conversionUUID generatorRandom generatorsJSON formatter & validatorText formatting
Base64 encode and decode
Base64 turns arbitrary text into a compact set of 64 safe characters, which makes it the standard way to move data through channels that only accept plain ASCII. Paste text to get its Base64 form, or paste Base64 to read the original text back. Switch between the two directions with the mode selector.
Encoding is fully UTF-8 aware, so Slovak diacritics, Greek letters, CJK characters and emoji all survive a round trip intact. The "URL-safe alphabet" option swaps the standard + and / characters for - and _ and drops the trailing padding, producing a string you can drop straight into a query parameter, a path segment or a JWT without further escaping. The "Wrap at 76 characters" option breaks long output into fixed-width lines, the format expected by MIME email headers and PEM-style blocks.
Decoding is deliberately forgiving. Whitespace and line breaks are stripped before decoding, both the standard and URL-safe alphabets are accepted, and missing padding is tolerated — so a value copied out of a log file or a config usually just works. If the input genuinely cannot be Base64, you get a plain explanation rather than a silent wrong answer.
Everything runs in your browser. Nothing is uploaded, which matters here more than for most tools: Base64 strings routinely carry API tokens, session data, basic-auth credentials and encoded payloads. Decode them here and the plaintext stays on your machine. The tally under the output shows sizes on both sides, so you can see the roughly 33% growth encoding adds.
FAQ
Does Base64 encrypt my text?
No. Base64 is an encoding, not encryption — anyone can decode it. Use it to transport data safely, never to protect secrets.
When should I use the URL-safe alphabet?
When the result goes into a URL, a filename or a JWT. It replaces + and / with - and _ and removes padding, so nothing needs escaping. Decoding accepts either alphabet automatically.
Do emoji and diacritics work?
Yes. Text is encoded as UTF-8 bytes, so "šťastie" and 🫐 round-trip exactly.
Why does my Base64 fail to decode?
Usually characters are missing from the end after a truncated copy, or the string contains characters outside the Base64 alphabet. Padding and whitespace are handled for you.
Is my text uploaded anywhere?
No. The tool runs entirely in your browser and your text never leaves your device — including any tokens you decode.