ASCII Banner Generator
Turn text into a block-letter ASCII banner for a README or a CLI.
Serialise a JSON object into a percent-encoded URL query string.
The JSON to Query String converter serialises an object into a percent-encoded query string, writing nested objects in bracket notation and letting you pick which of the three array conventions your backend actually parses.
The reverse trip: a JSON object becomes a query string ready to append to a URL. Nested objects are written in bracket notation, and every key and value is percent-encoded so the result is safe to paste into an address bar or a curl command.
Arrays are the part libraries disagree about, so the format is a choice rather than an assumption. Bracket style writes tags[]=a&tags[]=b, which PHP and Rails expect. Indexed style writes tags[0]=a&tags[1]=b, which some strict parsers require. Repeated style writes tags=a&tags=b, which Express and most Java frameworks read. Pick the one your backend actually parses and the output will round-trip through the Query String to JSON tool unchanged.
Bracket for PHP and Rails, indexed for strict parsers, repeated for Express and most Java frameworks. Pick the one your backend reads.
Reserved characters inside a value are escaped rather than breaking the string, so an ampersand in a name stays part of that name.
Any depth of nesting is written in bracket notation, which is what server-side parsers rebuild into structures.
Turn encoding off to inspect the structure of a long query string, then turn it back on for the real thing.
The output reads back through the Query String to JSON tool unchanged, which is the quickest way to confirm it is right.
Nested objects and arrays are supported; the root must be an object.
Bracket, indexed or repeated — match whatever your backend parses.
Leave percent-encoding on for a usable URL, or turn it off to read the structure more easily.
Append it to a URL after a question mark.
Bracket for PHP and Rails, repeated for Express and most Java frameworks, indexed when a strict parser insists on positions. If you are unsure, repeated is the most widely understood.
Yes, with encodeURIComponent semantics, so spaces become %20 and reserved characters such as & and = inside a value are escaped rather than breaking the string.
There is no limit in the specification, but browsers and servers impose one — around 2,000 characters is the safe practical ceiling. Send larger payloads in a request body instead.
They are written as an empty value, such as name=. Remove the key from the JSON entirely if you want the parameter to be absent rather than empty.
What people who use the JSON to Query String think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the JSON to Query String. It takes half a minute and no account.
Write the first reviewTurn text into a block-letter ASCII banner for a README or a CLI.
Generate the border trick that makes triangles and tooltip arrows.
Strip every optional byte from a JSON document and see what you saved.
Turn an SVG into a React component with the attributes React expects.
Describe a shape and get as many rows of matching JSON as you need.
Convert a start and end address into the smallest set of CIDR blocks.
See your own user agent string and what a server can tell from it.
Build a frosted glass panel with backdrop blur, over a real background.