Base64 to Text

Paste any Base64 string and decode it back to readable text in one click. Useful for inspecting API responses, reading JWT payloads before the signature part, checking encoded config values, and debugging auth headers.

Last updated: May 28, 2026

Base64 input

URL-safe(converts - _ back to + /)

Decoded text

Tip: Enable URL-safe mode if your Base64 string uses - and _ instead of + and /. Missing = padding at the end is a common cause of decode errors.

Client-Side Processing

Input Data Stays on Device

Instant Local Execution

Find this tool useful? Support the project to keep it free!

Buy me a coffee

What is Base64 to Text?

Base64 to text decoding is the reverse of encoding: it takes the 64-character ASCII representation and recovers the original bytes, then converts them back to readable text. You will encounter Base64 in HTTP Basic Auth headers, JWT tokens, email MIME attachments, cookie values, and many API responses.

This tool focuses on the decode-only direction so the interface stays clean and intent-specific. It auto-detects standard Base64 and URL-safe Base64 (-_ instead of +/) and gives a clear error when the input is not valid Base64.

How to Use Base64 to Text

Paste the Base64 string into the input field

Click "Decode to Text" to recover the original plain text

Enable URL-safe mode if your string uses - and _ instead of + and /

Read the error message if decoding fails — it will explain the likely cause

Use the copy button to grab the decoded text for your workflow

Common Use Cases

Developers inspecting Base64-encoded API responses or webhook payloads to read the original content.
Engineers debugging HTTP Basic Auth headers by decoding the credential block.
Security analysts decoding Base64 fragments found in logs, payloads, or config files during investigation.
Frontend developers decoding data URIs or inline assets back to their readable source.
QA testers verifying that an encoder/decoder round-trip preserves the original string exactly.

Example Input and Output

Decoding a Basic Auth header value is one of the most common debugging tasks where Base64 to text comes up.

Base64 string

YXBpLXVzZXI6czNjcjN0LWtleS0yMDI2

Decoded text

api-user:s3cr3t-key-2026

Decoded ≠ decrypted

Decoding Base64 just recovers the original bytes. If the original content was encrypted, you will still see ciphertext after decoding. Base64 and encryption are separate concerns.

Padding issues

Some systems strip the trailing = padding characters. If you see an error about invalid length, try appending one or two = characters to the end of your string.

Frequently Asked Questions

What does "invalid Base64" mean?

It usually means the string has invalid characters, is missing padding (= signs at the end), or was corrupted during copy-paste. Check for spaces, line breaks, or stray characters that snuck in.

What is URL-safe Base64 and how does it differ?

URL-safe Base64 replaces + with - and / with _ so the string can appear in URLs and filenames without percent-encoding. Enable URL-safe mode if your string contains those characters.

Can I decode Base64 that wraps across multiple lines?

Yes. The decoder strips whitespace before processing, so you can paste multi-line PEM-style Base64 and it will be handled correctly.

Why does the decoded output look like gibberish?

The string might be double-encoded (Base64 inside Base64), or the original data was binary (an image or file) rather than text. Try running the decoded output through the decoder again.

Is my Base64 data sent to a server?

No. Decoding happens locally in your browser. Your input never leaves your device, which is important when the encoded value contains credentials, tokens, or private data.