SMALL RESOURCES, COMPLETE BYTES
Generate a complete data: URL or recover its bytes. Compare Base64 and percent encoding before embedding a small resource.
Text, files and URI contents stay in this browser; nothing is sent or saved in a URL.
Enter type/subtype without parameters. Text uses UTF-8; file bytes stay unchanged. MIME is a declaration, not format detection.
Maximum: 600,000 source or decoded bytes; 1,900,000 URI characters; 1,024 header characters.
MIME: text/plain;charset=utf-8 · Charset: utf-8 · Encoding: Base64
Full URI lengths: Base64 65 · Percent 80
20 bytes · 65 URI characters
A broken inline icon may come from one unescaped hash, a missing comma or the wrong encoding marker. The Data URI converter makes these parts visible so you can inspect the wrapper separately from the resource it contains.
The Data URI converter shows both URI lengths for the same bytes. A small SVG often benefits from percent encoding, but punctuation and non-ASCII text can change that balance. Compare the numbers instead of assuming one method always wins.
A Data URI decoder should distinguish readable text from a binary file. Inspect the type and encoding, review literal text or hexadecimal bytes, then download the complete resource. HTML and SVG remain source text throughout the inspection.
The SVG entry starts with percent encoding and fixes the MIME type to image/svg+xml. Switch to Base64 to compare full lengths. The preset does not validate the drawing, remove scripts, change colors or compress the XML.
Automatic conversion waits 350 ms after a change. Disable it to use Convert or Ctrl/Cmd + Enter. Editing content, MIME or encoding immediately disables export until that input has been converted; changing modes preserves each input.
In parse mode, the result may be text or hex. The caption tells you which one Copy result will return. Download bytes always saves the entire decoded resource. Example, Clear and file replacement require review and allow one undo.
Generate from UTF-8 text or one local file. The header carries MIME and the encoding marker. Text includes charset=utf-8; files use their supplied MIME or application/octet-stream when the browser has no type, with a manual override.
Percent encoding operates on bytes, so %FF can represent a byte even though it is not valid UTF-8 text. A plus sign remains a plus. Generated URIs escape quotes, parentheses, hashes, whitespace and non-ASCII bytes for a portable value.
Parsing recognizes an omitted type, charset and other non-repeated parameters, plus a final base64 marker. The first comma separates metadata from content. Percent-escaped parameter values are accepted; malformed escapes and ambiguous parameters are reported.
Read the original or recovered byte count and the complete URI character count. The editor initially shows 20,000 characters and can reveal more. Copying and downloads use the full current result, regardless of how much is visible.
With data:, the media type defaults to text/plain;charset=US-ASCII. A shorthand such as data:;charset=utf-8, supplies the character set explicitly. The parser reports the effective type and charset; it does not guess them from a filename.
Base64 is a predictable choice for binary resources; its payload length is four times the ceiling of bytes divided by three. Percent encoding can be shorter for mostly plain ASCII, including some SVG sources. Compare the two complete URI lengths for your actual content.
Browsers and consuming applications have their own limits, but this tool accepts at most 600,000 resource bytes and 1,900,000 URI characters. Large embedded assets also enlarge their containing document. A separate file is often easier to update and cache.
Yes. Text and SVG generation use UTF-8 and preserve line endings and a leading BOM. Unpaired UTF-16 surrogates are rejected rather than replaced. Decoding displays valid supported text; other byte sequences remain available as hex and a byte download.
No. File selection reads bytes in the browser. The workbench does not upload input, create a share URL or persist a draft. A downloaded URI still contains the complete data, so share that file only when you intend to share its contents.
Have a URI that needs another case?
Use the Data URI converter to compare the two encodings, check metadata and verify recovered bytes before placing an asset in your project.