What is it?
Image to Base64 turns a picture into text (Base64) you can put directly in code, and turns Base64 back into a file.
Who is it for?
Web developers, email designers and people building single-file HTML pages or apps, who need small images embedded in code; also anyone who received Base64 text and needs the image back.
How to use it
- Choose the Direction.
- Pick images or paste Base64.
- Choose the output format and copy or download.
Image → Base64
- Set Direction to Image → Base64 and Choose images (PNG, JPG, SVG, GIF, WebP, ICO).
- Pick the Format: Data URL (data:image/…), Base64 only, HTML <img> tag, CSS background, Markdown image or JSON string.
- Copy the Result.
Base64 → Image
Set Direction to Base64 → Image, paste a data:image/… URL or plain Base64, choose its type if it’s plain Base64, and tap Download file. PDFs work too.
When to use Base64 images
- Good for small icons and logos (a few KB) in emails, single-file HTML pages, or the HTML to PDF tool.
- Avoid it for big photos on websites: Base64 is about a third larger, can’t be cached separately, and slows the page. Upload normal image files instead.
“This is not valid Base64”
Check that nothing was cut off when copying; long strings are often trimmed by chat apps.
Are my files uploaded?
No. The file is opened and processed inside your browser, on your own phone or computer. Nothing is sent to us, and closing the page clears it.
Example
A 2 KB PNG icon becomes a data URL of about 2.7 KB, like data:image/png;base64,iVBORw0KG…. Choose CSS background to get background-image: url(data:image/png;base64,…) ready to paste.
Open the tool: Image to Base64
Still stuck?
Contact support. Tell us which tool or page you were using, what you tapped, what you saw, and your phone or computer and browser (for example: Android phone, Chrome). We reply by email.






























Questions, or an error not listed here?
Tell us in the comments: what you were doing, the exact message you saw, and your device and browser. We read every comment and add new fixes to this article.