Is my image uploaded?
No. The image is read and encoded locally in your browser, so it never leaves your device.
What formats are supported?
PNG, JPG, WebP, GIF, and BMP images can be encoded to Base64.
How much bigger does Base64 make the file?
About 33 percent, because every 3 bytes become 4 characters. A 40 KB PNG becomes roughly 54 KB of text, plus the data URL prefix. That overhead is why inlining is only sensible for very small images.
When should I actually inline an image?
When it is under about 5 KB, appears on the critical path, and is used on one page. Icons and tiny sprites qualify. A hero photo does not: it will be 33 percent heavier, uncacheable on its own, and unable to be lazy-loaded.
What is the difference between the raw Base64 and the data URL?
The raw Base64 is the encoded bytes on their own. The data URL prefixes it with data:image/png;base64, so a browser knows how to interpret it. Use the data URL in CSS or an img src, and the raw string when you are putting it into JSON or a template that adds the prefix itself.
Can I encode an SVG?
Not here, since the encoder takes raster formats only. SVG is the one case where inlining reliably pays, and the better approach is to paste the SVG markup straight into your HTML rather than base64-encoding it, which is both smaller and stylable.
Is the image uploaded?
No. The file is read with a local FileReader and the base64 string is produced in the browser, so the image never leaves your device.