paramtree/ 02
Local by design

THE QUERY STRING WORKBENCH

Less encoding.
More understanding.

From tangled URLs to a clear picture.
Nested objects, real array indices,
and a second opinion from your server.

01 Your input

Read the parser docsBrowser simulations, not live server requests. UTF-8 text display; runtime settings and invalid-byte handling can differ.
Input in the hash.
Shared only by you.
How the parser thinks

Paramtree uses qs. Repeated keys combine into arrays. Dense numeric indices become arrays; sparse indices remain object keys, so 1 never turns into 0. Mixed scalar and nested names follow qs merge rules.

The decoded table preserves every pair, including duplicates. The JSON is a structural view, not a byte-for-byte reconstruction.

Limits are 2,000 pairs, 200,000 input characters. Paramtree has a 30-level nesting limit; server profiles use the defaults described above. Non-standard bracket syntax may be interpreted differently by your server.

02 The untangled version

0 parameters
STRUCTURE, WITHOUT THE GUESSWORK
Type hints never coerce values.