Free URL Query String Parser, Builder & Encoder | Dev Toolkit
Skip to main content

Free Online URL Query String Parser, Builder & Encoder

Parse, build, and batch-process URLs with full query string manipulation.

Table View:
OnKeyValue
{
  "page": "1",
  "limit": "20",
  "status": "active",
  "sort": "name",
  "order": "asc"
}
const url = new URL('https://api.example.com/users');
const params = new URLSearchParams();
params.append('page', '1');
params.append('limit', '20');
params.append('status', 'active');
params.append('sort', 'name');
params.append('order', 'asc');
url.search = params.toString();
console.log(url.toString());

About the Query String Parser

Query strings are how web applications pass parameters in URLs — pagination, filters, search terms, tracking parameters, and API keys all live in query strings. Parsing, building, and debugging them manually is tedious. This tool parses any URL into its components, lets you edit parameters visually, and rebuilds the URL — with proper encoding and decoding.

What this tool does

URL Parser

Breaks any URL into protocol, host, path, and query parameters. Decodes percent-encoded values for readability.

Visual Editor

Add, edit, remove, and reorder query parameters in a table view. The URL updates in real time with proper encoding.

Code Generation

Generates JavaScript (URLSearchParams), Python (urllib), and curl code for constructing the URL programmatically.

Batch Parsing

Parse multiple URLs at once and compare their query parameters — useful for analytics URL audits and log analysis.

Pipeline

  • cURL to Code — convert a cURL command with query parameters to code.
  • URL Encoder — encode/decode individual URL components.
  • HTTP Codes — reference status codes returned by the endpoints you're building URLs for.

Frequently asked

Is my URL data sent to a server?
No. All parsing and building runs 100% in your browser. Your URLs — which may contain sensitive query parameters — never leave your device.
What is a query string?
A query string is the part of a URL after the "?" character. It contains key=value pairs separated by "&". For example: ?page=2&sort=name&filter=active. Query strings pass parameters to web servers and APIs.
What is URL encoding and why is it needed?
URL encoding (percent-encoding) converts characters that are not allowed in URLs to a safe format. Spaces become %20, & becomes %26, = becomes %3D. Without encoding, special characters in parameter values would be misinterpreted as URL structure.
What is the difference between encodeURI and encodeURIComponent?
encodeURI encodes a full URL — it does not encode characters that are valid URL structure (/, ?, &, =, #). encodeURIComponent encodes a single parameter value — it encodes everything including /, ?, &, and =. Always use encodeURIComponent for individual parameter values.
Can I parse multiple URLs at once?
Yes. The batch mode parses multiple URLs simultaneously and shows the query parameters for each — useful for comparing URLs from analytics exports or log files.