Base64 Decode Online — Instant, Free, Browser-Based

Need to decode a Base64 string online? Paste it into the box above and get
the decoded output in milliseconds — no installation, no account, no data sent to any server.
The Base64 decoder at Urbi Tools runs entirely in
your browser, so your data stays private from start to finish.

How to Use This Base64 Decoder

1. Paste your Base64-encoded string into the input box above.
2. Click Decode — or the result appears automatically as you type.
3. The decoded plain text appears in the output panel instantly.
4. Click Copy to copy the result to your clipboard.

No file uploads, no sign-up forms, no waiting. If you see garbled output, check that your
input is valid Base64 — it should only contain letters, numbers, +, /,
and optional = padding at the end.

How Base64 Decoding Works

Base64 is a binary-to-text encoding scheme defined in
RFC 4648.
It represents binary data using a 64-character alphabet — uppercase A–Z, lowercase a–z,
digits 0–9, plus + and /.

Here is what happens in reverse when you decode:

1. Each Base64 character maps to a 6-bit value using the Base64 alphabet table.
2. Four Base64 characters produce 3 bytes: the four 6-bit values are
   concatenated into 24 bits, then split into three 8-bit bytes.
3. Padding is stripped: = characters at the end indicate the
   original data was not a multiple of 3 bytes, so the decoder discards the extra bits.
4. Bytes are interpreted: if the original data was UTF-8 text, the bytes
   become a readable string. If it was binary (an image, a PDF), you get raw bytes.

For example, the Base64 string SGVsbG8gV29ybGQ= decodes to
Hello World. Try it in the decoder above to verify.

URL-Safe Base64

Standard Base64 uses + and /, which have special meaning in URLs.
URL-safe Base64 (also called Base64url) replaces + with - and
/ with _. You will see this variant in JWT tokens and URL parameters.
Our decoder handles both variants automatically — no manual substitution needed.

MIME Base64 and Line Breaks

Email attachments encoded with MIME Base64 include line breaks every 76 characters
(per RFC 2045). Most decoders — including this one — strip whitespace before decoding,
so you can paste MIME-encoded content directly without cleaning it up first.

How Base64 Decoding Is Calculated

The algorithm works character by character through a lookup table:

• A–Z → values 0–25
• a–z → values 26–51
• 0–9 → values 52–61
• + → 62, / → 63

For each group of 4 encoded characters, the decoder:

1. Looks up each character’s 6-bit value.
2. Concatenates the four 6-bit values into one 24-bit integer.
3. Splits the 24 bits into three bytes: bits 23–16, 15–8, and 7–0.
4. Outputs those three bytes as the decoded data.

This is exactly what happens in your browser when you hit the Decode button — pure
JavaScript, no server round-trip.

Why Base64 Decoding Matters

Base64 is everywhere in software development. You will encounter it in:

• JWT tokens — JSON Web Tokens have three Base64url-encoded segments
  separated by dots. Decoding the header and payload reveals the token’s claims and algorithm.
• Email attachments — MIME encodes binary attachments as Base64 so they
  travel safely through text-only email infrastructure.
• Data URIs — Images embedded in HTML or CSS use the format
  data:image/png;base64,…. Decoding the Base64 portion gives you the raw image bytes.
• API responses — Some APIs return binary data (PDFs, audio, images) as
  Base64-encoded strings inside JSON payloads.
• HTTP Basic Auth — The Authorization: Basic … header contains
  a Base64-encoded username:password pair, useful to inspect while debugging.
• DevOps configs — Kubernetes secrets, Docker registry credentials, and
  CI/CD pipelines frequently store binary or sensitive values in Base64.

Being able to decode Base64 instantly — without writing code — saves time every day for
developers, security researchers, and DevOps engineers. If you also work with URL-encoded
strings, check out the URL decoder at Urbi Tools
for the same friction-free experience with percent-encoded characters.

Tips for Getting the Best Results

• Whitespace is handled automatically — copy-pasted Base64 from logs or
  emails sometimes includes spaces or newlines. The decoder strips them, but if you still see
  errors try removing extra characters manually.
• Watch for URL-safe characters — if your string contains -
  or _ instead of + or /, it is URL-safe Base64. The
  decoder handles both, but knowing the variant helps you understand the source.
• Binary output looks like garbage — decoding a Base64-encoded image or
  PDF produces raw bytes that display as unreadable characters in a text box. That is normal
  and expected behaviour.
• Decode JWT segments one at a time — split a JWT at the dots and decode
  each segment separately. The third segment (signature) is binary and will not produce
  readable text.
• Padding errors — if you get an “invalid Base64” error, try appending
  one or two = characters to the end. Some systems strip padding when storing
  Base64 strings.

Frequently Asked Questions

Is Base64 decoding the same as decryption?

No. Base64 is encoding, not encryption. It is a fully reversible transformation with no
secret key — anyone can decode it. Never use Base64 to protect sensitive data. If you need
actual confidentiality, use AES or another purpose-built encryption standard. Base64 exists
only to make binary data safe to transmit over text-based systems.

Why does my decoded output look like garbage?

If the original data was binary — an image, PDF, or audio file — the decoded bytes are not
valid UTF-8 text and will display as unreadable characters. This is expected. If you were
expecting readable text and got garbage instead, double-check that you copied the full Base64
string without truncating it.

How do I decode Base64 in JavaScript?

Use the built-in atob() function:

const decoded = atob('SGVsbG8gV29ybGQ=');
console.log(decoded); // "Hello World"

For URL-safe Base64, replace - with + and _ with
/ before calling atob(). In Node.js, prefer
Buffer.from(str, 'base64').toString('utf8').

How do I decode Base64 in Python?

Python’s standard library handles it natively:

import base64
decoded = base64.b64decode('SGVsbG8gV29ybGQ=')
print(decoded.decode('utf-8'))  # "Hello World"

For URL-safe Base64 (JWTs, etc.), use base64.urlsafe_b64decode() instead.

Is there a size limit for the online decoder?

There is no hard limit. The decoder runs entirely in your browser with JavaScript, so
performance depends on your device. In practice, Base64 strings up to several megabytes
decode instantly. Very large payloads (10 MB+) may take a second or two on older hardware.

What is the difference between standard Base64 and Base64url?

Standard Base64 uses the characters + and /, which have special
meaning in URLs and filenames. Base64url (URL-safe Base64) replaces them with -
and _, making the output safe to use directly in URLs, query parameters, and
filenames without percent-encoding. JWT tokens always use Base64url.

Start Decoding Now

The Base64 decode online tool at Urbi Tools gives you instant, private,
browser-based decoding with no strings attached. Whether you are inspecting a JWT, debugging
an API response, or unpacking a Kubernetes secret, it handles any valid Base64 string in
milliseconds — and your data never leaves your device.

Use the Base64 decoder now →