A data URI embeds a file directly inside a string using the form data:[mime];base64,[payload]. They are common in CSS, HTML and JSON to inline small images, fonts or icons. This tool reverses the embedding, recovering the original file.

Does it handle non-base64 data URIs?

Yes. If the header does not include the ;base64 flag, the payload is treated as percent-encoded text — the tool URL-decodes it and encodes the result as UTF-8 bytes for download. Most binary assets use base64, which is decoded with the browser's atob.

Is my data uploaded anywhere?

No. Decoding happens entirely in your browser, and the download is produced from an in-memory Blob object URL. The data URI you paste — which may contain private images or documents — never leaves your machine.

How is the file extension chosen?

The extension comes from the MIME type using a built-in map (for example image/png becomes .png, application/pdf becomes .pdf). For an unrecognised type the tool falls back to the MIME subtype or to .bin for application/octet-stream.

Why does the download show an image preview first?

When the MIME type starts with image/, the original data URI can be rendered directly in an img tag, so you can confirm you decoded the right asset before saving it. Non-image types skip the preview and go straight to the download button.

Data URI to File Converter

The Data URI to File Converter takes a data: URI and turns it back into a real, downloadable file. Paste the string, confirm the MIME type and size, preview images inline, and save the decoded bytes — all in your browser.

How it works

A data URI follows the form defined by RFC 2397:

data:[<mime-type>][;base64],<payload>

The converter splits the string at the first comma into a header and a payload, then:

reads the MIME type from the header (defaulting to text/plain when absent);
checks for the ;base64 flag;
decodes the payload — base64 via the browser’s atob, or percent-decoding for text data URIs — into a byte array;
chooses a file extension from the MIME type using a built-in map.

The decoded bytes are wrapped in a Blob and offered as a download through a temporary object URL, which is revoked immediately after the click.

Example

The URI data:text/plain;base64,SGVsbG8h decodes to the bytes for Hello! and downloads as a .txt file. A data:image/png;base64,... string previews the image, then downloads as a .png.

Notes

This is the inverse of a base64 file encoder. It is handy for recovering assets inlined in CSS, HTML or JSON, or for extracting an image a designer pasted into a message. Because decoding and the download both happen locally, no part of the embedded file is transmitted.