Base64 encode & decode
Convert text to Base64 and back, with full support for accents and emoji.
Encode any text to Base64 or decode strings from APIs, tokens and e-mail attachments. Unlike naive converters, we treat text as UTF-8 — accents and emoji survive the round trip. Everything runs in the browser, so pasting internal data is safe.
What Base64 is for
Base64 is a way of representing binary data (files, images) or text using only text-safe characters. It is used to embed an image inside HTML or CSS, send email attachments, put data in a token, or move information through channels that only accept text. The encoder converts text and files to Base64, and the decoder does the reverse.
Base64 is not encryption
An important point: Base64 protects nothing. It is just a reversible representation — anyone decodes it in seconds. Do not use it to "hide" passwords or sensitive data thinking they are safe. For real security, use encryption or hash functions, like those in the hash generator.
UTF-8 support, in the browser
The tool handles accents and emojis correctly (UTF-8), avoiding the broken character that appears in poorly built converters. Everything happens locally — nothing is uploaded to servers, so you can encode sensitive data with peace of mind.
Frequently asked questions
Is Base64 encryption?
No — it is just a text representation of bytes (letters, digits, + and /). Anyone can decode it. To protect data, use real encryption; Base64 exists to transport binary data through text-only channels.
Why do other sites corrupt accents and emoji?
The browser’s native btoa() only understands bytes 0–255 and fails on multi-byte characters. We convert text to UTF-8 before encoding and back when decoding — "ação" and "🚀" arrive intact.
Where is Base64 used in practice?
In JWT tokens, images embedded in CSS/HTML (data URIs), e-mail attachments (MIME), API keys and webhook payloads. If you saw a long string ending in "=", it is probably Base64.