Base64 decode UTF-8 text

Why decoded text looks broken

Base64 represents bytes, not a guarantee that those bytes are readable text. If the original bytes were UTF-8 text, decoding should restore readable characters. If the bytes were compressed, encrypted, binary, or created with another character encoding, the decoded output may look broken.

Example

5L2g5aW9IDEwMjRiYXNl

你好 1024base

How to decode it

1. Paste the Base64 string into the Base64 Encode / Decode tool.
2. Choose Decode and run the conversion.
3. Check whether the output is readable UTF-8 text.
4. If the output looks broken, confirm whether the original value was compressed, encrypted, binary, or encoded with a different character set.

Base64 and Unicode text

UTF-8 can represent English, Chinese, emoji, and many other characters. When text is first converted to UTF-8 bytes and then encoded as Base64, decoding those bytes as UTF-8 restores the original text.

When non-English text appears as replacement symbols or random characters, the problem is often not Base64 itself. The bytes may have been decoded with the wrong character encoding, or they may not be text at all.

When the result is not text

Many Base64 strings are used to carry binary data, such as images, compressed payloads, encrypted tokens, or signed values. Those strings can decode successfully while still producing output that is not useful in a text box.

If a value came from an API token, file upload, cookie, or authorization header, decode only small test values and avoid pasting production secrets into online tools.

Common mistakes

• Assuming every Base64 value is plain text
• Trying to decode encrypted or compressed bytes as UTF-8
• Leaving labels, quotes, spaces, or line prefixes in the input
• Confusing standard Base64 with URL-safe Base64

Related problems