Convert an image to Base64 text for a data URL, CSS rule, HTML snippet, Markdown image, or API test payload. Add JPEG, PNG, or WebP files, choose the output format, then copy from each image card or download TXT files.
The output stays focused on image-to-Base64 tasks: raw encoded text, full data URLs, and ready-to-paste snippets for HTML, CSS, Markdown, and text-based test payloads.
Raw Base64 and data URLs
Raw Base64 is only the encoded image data. It does not include the MIME type, so another system has to know whether the data is PNG, JPEG, or WebP.
A data URL includes the MIME type and the Base64 data in one value, such as data:image/png;base64,.... Use a data URL when the output will be pasted into an image source, CSS field, or self-contained demo.
Snippet formats
CSS output wraps the data URL in background-image: url("...");. HTML output creates an <img> tag with a data URL source. Markdown output creates image syntax with the Base64 data URL inside the link target.
These snippets are convenient for prototypes, documentation, email tests, and small embedded assets. They are not a good replacement for normal image files when the same image appears across many pages, because external image files can be cached separately.
Batch text export
Each card shows the image dimensions, MIME type, file size, and output character count. The character count matters because Base64 can become very long even for modest images.
Download one TXT file from an image card, or include selected cards in image-base64-files.zip. The ZIP contains text files, not converted image files.
Size and security
Base64 is encoding, not encryption. Anyone who receives the text can decode it back to the image.
Base64 also adds size overhead compared with the original binary file. Compress or resize the image first if the encoded text needs to stay small.