IT Market
Tools/Code/Data/Base64 to File Decoder Online — Download
Base64 → Файл

Декодирование Base64 и скачивание файла

Tool guide

Base64 to File Decoder Online — Download

This page unpacks a Base64 string back into the binary file it came from — an attachment out of a MIME email, a blob in an API response, or the contents of an image src attribute. Paste the string, type a filename including its extension (that extension decides which program opens it), and hit download. The file is assembled by the browser itself and lands straight in your downloads folder. See also: encode a file into Base64 again, open a Base64 string as an image, preview a Base64 blob as a PDF.

How to use it

  1. Copy the whole Base64 string, including a data:image/png;base64, prefix if there is one.
  2. Paste it into the Base64 string field — line breaks from an email or JSON payload are fine.
  3. Type a filename with the right extension into the filename field; it defaults to file.bin.
  4. Press the download button and the browser writes the assembled file to your downloads folder.
  5. Open it to check the result — an unreadable file usually means the string was truncated.

FAQ

Which extension should I use if I don't know the format?

Read the first few characters. JVBERi means PDF, iVBORw0KGgo is PNG, /9j/ is JPEG, and UEsDB is ZIP or an Office file such as docx or xlsx. If the data: prefix survived, the MIME type is written in it. Otherwise keep file.bin and rename the download once you can see what it contains.

Do I need to strip the data:application/pdf;base64, prefix?

No. Everything before the comma is discarded and the remainder is decoded, and a bare string with no prefix works just as well. What matters more is copying the tail of the string — truncated Base64 produces a file that looks right but ends mid-stream, and the viewer will refuse it.

Is there a size limit?

Only the memory available to the tab. A few megabytes decode in about a second, but a hundred-megabyte string can freeze the browser: Base64 inflates data by roughly a third, and both the text and the assembled file sit in memory at the same time. Very large attachments are safer to decode with a local tool.

Where does the pasted string go?

Nowhere outside the tab. The decoding uses the browser's own built-in function and the download is served from a temporary object created on this page. No request carrying your data is sent, so work attachments can be unpacked without handing them to a third-party service.

Why won't the downloaded file open?

Usually one of three things: the string was copied incompletely, stray characters came along from the interface (quotes, or the ellipsis from a shortened console dump), or the extension does not match the real format. Recopy from the source, delete the ellipses and try again with the right extension.

How do I go the other way, from a file to Base64?

Use the companion File to Base64 page: it takes a file through a picker and hands back the string. The two together close the loop — one turns a string into a file, the other turns a file into a string you can drop into JSON, CSS or an email body.

Examples

Icon returned inside an API response
Before: data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAAAAXNSR0IArs4c6QAAAARnQU1B...
After: logo.png saved to the downloads folder and opening in the image viewer
Attachment pulled out of a MIME email
Before: JVBERi0xLjQKJcfsj6IKNSAwIG9iago8PC9MZW5ndGggNiAwIFIvRmlsdGVyIC9GbGF0ZURlY29kZT4+...
After: report.pdf, opening in the system PDF reader