Image to Base64

Base64 represents every 3 bytes of binary as 4 text characters, an unavoidable 33 percent overhead, and the data URI prefix plus padding nudges it a little higher. That's why the preview estimates about 1.37 times the original size.

The Data URI tab includes the data:image/...;base64, prefix that browsers require to render the string directly. Raw Base64 is just the encoded payload, which is what you want when an API field or JSON schema expects the bare string.

A few kilobytes is the comfortable zone; think icons, logos, and tiny UI textures. It only pays to convert image to base64 string output for assets that small, because larger files bloat your CSS or HTML and lose the benefit of separate caching.

Support is patchy. Some clients render data URI images fine, while several major webmail clients strip or block them. Test in your actual target clients before committing, and keep a hosted image fallback for the ones that refuse.

Yes, any image type your browser recognizes is accepted, and the data URI carries the file's real MIME type, such as image/webp or image/svg+xml. For SVG specifically, plain URL encoding is sometimes more compact than Base64, but both work.

No, GitHub's image proxy doesn't serve data URIs, so the image simply won't render there. Inlined images are best kept to HTML, CSS, and JSON payloads you control end to end.

Not independently. The image data is cached only as part of the stylesheet or page that contains it, so changing the image invalidates that whole file. That's another reason to reserve inlining for small, rarely changing assets.

Drop an image under 5 MB onto the uploader, then pick an output tab. To do image to base64 online you don't press a convert button, the encoding runs the moment the file loads, and you just copy the Data URI, raw payload, CSS, or HTML you need.

It's fully online with nothing to install. As an online converter image to base64, it runs the encoding in your browser tab, so the file never uploads and the string appears instantly. That also means it keeps working if your connection drops after the page loads.

No, it's a single action. To convert to base64 online, just load the image; the tool reads it and fills all four output tabs at once. Switch between Data URI, Raw Base64, CSS, and HTML without re-uploading, and hit Use another to swap files.

It turns the binary image into plain text that fits inside a JSON string field, which is why APIs often ask for it. Use the Raw Base64 tab for that image to base64 conversion, since JSON wants the bare payload without the data URI prefix.

The uploader accepts image files, so you convert in base64 the picture types your browser can decode. It isn't a general binary encoder for zips or PDFs; for those you'd need a different tool. Here the focus is images headed into CSS, HTML, or an API field.

Yes, that's exactly the case it handles. To convert file to base64, drop the image in and copy the result; the tool encodes image files up to 5 MB. Non-image files aren't supported here, since the output is built for inline image embedding.

Open the CSS tab after loading your image. It wraps the data URI in a ready-made background-image rule you can paste straight into a stylesheet, so the icon ships with the CSS and needs no separate request. The Data URI tab gives you the bare data: string if you'd rather build the rule yourself.

No, this one only encodes. To base64 decode image data, use the Base64 to Image tool on this site: paste the string or data URI there and it renders the picture and offers a download. Think of the two tools as opposite directions of the same job.

Copy the Raw Base64 or Data URI from this page, then open the Base64 to Image tool and paste it in. It renders the payload as a picture and lets you save it as a real file, which is a quick way to confirm your encoded output is intact.