Data URI Decoder
Break an RFC 2397 data: URI into its media type, parameters, encoding, byte length, and decoded text.
This tool handles input and primary processing in your browser and is designed not to send the input to QuickKit’s server.
Avoid live production secrets; use dummy or masked data where possible. Data handling details
How it works
Paste a data: URI to see its declared media type, its parameters (such as charset), whether the payload is base64 or percent-encoded, the decoded byte length, and a hex preview of the first 16 bytes. For textual media types (text/*, application/json, +xml, +json, image/svg+xml, application/javascript) the decoded UTF-8 text is shown. Parsing follows RFC 2397 (checked 2026-09-02); when the media type is omitted the default text/plain;charset=US-ASCII is reported and flagged as a default. The part after the comma is the URI's payload and is treated as data — it is not trimmed; only whitespace before the data: scheme is stripped. A base64 payload is validated for RFC 4648 structure (alphabet, padding placement and count, and a possible final quantum); interior whitespace in a base64 payload is ignored, as browsers do. This tool reports only what the URI declares and never infers a media type from the decoded bytes. Input is capped at 2 MiB.