Free Base64 to Image Converter – Decode & Download

How Base64 Is Decoded Back into an Image

This is the decoder side of the data URI story. You have a long text string, either raw Base64 or a full data URI beginning with the data prefix, and you need to see the picture it represents or save it as a real file. Paste it here and the image renders immediately with a download button. Developers pull these strings out of stylesheets, API responses, JSON config blobs and email source all the time, and the question is nearly always the same: what actually is this, and is it the right asset? Reading a Base64 string by eye tells you nothing, so decoding is the only way to answer. The decode reverses the encoding exactly. Each Base64 character maps back to a six-bit value, four characters regroup into three bytes, and the padding characters at the end tell the decoder how many real bytes the final group holds. Those bytes are the original file, byte for byte. If your input is a full data URI, the MIME type is already declared in the prefix, so the browser knows whether to treat the bytes as PNG, JPEG, WebP, GIF or SVG. If you paste raw Base64 with no prefix, the format is inferred from the file signature in the leading bytes, the so-called magic number. A PNG always starts with the byte sequence 137, 80, 78, 71 followed by a carriage return and line feed pattern, and a JPEG always starts with 255, 216, 255. The decoded bytes are then wrapped in a Blob and shown, and the same Blob backs the download. Here is a real string you can learn to recognise. A one-pixel transparent PNG encodes to text beginning iVBORw0KGgoAAAANSUhEUgAA and running about 96 characters in total. Decode it and you get exactly 70 bytes whose first eight values are 137, 80, 78, 71, 13, 10, 26, 10, which is the standard PNG signature. The preview shows a single transparent pixel, which looks like nothing at all, but the byte count and signature together confirm the encoding is sound. That leading iVBOR pattern is worth memorising, because any Base64 string starting with it is a PNG. Likewise a string that begins with slash 9 j slash is a JPEG, and one starting PHN2Zw is an SVG, so you can identify a format before you decode anything. Where it gets used. A developer inherits a stylesheet full of inlined icons and decodes each one to work out which is the outdated logo that needs replacing. Someone debugging an image upload endpoint decodes the Base64 the client sent to confirm the file arrived intact rather than truncated in transit. A designer receives a logo pasted into a chat message as a data URI and decodes it to get a usable PNG back. A tester decodes the avatar returned by an API to verify the server is not silently returning a grey placeholder instead of the real file. A support engineer decodes an attachment lifted out of a webhook log to see what the customer actually received. Two things to watch. Truncation is the most common failure: Base64 strings are long and copying from a code editor or a terminal often drops the tail, leaving a string that decodes into a partial file which renders as a broken image or nothing at all. Check that the string ends where you expect and includes its padding characters. The other point concerns SVG specifically: an SVG is executable markup, so decoding one from an untrusted source and opening it in a browser can run embedded script. Treat unknown SVGs with the same caution as any untrusted file. Decoding happens entirely in your browser through a local Blob, so unreleased artwork and client assets are never uploaded anywhere.

🔥 Trending Tools