Base64 Encode & Decode
Encode text into Base64 or decode it back. Handles emoji and accented characters correctly.
Dieser Inhalt ist auf Englisch.
Durchgerechnete Beispiele
Encoding a short word
hello
aGVsbG8=
Base64 is a reversible encoding, not encryption, so anyone can decode the output.
Encoding accented text and emoji
Café ☕
Q2Fmw6kg4piV
The text is converted to UTF-8 bytes before encoding, which is why the accented letter and the emoji survive a round trip.
Über Base64 Encode & Decode
Base64 is a way of representing binary or text data using 64 printable ASCII characters. Developers use it to embed images in HTML and CSS, pass data through JSON fields, and build HTTP basic authentication headers. Base64 is an encoding, not encryption, so anyone can reverse it, and it should never be relied on to hide sensitive information.
This converter encodes plain text into Base64 and decodes Base64 strings back into readable text. It also offers the URL-friendly variant defined in RFC 4648, which replaces plus and slash characters with hyphen and underscore so the output fits in web addresses. Emoji and accented characters are handled correctly, because the text is encoded as UTF-8 before conversion.
So verwenden Sie Base64 Encode & Decode
- Paste your text into the input field, or paste a Base64 string to decode it.
- Select encode or decode, depending on the direction you need.
- Tick the URL-friendly option if the output will appear in a web address or query string.
- Copy the result and check that it matches what your system expects.
Typische Einsatzzwecke
- Inspecting a Base64 payload found in an API response or a token segment.
- Preparing a Basic authentication header for a test request.
- Embedding a small icon or snippet as a data URI in a stylesheet.
- Checking how an email or webhook body has been encoded.
Häufige Fragen
Is Base64 encryption?
No. Base64 is an encoding scheme that changes how data is represented, so that it can travel through systems that handle text only. It requires no key, and anyone can decode it with the same method. If you need to protect information, use a proper encryption method with a key, rather than relying on Base64 to hide content.
What is the difference between Base64 and Base64URL?
Standard Base64 uses plus and slash characters, and it often ends with equals signs used as padding. Base64URL, defined in RFC 4648, replaces plus with hyphen and slash with underscore, which avoids clashes with characters that have special meaning in URLs. Padding is often omitted in the URL variant. Decoders usually expect the matching form, so check which one your system uses.
Does Base64 make a file or text longer?
Yes. Base64 represents every three bytes of input as four characters, so the encoded output is roughly 33 percent larger than the original. Line breaks or padding can add a little more. This overhead matters when you embed large images in HTML or send payloads through size-limited channels, so consider linking files directly for big assets.
Why does decoding Base64 give garbled characters?
A frequent cause is that the original text was not UTF-8, so decoding it as UTF-8 produces unreadable symbols. Another cause is a string that was altered in transit, or one with missing padding or extra whitespace. Check the source encoding, remove stray spaces or line breaks, and confirm whether the URL-friendly form was used.
Can Base64 handle emoji and accented letters?
Yes, provided the text is encoded as UTF-8 first. Accented letters such as é and emoji occupy two or more bytes each in UTF-8, and Base64 then represents those bytes faithfully. When decoding, the output must be read as UTF-8 to display the original characters correctly. Mixing encodings is the usual reason accents turn into strange symbols.