About this base64 to image
This base64 to image tool restores an image file from encoded text. It accepts ordinary padded base64 or a raster image data URL that begins with a MIME type and the base64 marker. This is useful when an API response, saved document, or debugging log contains the picture as text instead of as a separate downloadable file.
Paste the complete value and click Decode image. Spaces and line breaks are removed before decoding. The tool checks the alphabet and padding, inspects the decoded file signature, and verifies that a stated MIME type matches the actual format. A successful result shows a preview, dimensions, byte count, and a download link with the correct extension.
Base64 is an encoding, not encryption or an image format. This tool does not improve image quality or convert between formats; the download retains the original binary bytes. PNG, JPG, GIF, WebP, AVIF, BMP, TIFF, and ICO are accepted when their decoded image is readable. SVG, HTML, URL-safe base64, malformed padding, and content larger than 40 MiB are rejected. Processing stays inside your browser and the pasted text is not submitted to a server.
Which controls should I check first?
The Base64 to Image form labels its controls as Base64 image or data URL. Use those labels to keep the source and settings separate. A sample argument that selects a mode is not additional source text. Choose the setting matching your intended operation before copying a result, and change it explicitly when comparing another mode. The labels describe what this form accepts; the worked examples below demonstrate only the stated supplied values.
How should I interpret this specific operation?
A data URL's declared MIME type must agree with the decoded signature. The eight PNG signature bytes in the helper example establish header recognition only; they do not constitute a complete renderable picture. A valid result needs both the byte representation and an image that can actually decode. The download retains decoded original bytes rather than recompressing the source.
Worked helper values
These values come from the reproducible calculation examples supplied with this tool. Each row identifies the complete supplied arguments and the returned value. A visible ↵ denotes a line break and ⇥ denotes a tab in text examples. Settings appear alongside source data so that a different mode is not mistaken for an identical input. These are helper calculations, not observations of a live device, fetched target, image decoder, browser preview or downloaded file. Use the stated method above to relate the returned fields to the actual operation.
| Supplied values | Calculated return value |
|---|---|
| photo.heic; jpg | photo.jpg |
Is this a representation change or a content change?
An encoding expresses bytes or characters using a different alphabet or escape notation. It should not be confused with encryption, compression or permission to execute the result. Work out which layer the receiving field expects before converting. A URL component, a complete URL, an HTML text node and a JSON string need different escaping rules. Encoding for one context does not automatically make a value safe in another. Keep the unencoded source while editing and convert at the boundary where the destination requires it. Otherwise repeated conversions can encode existing escape markers rather than the original content.
How do I diagnose a malformed input?
Check the alphabet, prefix, separators and final padding against this tool's documented input format. A pasted quotation mark or trailing label can turn a valid payload into invalid text. For UTF-8 decoding, a byte sequence can be syntactically valid in its outer representation yet still fail to represent text. Binary images and compressed data are examples of payloads that should not be forced through a text decoder. Use the appropriate file or image workflow for them. Do not remove padding or percent signs at random to make an error disappear; first identify what those characters mean in the expected representation.
Why does decoding once matter?
A value can have more than one encoding layer. Decoding the outer layer yields another encoded string rather than necessarily reaching the final readable content. Repeating the operation is appropriate only when the source format specifies those layers. With URL components, decoding separator characters too early can change the structure of a query. With HTML entities, a decoded angle bracket is ordinary text until another application interprets it as markup. Inspect the result as text before placing it into an active context. Keep a record of which layer you decoded so that a later step does not accidentally repeat it.
How do non-ASCII characters affect the result?
A character such as é occupies more than one UTF-8 byte. An emoji can require several bytes even when it occupies one visible position. Encoders process those bytes according to their representation rules, so output length cannot be predicted from visible character count alone. A percent-encoded character can consist of several percent triplets, and Base64 groups bytes rather than visible letters. Compare the worked Unicode example with the result instead of assuming one output group per character. A strict text decoder helps expose damaged bytes that would otherwise be replaced by an ambiguous replacement character.
Can I paste a complete data URL?
Yes, if it identifies a supported raster image and includes the ;base64, marker.
Does this change the image quality?
No. It decodes the original file bytes; the download is not re-encoded.
Why is a MIME mismatch rejected?
The declared type must agree with the actual image signature so a misleading extension is not offered.
Can this render SVG?
No. This decoder accepts raster images only and does not render SVG or HTML.