How URL Percent-Encoding Works (RFC 3986)
URLs sent across the World Wide Web can only be transmitted using the US-ASCII character set. Because web addresses frequently contain characters outside this range (such as accented characters, non-Latin alphabets, and emojis) or reserved characters used as protocol delimiters (such as ?, &, /, and :), they must be converted into safe percent-encoded triplets.
A percent-encoded character consists of a percent sign (%) followed by the two-digit hexadecimal representation of its corresponding UTF-8 byte.
Common Reserved & Special Character Encoding Reference
encodeURI vs. encodeURIComponent: When to Use Which?
encodeURIComponent (Query Parameter Encoding)
Encodes all reserved characters including ; , / ? : @ & = + $ #.
encodeURI (Full URL Address Encoding)
Preserves reserved characters essential to URL structure (http://, ?, &, =) and only encodes illegal characters like spaces and emojis.
Frequently Asked Questions (FAQ)
How does the query parameter table parser work?
When you paste an address containing a question mark (?), the tool extracts the query string, splits key-value pairs separated by &, and displays each parameter in a clean decoded inspection table.
Does this tool support emojis and non-English UTF-8 characters?
Yes. Multi-byte UTF-8 sequences (such as emojis like 🚀 and Chinese/Japanese/Arabic scripts) are encoded into multi-triplet hexadecimal sequences (e.g. 🚀 becomes %F0%9F%9A%80).