Base64 Decoder
Decode Base64 encoded text.
How to Use Base64 Decoder
Paste the Base64 string into the input box - an Auth header, a data URI payload or a token segment.
Click the "Process" button to decode it and display the original text in the output panel.
If the result still looks encoded, run it through again, since the data may have been encoded twice.
Copy the decoded text with one click, or download it as a .txt file to examine it in full offline.
Features
Frequently Asked Questions
Related Tools
Word Counter
Count the number of words in your text instantly.
Character Counter
Count characters with and without spaces.
Sentence Counter
Count the number of sentences in your text.
Paragraph Counter
Count paragraphs in your text content.
Text Case Converter
Convert text between different cases - upper, lower, title, sentence.
Uppercase Converter
Convert text to UPPERCASE letters.
About Base64 Decoder
Every now and then a string arrives that you simply cannot read: a blob in a CSS data URI, the value in an Authorization header, or the middle section of a JWT token. Those are all Base64, and decoding them turns an unreadable wall of characters back into the text or structure that was hidden inside it.
Authentication is the most common reason people end up here. An HTTP Basic Authorization header looks like a single unbroken run of letters and equals signs, and if a request keeps returning 401 Unauthorized, decoding it shows you the exact username:password pair being sent - which immediately reveals the trailing space, the wrong colon, the stale password or the basic-auth prefix that was never stripped out. A JSON Web Token is a related case: the header and payload are Base64url encoded, and decoding the payload shows you the claims and their expiry timestamps without any verification.
Data URIs are the other common one. When an image or font is embedded in a file you receive, the payload after the comma is Base64 and decoding it reveals the original data, or at least its opening characters. Data can also be encoded more than once, so if the first result still looks encoded, decode it again. Invalid characters are reported rather than silently dropped, which makes it a useful way to find a corrupted or truncated payload.
When to Use This Tool
- Inspecting an HTTP Basic Authorization header that keeps returning 401
- Reading the claims and expiry inside a JSON Web Token
- Decoding the payload of a data URI embedded in CSS or HTML
- Reversing a Base64 string you generated and checking it round-trips correctly
- Finding out why a payload is malformed by spotting the invalid character