Create and inspect data URIs. Turn text into a data: URL with your choice of media type and percent or Base64 encoding, convert any number of files at once, or paste a data URI to see what's inside — its media type, encoding, parameters and real size — with a preview and a download of the decoded file. It's free, runs in your browser, and files never leave your device.
| Part | Example |
|---|---|
| Scheme | data: |
| Media type | image/png |
| Parameters | ;charset=utf-8 |
| Encoding flag | ;base64 |
| Payload | ,iVBORw0KGgo… |
A URL that contains the file itself: data:, a media type, an optional ;base64 flag, a comma and the data.
Binary files need Base64. For text, percent-encoding is readable and usually smaller.
About a third bigger — every 3 bytes become 4 characters.
Inspect it first. HTML data URIs are used for phishing pages; this tool shows what's inside without opening it.
No. Encoding and decoding happen in your browser.
A data URI, defined in RFC 2397, embeds a file directly in a URL as data:[media type][;parameters][;base64],payload. For text the payload can be percent-encoded, which keeps it readable and is often shorter; for binary it must be Base64, which grows the data by a third. The generator writes either for text, with the chosen media type and a UTF-8 charset, shows both sizes, and turns any number of dropped files into Base64 data URIs using each file's own type. The inspector doesn't trust what it's given: it checks the data: prefix and the comma, validates the media type, defaults to text/plain as the RFC specifies when none is given, separates parameters like charset, decodes the payload and reports its real size. Images are previewed and text is shown, and the decoded bytes can be downloaded as a file. An HTML data URI is flagged, since that format is a common phishing technique and browsers block top-level navigation to it. Everything is processed locally.