Image to Base64
Encode any image into a ready-to-paste data URI or raw Base64 string.Image ToolsDrop your image here
A single image file of any common format
Up to 10 MB per file
Output format
Your files are processed on this device. Nothing is uploaded to a server.
About this tool
Base64 encoding is useful when an image has to travel inside HTML, CSS or JSON instead of as a separate file. This tool encodes the original file bytes, so the data URI keeps the exact source format and quality.
How to use the Image to Base64 tool
- Choose an image. Drop any common image file into the area below. The MIME type is detected from the file's actual bytes.
- Pick an output shape. Copy a full data URI (ready for an img src or CSS url()), or the raw Base64 payload without the prefix.
- Copy the result. Use the copy button and paste it into your code. A preview and the exact character count are shown alongside.
Supported formats
Input
- Any image format the browser can read
- JPEG, PNG, WebP, GIF, SVG, AVIF, HEIC (as bytes)
Output
- Data URI (data:<mime>;base64,...)
- Raw Base64 string
Inputs are validated before anything is processed. Invalid values and unsupported files are rejected with a clear error instead of failing silently.
Frequently asked questions
What is the difference between a data URI and raw Base64?
A data URI includes the `data:<mime>;base64,` prefix and can be used directly as an img src or CSS url(). Raw Base64 is just the encoded payload, intended for an API field or a JSON document where you supply the MIME type separately.
How much bigger does the image get?
Base64 represents 3 bytes as 4 characters, so output grows by roughly 33% plus the small prefix. The tool shows the exact character count so you can decide whether inlining is worth it.
When should I avoid data URIs?
For large images, a normal file is better: data URIs cannot be cached independently, block HTML parsing and bloat your markup. They are best for small icons, placeholders and single-file demos.
Does the image get re-encoded?
No. The original file bytes are encoded, so a JPEG stays a JPEG and a PNG stays a PNG, exactly as supplied.
Privacy
Encoding is a pure in-memory transform of the local file. No request containing your image is made.
No account is required and no file is ever uploaded. See the privacy policy for details about analytics and the limited data this site stores.
Known limitations
- Base64 adds about 33% overhead; keep inlined images small.
- Very large files produce long strings that can be slow to copy or paste in some editors.
- The tool encodes; it does not decode Base64 back into a downloadable file.
Related tools
Other free tools from the same collection.