Base64 to Image Converter

Base64 to Image: the picture back out of the string

Base64 strings turn up everywhere in real work: inside API responses, JSON payloads, log files, email source and old code. This tool turns one back into a file. Paste a raw Base64 string or a full data URI, and it decodes the text, works out what the bytes really are, shows you the format, the size and the pixel dimensions, previews the picture, and downloads the decoded bytes exactly as they came out.

The format is sniffed from the decoded bytes themselves, never trusted from the label. A data URI can claim to be a PNG while carrying JPG bytes, because labels get typed by hand and copied wrong. The opening bytes of a file do not lie: PNG, JPG, GIF, WebP and SVG each start with a signature this tool checks before it names the download.

How to convert Base64 to an image

1. Copy the Base64 string from your code, API response or document. The full data URI works too, prefix and all.
2. Paste it into the box above. Spaces and line breaks from a wrapped copy are stripped out for you.
3. Press the decode button. The tool decodes the text and reads the real format, size and dimensions from the result.
4. Check the preview. If the bytes are a displayable image, you see it before anything downloads.
5. Download the file. It holds the exact decoded bytes, with the extension that matches the true format.

Why the bytes get the final say

Two strings that look the same kind can behave very differently when decoded, and the bytes explain both. When a data URI label and the real format disagree, browsers often refuse to render the image or save it under a name nothing can open. Sniffing the signature sidesteps the whole problem: a PNG signature of 89 50 4E 47, a JPG opening of FF D8, the GIF8 header and the RIFF container of WebP each announce themselves in the first few bytes.

The same check protects you when the string is not a picture at all. Base64 can carry anything: a PDF, a font, a chunk of a zip file. When the decoded bytes are not an image, the tool says what it found and still offers the raw bytes for download, rather than pretending a preview exists. SVG is the one text-based case, recognized by its markup and previewed like any other picture. To go the other way, from a file to a string, the Image to Base64 encoder handles it.

When a string will not decode, honestly

The common failure is a cut copy. Consoles, log viewers and chat windows truncate long values in the middle, and a truncated Base64 string cannot be repaired, because the missing characters held real picture data and nothing can guess them back. If a decode fails, go back to the source and copy the value from the raw response or the file itself, not from a preview that shortens it.

Padding causes the second failure. Base64 strings often end in one or two equals signs, and some systems strip them. This tool tolerates the usual wrapping damage, stray spaces included, and fixes missing padding where the length allows it. What no tool can fix is a string that was never complete. And temper expectations the other way too: decoding is exact, so a picture that went into the string as a small, heavily squeezed JPG comes back out as that same small JPG. You get back exactly what was encoded, nothing restored and nothing improved.

Your strings stay in your browser

People decode Base64 pulled from private systems, internal tools and client data. That text is decoded in this tab, on your device, and none of it is uploaded or stored. There is no account, no daily cap and no watermark, on this page or anywhere in the image tools family.