Home Tools About

Base64 Encoder / Decoder

Encode text to Base64 and decode it back — Unicode-safe, so emoji, Hindi, and CJK text round-trips without corruption.

Ad space

Encode or decode

Converts live as you type.

Result


          

How Base64 encoding works

Text → UTF-8 bytes → Base64

Your text is first converted to UTF-8 bytes, then re-encoded into the 64-character Base64 alphabet. That two-step path is what keeps emoji and non-Latin scripts intact.

Decoding is strict

The decoder accepts the standard alphabet plus optional padding, and fails gracefully (with a clear message) on garbage instead of emitting corrupted text.

Swap directions

Use the "Use result as input" button to chain operations — encode, then feed the output straight back into the decoder to verify a round trip.

Base64 FAQ

Why use Base64 for text?

Base64 turns binary or tricky text into a safe subset of ASCII (A–Z, a–z, 0–9, +, /, =) that survives email, JSON fields, URLs, and other text-only channels without corruption.

Does it support emoji and other languages?

Yes — text is encoded from UTF-8 bytes, so emoji, Hindi, Arabic, CJK, and any other Unicode content round-trips correctly. Plain atob-based tools corrupt those; this one does not.

Is Base64 encryption?

No. Base64 is encoding, not encryption — anyone can decode it instantly. Never use it to protect secrets.

What is the = padding at the end?

Base64 processes data in 3-byte groups. When the input is not a multiple of 3 bytes, the output is padded with = characters so decoders know how much to discard. Some tools strip it; this tool accepts both.