Base64 Decoder

Decode Base64 or URL-safe Base64 back to readable text, Arabic included.

How to use

What it checks and how it works

The decoder accepts both alphabets of RFC 4648: the standard one (+ and /) and the URL-safe one (- and _). It ignores whitespace and a data: URI prefix, adds missing = padding, and reports any character outside the alphabet with its position. The bytes are then read as UTF-8 (RFC 3629), so Arabic text comes back correctly. If the bytes are not valid UTF-8, the data is probably an image, a file or another encoding, and the tool shows the start of the data in hex instead of garbled text. It cannot tell you what the data was meant to be, and a decoded value may still be sensitive, so treat it with care.

Why do I get strange characters instead of Arabic?

The text was probably encoded in another character set, not UTF-8. The tool tells you when the bytes are not valid UTF-8 and shows them in hex.

Why is the padding added back?

Base64 text should end with = to fill the last group of four characters. Many systems drop it, and the tool restores it before decoding.

Can I decode a JWT with this?

You can decode each of its dot-separated parts, which are Base64URL text. That shows the contents but does not check the signature.

Sources

Related tools

Privacy

Runs in your browser; nothing is uploaded. The interactive tool needs JavaScript.