Data URI Generator - Online File to Base64 Converter

Text mode and file mode: text mode takes any text with an editable media type (text, vector graphics, scripts); file mode accepts drag & drop and detects the type from the file itself. After switching the encoding, regenerate before copying.

Base64 suits binary data like bitmaps and fonts, adding roughly 33% in size; percent-encoding suits text resources (SVG, style snippets) and preserves semantics better. Classic inline-SVG pitfall: the hash character must be encoded, or the stylesheet treats everything after it as an anchor. If you need a bare Base64 string without the data: prefix, use the Base64 tool instead.

Resources of a few KB benefit most: fewer requests and a snappier first paint. Beyond roughly 10 KB it usually backfires — base64 adds about a third to the size and oversized inlines slow parsing. Inlined resources cannot be cached separately either, so changing one icon invalidates the cache for the whole page. Glance at the output length before copying: abnormal bloat usually means the wrong encoding or an oversized image; compress or convert images first to shorten the URI.

Many email clients block external images by default, so inlining them as data URIs is the reliable way to get them shown — one of the most classic uses of this format.

Never commit key-bearing configuration as data URIs to a public repository; inline script URIs get blocked under some content security policies, so check the site policy first; and never paste an unknown data URI into a production page without confirming its media type and content.