Encode text to Base64 or decode Base64 back to text. Base64 is a binary-to-text encoding scheme defined in RFC 4648 that represents arbitrary byte sequences as printable ASCII characters using a 64-character alphabet. It is universally used for safely transmitting binary data in email, APIs, and configuration systems.
Instantly encode or decode Base64 with full UTF-8 support — handles emoji, CJK characters, and special symbols. 100% free, no registration, and complete privacy — everything runs locally in your browser, so your data never touches a server.
Switch between encode and decode modes to convert text to Base64 or reverse the process with a single click.
Handles emoji, CJK characters, and all Unicode safely. Properly escapes special characters before encoding.
Live character count for both input and output helps you monitor payload size.
Copy the output instantly with a single button click for seamless integration into your code.
Encoding & Decoding Example
Plain Text
Hello, World!Output:
SGVsbG8sIFdvcmxkIQ==Base64 (RFC 4648) is a binary-to-text encoding that converts arbitrary bytes into a 64-character printable ASCII alphabet (A–Z, a–z, 0–9, +, /). It is used to safely embed binary data in text protocols (email, JSON, XML) and to encode credentials for HTTP authentication. The trade-off is a ~33% size increase, but the data is safe for transmission across any system.
No. Base64 is encoding, not encryption. Anyone can decode it as easily as encoding it. If you need security, use encryption (AES, RSA) first, then Base64-encode the ciphertext. Base64 is for *safe* representation of binary data in text contexts, not for hiding secrets.
Concatenate the username and password with a colon (username:password), then Base64-encode the result. For example, alice:secret123 encodes to YWxpY2U6c2VjcmV0MTIz. Include this in the Authorization header as Authorization: Basic YWxpY2U6c2VjcmV0MTIz.
Yes! JWTs (JSON Web Tokens) use Base64url encoding for the header and payload. Copy the middle segment (between the first two dots) and paste it here to decode the claims. Note that the signature is cryptographic and cannot be decoded — only verified with the secret key.
Base64url (RFC 4648 section 5) replaces + with - and / with _ to be URL-safe without percent-encoding. This tool encodes/decodes standard Base64 (with + and /). If you are working with JWT or URL-safe data, strip or convert those characters accordingly.
Yes. This tool uses UTF-8 encoding, so emoji, CJK characters, and accented letters are first converted to UTF-8 bytes, then Base64-encoded. When decoding, the process reverses: Base64 bytes are decoded and interpreted as UTF-8, restoring the original text with all special characters intact.
Encode and decode Base64 online, free. Base64 encoding (RFC 4648) represents arbitrary bytes using a 64-character set of letters, digits, + and /, so binary or text data can travel safely through systems that only handle text — like JSON, data URLs, or email. This tool encodes text to Base64 and decodes it back, entirely in your browser, with full UTF-8 support.
Encoding and decoding run locally with correct UTF-8 handling, so multi-byte characters and emoji round-trip cleanly and nothing is uploaded. 100% free, no registration, and complete privacy — everything runs locally in your browser, so your data never touches a server.
Convert text to Base64 and decode Base64 back to text with one click in either direction.
Multi-byte characters and emoji are encoded as their UTF-8 bytes, so they survive the round-trip intact.
Runs locally as you type — no upload, no wait.
Your data is encoded locally and never sent anywhere — safe for tokens and secrets.
Base64 encodes binary or text data using only printable ASCII characters, so it can travel safely through text-only channels — data URLs, JSON/XML fields, Basic Auth headers, and email (MIME). It is an encoding, not encryption.
No. Base64 is fully reversible with no key — anyone can decode it. It hides nothing; use it for transport/encoding, never to protect secrets.
Yes. Text is encoded as UTF-8 before Base64, so multi-byte characters and emoji encode and decode correctly without corruption.
Base64 represents every 3 bytes as 4 characters, so encoded output is roughly 33% larger than the input. That's the normal size trade-off for text-safe encoding.
No. Encoding and decoding run entirely in your browser — nothing you paste is sent to a server.
We use cookies for analytics and personalized ads to help keep these tools free. Until you accept, ads stay non-personalized and analytics cookies are off. See our Privacy Policy.