Base64 to Image

Paste your Base64 — drop the string or a Data URI into the editor, or drag in a .txt file that contains it. Extra whitespace and line breaks are stripped automatically.

Fix if needed — if a raw string lacks the data:image/...;base64, header and won't render, open Advanced Options and click "Fix Missing URI Prefix". You can also strip the prefix, or turn on Gallery Mode to decode several strings at once.

Download or copy — save the decoded image to your device in its native format, or copy it straight to your clipboard. ```

Paste your Base64 string or Data URI into the editor — or drag in a .txt file containing it — and the tool instantly detects the format and renders the image. Then click Download to save it, or copy it to your clipboard. Stray whitespace and line breaks are cleaned up automatically, so you don't have to tidy the string first.

No. Decoding happens entirely in your browser, so the Base64 data is turned into an image on your own device and never uploaded. Nothing is stored once you close the tab. That keeps the contents private — useful when a string came from a confidential project or API response.

Most often it's missing the header. A browser needs the data:image/...;base64, prefix to know the string is an image and what type it is. Open Advanced Options and click "Fix Missing URI Prefix" to add it automatically. If it still won't render, the string may be truncated or contain characters that aren't valid Base64.

A Data URI is a Base64 string with a prefix like data:image/png;base64, that tells the browser the data is an image and which format it is. That prefix is what lets a Data URI render directly in an img tag or CSS. This tool reads Data URIs and can also add the prefix to a bare Base64 string.

Yes. Open Advanced Options and turn on Gallery Mode, then paste multiple Base64 strings with one per line. The tool decodes them all and shows a grid of images you can download individually. It's a fast way to extract several inline images from a stylesheet or data file in one go.

It auto-detects the common ones — PNG, JPG, WebP, GIF, and SVG — from the Data URI's type or the data itself, and saves the decoded file in its native format. So a PNG Data URI downloads as a .png, an SVG as .svg, and so on, without you having to specify the format manually.

Yes. Alongside the download button there's a copy option that places the decoded image on your clipboard, so you can paste it straight into a document, chat, or design tool without saving a file first. It's handy for quickly checking and reusing an inline image.

No. Decoding is the exact reverse of encoding — it reconstructs the original bytes, so you get back an identical image with no quality loss. Base64 is just a text representation of the file, so converting it back produces the same pixels the original had.

The tool downloads the image in whatever format the Base64 actually represents — if the data is a PNG, you get a PNG. To change the format afterwards (say PNG to JPG), run the downloaded file through the relevant converter, such as PNG to JPG. The decoder itself preserves the original format.

Use the Image to Base64 tool, which does the opposite of this page — it takes an image file and produces a Base64 string or Data URI you can paste into HTML or CSS. The two tools pair together so you can move freely between image files and Base64 text.

There's no server limit because everything runs locally, but very long strings use more of your device's memory. Base64 images are typically small inline assets, so most strings decode instantly. An extremely large string may take a moment or strain an older device.

Yes. It runs in your phone's browser with nothing to install, so you can paste a Base64 string and decode it to an image on Android or iOS, then download or copy it. As a developer tool you'll often use it on a computer, but it works on mobile when you need to check a string on the go.