About Image2Base64

Last updated: 2026-11-10

Image2Base64 is a free, independent utility site for encoding images to Base64 strings and data URIs, and for decoding those strings back into files. Older screenshots may show the header as Base64Img; it is the same site. It is not a product of Google or of any image-hosting company. The site has been operating since 2026 and is hosted on Cloudflare.

Around the converters sits a library of format guides — why a PNG with transparency behaves the way it does, how email clients treat inline images — plus compression and resizing tools, a Base64 size calculator, and a set of photo privacy utilities. Common questions are collected on the FAQ.

Who runs it

The site is built and operated by one person: Jerome (GitHub @Jeromelll). There is no company behind it, no editorial staff, and no support desk. Source code and the issue tracker are public at github.com/Jeromelll/image2base64, so bug reports and fixes happen in the open. Corrections, tool bugs, and advertising questions go to jeromell@be-winner.com; the contact page explains what to include so a report can be reproduced quickly.

Why everything runs in your browser

Every converter executes locally with the FileReader and canvas APIs built into your browser. Your image is decoded, processed, and re-encoded on your own machine; the bytes never leave the device, and nothing is stored server-side. You can confirm this in the Network tab: choosing a file does not produce an upload request.

The design has three practical consequences. Privacy: a confidential screenshot, an ID scan, or a family photo can be converted without anyone else ever holding a copy. Speed: there is no round trip, so conversion takes however long your machine needs, not a turn in a server queue. Independence: once the page has loaded, the conversion itself needs no further connection.

What the tools do

The converters cover the formats developers actually run into:

Compression and resizing tools shrink a file to a byte target before encoding, and a size calculator tells you how much text a given image will produce once encoded. Separate photo privacy utilities let you see what a photo reveals about itself — camera details, timestamps, location tags — and remove it before sharing; the remove photo metadata tool is the main entry point, with an EXIF viewer alongside it. Because the tools are ordinary web pages, they behave the same on Windows, macOS, Linux, Android, and iOS, with nothing to install.

What the guides cover

The guides deal with the cases that actually break: a PNG with alpha behaving differently after conversion, an animated GIF coming out as a still frame, the data:image/png;base64, prefix getting lost in a paste, or Outlook and Gmail refusing to render an inline image. Others walk through integrations — embedding images in a single HTML file, sending Base64 payloads through mail and chat APIs, uploading attachments through third-party services. Several are troubleshooting notes rather than tutorials, written for the failure modes that keep repeating: a signature image visible to the sender but not the recipient, an API that rejects a Base64 attachment because it expects multipart form data, a bot that needs the payload wrapped differently. Each guide states what the browser really does with that format, including when a conversion is not lossless, instead of repeating one generic paragraph about Base64 on every URL. How pages are written and verified is documented in the editorial policy.

Optional sign-in

Signing in with Google, GitHub, or X is optional and exists purely for convenience. Every tool works without an account, and signing in does not open any upload path for image data — there is still no server pipeline for your files.

How the site is funded

Google AdSense keeps the tools free. Ads stay out of the converter interface, and guides contain no sponsored recommendations. First-party analytics are cookieless event pings used to see which tools get used; they do not build advertising profiles or follow you across sites. Cookie and vendor details are on the privacy policy, and authorized ad sellers are listed in ads.txt.