Convert Text to Data URI

A URL scheme that embeds the resource inline – data:<mime>[;charset=…][;base64],<payload>. Defined in RFC 2397, they let you skip an HTTP request by putting a file’s bytes directly into the URL.

To inline small assets in HTML/CSS (saving a network round-trip), to mock API responses in tests, to attach a preview to a link, or to ship a self-contained page where every resource is embedded in the markup.

URL-encoded is shorter and human-readable for ASCII-heavy text (plain text, JSON, short HTML). Base64 is binary-safe, always a predictable 4/3 ratio, and the only sensible choice for SVG, large text, or anything with many special characters.

Yes. Encoding runs entirely in your browser – nothing is uploaded, cached, or tracked. After the page loads you can disconnect the network and keep encoding indefinitely.

image/svg+xml. Pair it with the Base64 encoding and you get a URI that works in every browser’s background-image: url(data:…) or <img src>.

Yes. HTML, CSS, and JavaScript are self-contained. Once the page has loaded, you can turn off Wi-Fi and the tool keeps working.

Yes, 100% free with no cap on input length or number of encodes. No sign-up, no premium tier, no watermark.

The tool has no cap, but browsers do. Chrome and Firefox handle URIs into the megabytes; older mobile browsers can choke around 32 KB. For large payloads prefer a real file URL or object URL.

RFC 2046 says text/* MIME types default to US-ASCII when no charset is present, which breaks anything non-ASCII. Keep the toggle on for text-based MIMEs unless you really know you want the old default.

Use the sibling Data URI to ASCII converter. It handles both the URL-encoded and Base64 variants with or without the charset fragment.