DevTilt

Base64 Decode

Convert standard Base64 back to UTF-8 text. Whitespace and data-URI prefixes are stripped automatically. Processing stays local.

Result

Paste Base64, then Decode.

How to decode Base64

  1. Paste a Base64 string or a data URI.
  2. Click Decode.
  3. Valid UTF-8 text appears in the output.
  4. If the payload is an image or binary, use Base64 to Image instead.

What is Base64 Decode?

Encoded strings hide their contents until decoded. Paste a Base64 value from a header, log line, or API response to recover the original UTF-8 text. Data URI prefixes are stripped automatically so you can paste either raw Base64 or a full data: string.

Why use DevTilt's Base64 Decode?

  • Strips data URI prefixes before decoding
  • Validates alphabet and padding characters
  • Recovers UTF-8 text from encoded bytes
  • Clear errors for invalid or truncated input

Common use cases

  • Reading a Base64-encoded JWT payload segment
  • Decoding a Basic Auth header from a captured HTTP request
  • Recovering text from a Base64 field in a database export
  • Inspecting encoded values in application logs

FAQ

Standard Base64 length must be a multiple of 4, using = padding when needed. Truncated strings or missing padding fail validation with a specific message.
Yes. A prefix like data:image/png;base64, is stripped before decoding so you can paste either raw Base64 or a full data URI.
If decoded bytes are not valid UTF-8, you will see an error suggesting a binary or image workflow such as Base64 to Image.
The payload may be binary, compressed, or encoded with a legacy charset instead of UTF-8. Image and file Base64 should go through Base64 to Image or a binary-aware workflow, not the text decoder.
This tool expects standard padded Base64. If padding was stripped, add = characters until the string length is a multiple of four, or paste the value from the source system that included padding.