Does Query String Parse upload my file or text to Tool-You servers?

No. Query String Parse runs in this browser tab. Files stay on the device. Limit note: Needs at least one pair. Sort is localeCompare.

Should I use Parse URL instead of Query String Parse?

Use Query String Parse when you need Decode query pairs; optional sort. Use Parse URL when you need Split a URL into host, path, query, and more. They share a category (Developer) but not the same job.

Query String Parse

Decode query pairs; optional sort.

Parses ?a=b&c=d or a full URL query into decoded lines. Optional alphabetical sort. Unlike Parse URL this focuses on query pairs only. Empty query fails.

What Query String Parse does

Parses ?a=b&c=d or a full URL query into decoded lines. Optional alphabetical sort. Unlike Parse URL this focuses on query pairs only. Empty query fails.

Practical limit for Query String Parse: Needs at least one pair. Sort is localeCompare. That is why output can differ from heavy desktop Developer software. Read the tool-specific note again: Parses ?a=b&c=d or a full URL query into decoded lines. Optional alphabetical sort. Unlike Parse URL this focuses on query pairs only. Empty query fails.

How to use Query String Parse

Keep this tab on Query String Parse (/developer/query-string). Pasting into the wrong Developer tool (for example Parse URL) changes the job.
Paste or type the input Query String Parse expects. Path hint: developer · query string. Decode query pairs; optional sort.
Apply the Query String Parse action only. URL Encode / Decode is a different transform (Percent-encode or decode a string (component or URI).). Parses ?a=b&c=d or a full URL query into decoded lines. Optional alphabetical sort. Unlike Parse URL this focuses on query pairs only. Empty query fails.
Copy the output of Query String Parse if you need it elsewhere. Size/complexity still follows: Needs at least one pair. Sort is localeCompare.
If the text job is actually Split a URL into host, path, query, and more., leave Query String Parse and open Parse URL.

When not to use Query String Parse

Skip Query String Parse when a neighbor tool matches better — start with Parse URL or URL Encode / Decode — or when the description already warns the job will fail. In the tool’s own words: Parses ?a=b&c=d or a full URL query into decoded lines. Optional alphabetical sort. Unlike Parse URL this focuses on query pairs only. Empty query fails.

Questions about Query String Parse

What does Query String Parse do that other Developer pages on this site do not?: Parses ?a=b&c=d or a full URL query into decoded lines. Optional alphabetical sort. Unlike Parse URL this focuses on query pairs only. Empty query fails. Short version: Decode query pairs; optional sort.
Does Query String Parse upload my file or text to Tool-You servers?: No. Query String Parse runs in this browser tab. Files stay on the device. Limit note: Needs at least one pair. Sort is localeCompare.
Should I use Parse URL instead of Query String Parse?: Use Query String Parse when you need Decode query pairs; optional sort. Use Parse URL when you need Split a URL into host, path, query, and more. They share a category (Developer) but not the same job.
What are the limits of Query String Parse?: Needs at least one pair. Sort is localeCompare. Also: Parses ?a=b&c=d or a full URL query into decoded lines. Optional alphabetical sort. Unlike Parse URL this focuses on query pairs only. Empty query fails.