Paste a Base64 string or a full data: URI to render the image inline. We auto-detect PNG, JPEG, GIF, WebP, BMP, and SVG from the magic bytes. Everything runs in your browser.
PNG, JPEG, GIF, WebP, BMP, and SVG. The tool auto-detects the format from the first few bytes (the "magic number") — you don't need to tell it which format you have. Full data URIs (data:image/png;base64,...) are also accepted.
PNG, JPEG, GIF, WebP, BMP, and SVG. The tool detects the format automatically from the magic bytes at the start of the decoded data — you do not need to specify which format you have.
No. If the decoded bytes do not match a known image signature, the tool shows an error and refuses to render. This prevents accidentally treating a non-image binary as an image, which would just render as a broken image icon.
The decoder handles strings up to about 50 MB of decoded output (around 67 MB of Base64 input). Larger files should use a desktop tool. For very large data URIs in CSS or HTML, consider whether direct file references would be more appropriate.
No. Decoding and rendering happen entirely in your browser. The data URI shown in the preview is generated locally from the decoded bytes.
src attribute with the pattern data:[mediatype];base64,[data]. For a PNG:<img src="data:image/png;base64,iVBORw0KGgo..." alt="Inline image">image/png, image/jpeg, image/svg+xml), otherwise the browser may refuse to render it.data:image/png;base64,), that no spaces or newlines crept into the Base64, and that the padding is intact. A wrong media type or a single stray character stops the browser from reconstructing the pixel data.