Open Convert to Base64
Convert a supported image to JPG output, then copy its raw Base64 or full data URL.
Encode small images as Base64, add the correct data URL prefix when needed, and avoid oversized CSS, HTML, or JSON payloads.

Base64 turns output file bytes into text and makes the raw data about one-third larger. Choose the JPEGConvert route that matches the format you want because these pages may convert or re-encode the uploaded image before producing Base64; use a normal file URL for large or reused images.
Choose the output format first, then copy the right Base64 form and decode-test the result.
Resize or compress it first and choose JPG, PNG, WebP, GIF, or SVG based on the content.
Use JPG to Base64, PNG to Base64, or another named page for the output format you need; the general Convert to Base64 page targets JPG.
Copy a full data URL for CSS or HTML, or switch to raw Base64 when an API asks for the encoded characters only.
Decode the final stored or transmitted value and compare its format, dimensions, and appearance with the converter output.
Base64 itself changes binary bytes into text characters. It does not compress an image or improve its quality.
Convert a supported image to JPG output, then copy its raw Base64 or full data URL.
JPEGConvert image-to-Base64 pages call an image conversion route before returning the text, so the encoded bytes may not match the original upload byte for byte.
For Base64 image embeds, include the matching MIME type and ;base64 marker in the data URL. Many APIs expect raw Base64 without that prefix instead.
An SVG background can contain Base64 text or URL-encoded XML. Check which form you have before changing the prefix or trying to decode it.
A successful decode only confirms that the encoded file can be recovered. A blank image can still come from the SVG or the way the page displays it.
No. Base64 usually makes the raw data about one-third larger. Compress or resize the image before encoding if size matters.
Raw Base64 is only the encoded text. A data URL adds a prefix such as data:image/png;base64, so a browser knows the media type and encoding.
Common causes include a missing or wrong MIME type, a truncated string, added spaces, unsafe JSON escaping, or an API that expects raw Base64 instead of a data URL.
Base64 can recover the bytes it contains. JPEGConvert may convert or re-encode the upload first, so decoding restores that output image, not necessarily the original upload byte for byte.
No. SVG is XML text and can be embedded as a URL-encoded data URL as well. Use ;base64 only when the payload is Base64. For a normal external SVG file, a file URL is usually simpler to maintain.
Choose the tool for the change your file needs.