it3 — URL shortener & tools

Image to Base64 Converter

Get a data URL or the raw Base64 payload. Copy in one click—nothing leaves your device.

Open tool

Drop image, paste from clipboard after focusing here, or browse.

Works in modern desktop and mobile browsers. Focus this area (tap or Tab) before pasting.

About this tool

Base64 grows size versus binary, but it is convenient for inline images, small assets in JSON, and quick prototypes. Do not paste secrets in public pages; very large files can bloat your markup.

When useful

  • Inline img src=data URL in HTML
  • Email signatures (small icons)
  • Config snippets needing embedded bytes

Outputs

  • Drag & drop, paste, or browse
  • Full data URL
  • Raw Base64 only
  • Copy buttons

How it works

  1. Add an image.
  2. Wait for encode.
  3. Copy data URL or raw Base64.

FAQ

Why does Base64 make the payload bigger?

Binary files are dense; Base64 encodes every three bytes as four ASCII characters (~33% overhead) plus the `data:image/...;base64,` prefix for URLs. That inflation matters when you embed multi-megabyte photos—small icons are fine, hero images are not.

Is it safe to paste customer IDs or tokens into the tool?

Processing is local, but anything you embed in public HTML or JavaScript becomes visible to every visitor and scraper. Treat Base64 in pages like any other secret: if it should stay private, keep it on the server and serve binary via authenticated routes.

Which MIME appears in the data URL?

It reflects what the browser knows about the `File` object—typically `image/png`, `image/jpeg`, or `image/webp`. If an OS mislabels a rare type, downstream consumers might mis-parse; re-export through a known format when integrating with picky parsers.

Clipboard paste from designers?

Yes: focus the dashed zone and press Ctrl/Cmd+V when Slack, Figma exports, or snipping tools place an image on the clipboard. Some mobile browsers restrict clipboard image writes—use browse as fallback.

Limits on file size?

Very large images produce strings that choke textarea rendering, DevTools copy, or backend JSON parsers with default limits. Prefer assets under a few hundred KB for inline patterns; otherwise use a CDN URL.

How does this differ from the text Base64 tool?

This page is optimized for files: you get both the full `data:` URL and the naked Base64 block, with MIME included automatically. The general encoder targets arbitrary UTF-8 strings, not raster decode guarantees.

Buy Me a Coffee at ko-fi.com