URL Encoder & Query Parser
Convert text to and from RFC 3986 standard percent-encoded values. Automatically parses and tables full query string parameters.
URL Query Parameters Parser Params Extracted: 0
Deep Dive: URI Schemas, Percent-Encoding Math, & Query Parameters
What is URL Encoding (Percent Encoding)?
Uniform Resource Identifiers (URIs) are designed to transmit characters over the web reliably. However, the standard internet protocol restricts characters allowed inside a URL to a small subset of the ASCII character set. The remaining characters are categorized into **Reserved** (which serve structural purposes, like `/` for paths, `?` for queries, and `&` for separators) and **Unreserved** (alphanumeric characters, hyphens, periods, underscores, and tildes).
To transmit spaces, structural symbols, or emojis safely in a URL parameter without disrupting the routing parsing of the browser, we use **Percent Encoding** (defined under the global RFC 3986 guideline). Every reserved or non-ASCII symbol is converted into its UTF-8 octet byte equivalent, and expressed as a percent sign (`%`) followed by a two-digit hexadecimal representation of that byte (e.g. a space translates to `%20`, and `&` translates to `%26`).
Unreserved Characters
Includes characters that do not have special structural meanings in URIs: `A-Z`, `a-z`, `0-9`, `-`, `.`, `_`, and `~`. These characters are never encoded by standard web engines.
Decoding Errors & Safety
Trying to decode invalid percent-encoded sequences (such as `%99%` or arbitrary `%` symbols) throws a Javascript URIError. Our engine catches this safely to prevent UI freeze crashes.
Common Reserved Characters Reference
Refer to the data matrix below to review typical reserved characters and their corresponding percent-encoded hex coordinates:
| Character | Structural URL Role | Percent Encoded String | ASCII Code Value |
|---|---|---|---|
| `Space` | Separates parameter words or strings | `%20` or `+` (in query fields) | 32 |
| `?` | Marks the beginning of the query parameter string block | `%3F` | 63 |
| `&` | Separates individual key-value query pairs | `%26` | 38 |
| `=` | Binds a query parameter key to its value | `%3D` | 61 |
| `/` | Acts as a path segment directory separator | `%2F` | 47 |
| `:` | Separates URI schemes from directory paths (e.g. `https:`) | `%3A` | 58 |
HTML Forms & Application Encoding Models
When submitting HTML forms via standard GET/POST protocols, web browsers encode form values using the standard `application/x-www-form-urlencoded` format. In this model, spaces can be encoded as a plus sign (`+`) rather than `%20`. Modern development practices prioritize using standard `encodeURIComponent` and parsing full search strings through native `URLSearchParams` libraries to avoid cross-platform mismatches.