Skip to content
ToolboxHere home

Base64 decode

Decode Base64 online, in your browser: paste it to read it as text, or, if it is an image or a file, to see it and save it with the right extension. Line breaks, missing padding, the URL-safe alphabet and data: URLs are all accepted.

  • Nothing you type leaves your device
  • 100% free
  • No sign-up
  • Instant results
Base64 DecodeBase64 back to text, or to an image or file you can save, with the type read from the bytes.Starting… the tool runs entirely in your browser and needs JavaScript.

How to use Base64 Decode

  1. Paste the Base64 on the left. A data: URL or a string with line breaks works as it is.
  2. Read the text on the right. If the bytes are not text, the page names the file type (PNG, JPEG, PDF, ZIP…) and shows an image when it is one.
  3. Tap Save to download the decoded file with the right extension, or Copy for text.
  4. Swap sends the text back to the encoder if you want to change it and encode again.

Why use Base64 Decode

Text or file, decided by the bytes

UTF-8 text is shown as text; anything else is identified by its signature and offered as a download.

Image preview

A decoded PNG, JPEG, GIF, WebP or SVG is shown on the page before you save it.

Forgiving input

Whitespace and line breaks are ignored, = padding is optional, and both alphabets are read.

Plain errors

A stray character or a length that cannot be Base64 is named, so you know whether the string was cut.

About this tool

Base64 turns bytes into text so they can travel in JSON, email, URLs and CSS; decoding turns them back. The catch is knowing what the bytes are: a decoder that always shows text turns a PNG into garbage. This page reads the first bytes to tell an image, a PDF, a ZIP or a font from text, shows images on the page, and saves files with the right extension.

Text is decoded as UTF-8, so Arabic, Urdu and emoji encoded by any correct tool come back exactly. Whitespace, line breaks and missing padding are tolerated because copied strings often lose them, and the URL-safe alphabet used by JWTs and OAuth is read alongside the standard one. Decoding runs in your browser; nothing is uploaded.

Frequently asked questions

Can I decode Base64 to an image?

Yes. Paste the string (or the whole data:image/… URL); the picture appears on the page and Save downloads it as .png, .jpg, .gif, .webp or .svg as the bytes say.

The result is "binary data": what is it?

The bytes are not UTF-8 text and not a file type the page recognises. The first bytes are shown in hex so you can look up the signature, and Save gives you the raw .bin file.

Why does it say the text is one character short?

Base64 strings can never have a length of 4n + 1 (after removing padding); one character was lost in copying, so the last bytes cannot be recovered.

Does it read URL-safe Base64 and JWT parts?

Yes. - and _ are accepted, with or without = padding. For a JWT, the decoder page reads the whole token at once.

Is anything sent to a server?

No. Decoding and the preview happen in your browser.

Related tools