Developer
Encoders, converters & dev utilities
Base64 to Image — Decode & Download In-Browser
Paste a Base64 string that encodes an image (PNG, JPEG, GIF, WebP) and this tool decodes it, renders a live preview, and lets you download the file with the correct MIME type. Base64 (RFC 4648) is how images are embedded inline in CSS, HTML data URIs, and JSON API responses — every 3 bytes become 4 characters. You can often recognise the format from the first characters: a PNG begins with the signature bytes 89 50 4E 47 0D 0A, which Base64-encode to the prefix iVBORw0K, so PNG data URIs famously start iVBORw0KGgo. Decoding runs 100% in your browser via atob/Uint8Array + a Blob object URL, so the image never leaves the page. Free, no login.
Decode = Base64 → raw bytes → Blob with the image MIME (image/png, image/jpeg…) → preview + download
- Byte-exact tell: the PNG signature 89 50 4E 47 0D 0A → Base64 "iVBORw0K" (PNG data URIs start iVBORw0KGgo)
- A data URI wrapper like data:image/png;base64, is stripped so only the payload is decoded
- 100% client-side (atob + Uint8Array + Blob URL) — your image is never uploaded
- Base64 only transports the bytes — it is encoding, not encryption, and hides nothing
Frequently asked questions
How do I convert a Base64 string to an image?
Paste the Base64 (or a full data: URI) and the tool decodes it into the original image bytes, wraps them in a Blob with the right MIME type, and shows a preview you can download. It all happens in your browser with atob and a Uint8Array — no upload. If your string begins data:image/png;base64, the tool strips that wrapper and decodes only the Base64 payload after the comma.
How do I know what image format the Base64 is?
The first bytes (the file signature) tell you, and they show through in the Base64 prefix. A PNG starts with bytes 89 50 4E 47 0D 0A, which encode to iVBORw0K — so PNG strings usually begin iVBORw0KGgo. A JPEG starts with FF D8 FF, which encodes to /9j/. Matching the prefix confirms the format before you download, and the tool sets the correct MIME type accordingly.
Does the image get uploaded to a server?
No. The decode is entirely client-side: the Base64 becomes bytes via atob/Uint8Array and is rendered from a local Blob object URL, so the image never leaves your browser — you can verify this in the network tab. This is why a client-side decoder is safe for private or unreleased images. (Note that Base64 is not encryption, so the data itself is not protected — it is simply not transmitted.)