We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Parse URL strings into structured JSON to quickly extract key information like protocols, parameters, and paths.
Enter content on the left to view the conversion result in real-time
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
This page turns URL query parameters into a formatted JSON object, or serializes JSON input into a query string. A query string is the portion of a URL after ?, commonly written as pairs such as search=books&page=2. In query-to-JSON mode, you can paste a bare parameter string, a string beginning with ?, or a full URL containing a question mark; the converter takes the text after the first question mark. It outputs parameter data, not the URL’s scheme, host, path, or fragment.
Query components follow URL form-encoding conventions. Percent escapes are decoded, and a plus sign is read as a space; encode a literal plus as %2B. The reverse direction percent-encodes values for a query string. The WHATWG URL Standard describes these URLSearchParams parsing and serialization rules. RFC 3986 defines the query component’s position in the URI syntax, and RFC 8259 defines JSON objects and values.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Paste a query string or a full URL with query parameters. For example, https://example.com/search?q=tea+set&page=2&debug becomes {"q":"tea set","page":"2","debug":""}. Parameters without an equals sign become empty-string values.
Percent-encoded characters are decoded. A plus sign means a space, so q=red+fox produces "red fox"; use %2B to represent a literal plus. JSON output values from query parameters are strings, even when they look like numbers or booleans.
Enter valid JSON and the result updates as you type. For example, {"q":"tea set","page":2} serializes to q=tea+set&page=2. Copy the result and append it to a base URL yourself, adding ? if that URL does not already have a query.
Use the copy control for the displayed output. Switching direction carries the current output into the input, which can help inspect a conversion, but the two formats do not preserve every distinction.
Query strings can contain the same name more than once. A JSON object has one member for each unique name, so this converter keeps the last value it reads: tag=red&tag=blue becomes {"tag":"blue"}, not an array. If your API expects repeated keys or arrays, check its parameter conventions before relying on a round trip.
For JSON-to-query conversion, use a simple object with scalar values such as strings, numbers, or booleans. When represented in the query string, numbers and booleans become text; for example, false is serialized as flag=false and comes back from query-to-JSON as the string "false". Nested objects and arrays are not a dependable reversible representation here; use a format agreed with the receiving application.
Use cases
See how the tool fits into real work and everyday tasks.
Paste a link containing search, sort, or pagination parameters to view its encoded values as readable JSON. Ignore the domain and path when checking only the parameter data.
Turn a small JSON object into a query string to place in a test request or browser address. Confirm how the target endpoint handles booleans, repeated keys, and empty values before sending it.
Try a value with spaces, a literal plus sign, or non-ASCII text to see how form-style encoding is decoded and rebuilt. This is useful when debugging a link or checking a sample parameter set.
Q&A
Find concise answers to common questions and confusing cases.
Yes, if it has a question mark. The converter extracts text after the first ?; it does not return scheme, hostname, path, or fragment fields. A bare query string works too.
In form-style query encoding, + represents a space. To preserve an actual plus character, encode it as %2B before converting.
Each JSON object property name can hold only one value in this conversion. When the query repeats a name, the last value replaces earlier values. The output does not group repetitions into an array.
No. Query parameter values are returned as strings. A value written as 2 becomes "2", and true becomes "true"; JSON-to-query therefore is not a type-preserving round trip.
Notes
Review scope, result limitations, and important precautions before use.
Query-string conventions differ across APIs and server frameworks. Before using converted output in a request, verify how the destination expects repeated names, empty values, arrays, nested data, and text encoding.
Related
Discover related tools, collections, and available API capabilities.