Skip to content
FizzKit

Image Converter & Base64

Drop, upload or paste an image to get a Base64 data URI with HTML, CSS, Markdown, JSX, srcset, <picture> and image-set() snippets — or convert it: change the format to PNG, JPEG, WebP or AVIF with a quality slider and live output size, resize by exact dimensions, maximum edge or scale factor, flatten transparency, and export a favicon set. Decode a data URI or raw Base64 back into a downloadable image, read the EXIF orientation, camera and date from JPEGs (and see that conversion strips it), and process files in batch. SVGs get a compact UTF-8 data URI. Everything runs in the browser with a 20 MB per-file guard.

Runs locally in your browser

How to use Image Converter & Base64

  1. 1Drop, choose or paste an image (⌘V works anywhere on the page).
  2. 2Optionally pick a target format and quality, and a resize rule — the output size updates live.
  3. 3Copy the data URI or an embed snippet, or download the converted file / favicon set.
  4. 4Use the Base64 → image tab to decode a string, or Batch to convert many files with the same settings.

About Image Converter & Base64

Drop, upload or paste an image to get a Base64 data URI with HTML, CSS, Markdown, JSX, srcset, <picture> and image-set() snippets — or convert it: change the format to PNG, JPEG, WebP or AVIF with a quality slider and live output size, resize by exact dimensions, maximum edge or scale factor, flatten transparency, and export a favicon set. Decode a data URI or raw Base64 back into a downloadable image, read the EXIF orientation, camera and date from JPEGs (and see that conversion strips it), and process files in batch. SVGs get a compact UTF-8 data URI. Everything runs in the browser with a 20 MB per-file guard.

Image Converter & Base64 is part of FizzKit — a collection of focused developer and ad-tech tools. Because everything runs locally, it works offline once loaded and never exposes your data to a remote server.

Frequently asked questions

For very small images used in CSS or email, or when you want to avoid an extra request. Base64 adds about 33 % and cannot be cached separately, so photos should stay as files.