Base64 to Text Converter
Decode any Base64 string back into readable text - paste it in, click convert, and copy the result.
What is the Base64 to Text Converter?
This tool takes a Base64 string and turns it back into the text it came from. Base64 (RFC 4648) encodes bytes as 64 printable ASCII characters; decoding walks that process backwards - every four Base64 characters become three original bytes - and the result is handed back to you as UTF-8 text.
It is the other half of the Text to Base64 encoder. Reach for it when you have received an encoded value and need to read what is actually inside: a token fragment, a config blob, the contents of a data URI, or a field some API returned in Base64.
How to use the Base64 to Text converter
- 1. Paste your Base64 string into the Base64 field on the left.
- 2. Click Convert Now to decode it.
- 3. The decoded text appears in the field on the right - select and copy it.
Features
- Decodes the standard RFC 4648 Base64 alphabet.
- Returns UTF-8 text, so accented and multibyte characters come back intact.
- Works on short tokens or large encoded blocks.
- Pairs with our Text to Base64 tool for the encode direction.
- Free to use, no account required.
Common uses
Reading the payload hidden in an encoded config value, inspecting what a data URI really holds, checking a Base64 field returned by an API, or recovering text that someone sent you encoded. If you only need to peek at the claims inside a JSON Web Token, the JWT Decoder splits and decodes all three parts for you.
FAQ
What does Base64 decoding do?
It reverses RFC 4648 encoding. The decoder reads the Base64 alphabet - A to Z, a to z, 0 to 9, + and / - rebuilds the original bytes, and returns them as UTF-8 text.
Why does my Base64 fail to decode?
The input must be valid Base64: a length that is a multiple of 4 with = padding, using only alphabet characters. Stray spaces, line breaks or URL-safe - and _ characters can cause errors.
Is decoding the same as decryption?
No. Base64 is only an encoding, so decoding does not break any protection. The data was never encrypted, just re-expressed as text, and anyone can decode it.
Can I decode URL-safe Base64?
Standard Base64 uses + and /. URL-safe variants swap those for - and _, so convert them back to + and / before decoding the string here.