Boolean Query Parameters – Build true and false from JSON

Local only

Show the exact string representation used for JSON booleans in Build Query mode.

31 chars · 1 line

47 chars · 3 lines

1 parameter1 unique keys

Query primitive serialization

How JSON booleans are written into a query string

Build Query stringifies boolean primitives. true becomes the text true and false becomes the text false; the builder does not silently convert them to 1/0 or presence-only flags. This tool is free to use. No account or payment is required.

Last updated

What you can do here

  • Browser-native URLSearchParams behavior
  • Full URL and raw query parsing
  • Repeated parameter preservation
  • JSON object to query construction
  • Browser-local processing

Steps

  1. Enter boolean JSON properties in Build Query.
  2. Inspect the generated true/false text.
  3. Confirm the receiving API expects those strings rather than 1/0 or key presence.

Query strings remain textual at the transport layer

The builder applies String() to supported primitive values before URLSearchParams serialization.

When the generated query is parsed again, those values return as strings. Boolean interpretation belongs to application logic.

true and false values

Both booleans are emitted explicitly.

JSON object

{"debug":true,"archived":false}

Built query string

debug=true&archived=false

Common questions

Frequently asked questions

Does false remove the parameter?

No. false is emitted as the text false.

Does true become 1?

No. It becomes the text true.

Will Parse mode return booleans?

No. Generic query parsing returns strings.

Debugging a specific Query String issue? Browse Query String troubleshooting.