Convert a local image into raw Base64 or a data URI.
Choose an image. Processing happens entirely in your browser.
SVG is not accepted. The file type is checked against its content signature; Base64 output can be about one-third larger than the original.
How to use it
A PNG produces a data URI beginning data:image/png;base64, followed by the exact file bytes encoded as Base64.
Supported files are PNG, JPEG, WebP, and GIF up to 8 MiB. SVG is rejected, and the declared MIME type must match the file signature. The full file is read into browser memory. Base64 usually adds about one-third to the byte length before the data-URI prefix, so it is best suited to reasonably small assets.
FAQ
No. Base64 represents the original file bytes exactly; it does not resize or recompress the image. It does make the text representation larger.
Practical guidance
Choose a data URI when a destination expects the complete data:image/...;base64,... value, such as an HTML image source or a CSS URL. Choose raw Base64 when an API, configuration field, or decoder supplies the media type separately.
Base64 text is larger than the original binary file and the browser must hold the full input and output in memory. Prefer ordinary image files for large assets, reusable images, or content that benefits from independent browser caching.
Converting text instead? Open Base64 Encoder & Decoder