Developer Utilities

Base64 Decoder

All tools

Turn a Base64 blob from a config file, header or API response back into readable text.

How it works

Four simple steps

1

Paste the Base64

Wrapped lines and stray spaces are fine; whitespace is stripped first.

2

Format is checked

Characters outside the standard alphabet or an impossible length stop with a clear message.

3

Read as UTF-8

Valid bytes are decoded to text, including accents and emoji.

4

Copy or save

Copy the decoded text or download it as decoded.txt.

Base64 Decoder

About Base64 Decoder

A Kubernetes Secret stores DATABASE_URL as a Base64 string and the app still cannot connect. Decoding it shows the exact value the pod receives, including a stray trailing newline or the wrong host name. Base64 Decoder does that in one paste.

Decoding starts as soon as you paste. Spaces and line breaks are stripped first, so wrapped output from PEM files or email bodies works without cleanup. The decoder accepts the standard alphabet (A to Z, a to z, 0 to 9, + and /) with up to two = padding characters, and it reports an invalid character or impossible length instead of returning garbage. The bytes are then read as UTF-8, so accented text and emoji come back intact.

If the input contains - or _, it is URL-safe Base64 (common in JWTs and web tokens), and this decoder will reject it. Convert it first with base64url to standard conversion, or for tokens use the JWT decoder, which handles the header and payload for you. When the characters are valid but decoding still fails with a malformed URI error, the bytes are not UTF-8 text at all; they are likely compressed, encrypted or an image. View the raw bytes as hex to tell which.

The string is decoded with the browser's atob function inside this page, so a secret copied out of a config file never reaches a third-party decoder.

Keyboard shortcut

Ctrl Enter - Run tool

Use cases

Config archaeology

Reveal what a Base64 setting actually stores.

API response unwrap

Decode fields that arrive Base64-encoded in JSON.

Incident triage

Inspect encoded tokens locally during an outage.

Instructions

How to use this tool

FAQ

Frequently asked questions

See all FAQs

Answers for this tool. For site-wide help, open the FAQ hub.

The Base64 itself was fine, but the decoded bytes are not valid UTF-8. That happens with images, gzip data, encrypted blobs and some legacy encodings such as Windows-1252. Use the hex or binary view to inspect the bytes instead.

Usually not. A string whose length leaves a remainder of 2 or 3 after dividing by 4 decodes fine without the = signs. A remainder of 1 is impossible in Base64, so that length is reported as invalid.

It decodes to text only, so an image would fail the UTF-8 step. The Base64 to Image tool in Image Tools displays and downloads the picture instead.

View more FAQs

Related tools

View all

Cron Calendar

Explain cron expressions and preview the next run times in any timezone.

Open

CSV to SQL

Infer column types and generate CREATE TABLE + INSERT statements from CSV.

Open

SQL Query Builder

Build SELECT queries visually and reverse-parse SQL into a structure tree.

Open

Log Pattern Miner

Cluster log lines into templates, surface anomalies, and mask PII locally.

Open

Explore 321 free tools

Everything you need as a developer, marketer or creator - in one beautiful place.

Browse all tools