URL Parser & Query Parameters Editor
Decompose any URL into its components, edit query parameters in a visual grid, and rebuild a clean URL — 100% free and client-side.
Paste any URL to decompose it into components, inspect and edit query parameters in a visual grid, then copy the rebuilt URL — all client-side with no data sent anywhere.
Query Parameters (5)
| # | Key (decoded) | Value (decoded) | Raw | |
|---|---|---|---|---|
| 1 | q | hello world | q=hello+world | |
| 2 | lang | en | lang=en | |
| 3 | page | 1 | page=1 | |
| 4 | sort | relevance | sort=relevance | |
| 5 | filter | active | filter=active |
Complete URL Decomposition
Instantly break any URL into protocol, username, password, hostname, port, path, query string, and fragment — with copy buttons on every field and a clear table of all decoded query parameter key-value pairs.
Visual Query Parameter Editor
Edit query parameters in a familiar spreadsheet-style grid. Add, delete, sort, enable or disable individual parameters, and switch between percent-encoded and human-readable decoded views at any time.
Instant URL Rebuild with Encode Control
Modify the protocol, hostname, port, path, authentication, or fragment directly, and watch the rebuilt URL update in real time. Toggle percent-encoding to produce clean human-readable URLs or RFC 3986 compliant encoded output.
100% Free — Client-Side & Private
All parsing, decoding, and rebuilding uses the browser-native URL API with no server communication. Sensitive URLs containing API keys, session tokens, or authentication credentials never leave your device.
API Endpoint Debugging
Paste long API URLs from error logs, decompose all query parameters, and instantly see which key carries the wrong value without string manipulation or manual decoding.
UTM Parameter Inspection
Decode and audit campaign tracking URLs from email newsletters or ad platforms, verifying utm_source, utm_medium, utm_campaign, and utm_content values at a glance.
OAuth / OIDC Callback Analysis
Inspect authorization callback URLs containing code, state, and scope parameters to debug OAuth 2.0 flows during development or security reviews.
URL Sharing & Sanitization
Remove sensitive tracking parameters, disable specific query keys, sort parameters alphabetically for consistency, then copy a clean rebuilt URL.
Webhook Signature Debugging
Decompose incoming webhook URLs to compare query-string signatures, timestamps, and nonce values against expected values when diagnosing HMAC verification failures.
SEO URL Auditing
Verify that canonical URLs, pagination parameters, and facet filters are correctly formed before submitting a site for indexing or diagnosing duplicate content issues.
The Aback Tools URL Parser decomposes any web address into its RFC 3986 components and provides an interactive editor for query parameters — entirely in your browser. No data is transmitted to any server at any point.
URL Anatomy
A URL (Uniform Resource Locator) is a structured string with several optional parts defined in RFC 3986. The scheme (e.g. https:) identifies the protocol. The authority section contains optional user credentials, the hostname, and an optional port. The path identifies the resource on the server. The optional query string after the ? carries key-value parameters. Finally, the fragment after the # identifies a subsection within the page.
Percent-Encoding
Query parameter keys and values must not contain raw special characters such as &, =, +, or Unicode. These characters are instead encoded as %XX hexadecimal sequences. For example, a space becomes %20 (or + in the older application/x-www-form-urlencoded encoding). The editor shows both the raw encoded form and the human-friendly decoded form, and re-encodes your edits automatically when you toggle the "Percent-encode" option.
URL Rebuild Engine
After editing, the tool reassembles the URL from its parts in the correct RFC 3986 order: scheme, authority (credentials, host, port), path, query string, and fragment. Parameters that are disabled via the checkbox are omitted from the output. Parameters are serialised in the order they appear in the grid, preserving your intended priority.
Privacy Notice
Because parsing runs client-side using the browser's built-in URL API, URLs containing authentication tokens, API keys, or session identifiers are never exposed to any third party. The tool is safe to use with production credentials or private endpoints.
The parser handles any syntactically valid URL — HTTP, HTTPS, FTP, WebSocket (ws://, wss://), mailto, tel, and custom schemes. If no protocol is detected, https:// is assumed automatically. Malformed URLs that cannot be parsed by the browser's native URL API are flagged with a descriptive error.
No. All parsing, decoding, and rebuilding is performed client-side using the browser's built-in URL API and JavaScript string operations. Nothing leaves your browser. This makes the tool safe to use with URLs containing API keys, session tokens, OAuth codes, or any sensitive credentials.
Percent-encoding converts special characters (spaces, &, =, Unicode) into %XX hex sequences so they are safe to include in a URL. Enable the toggle when you need a standards-compliant URL for embedding in HTML, HTTP headers, or API requests. Disable it to get a readable URL for sharing in chat or documentation.
Yes. The Edit & Rebuild tab shows each parameter in an editable row. Click "Add Parameter" to insert a new row, click the bin icon to remove one, use the Sort button to sort alphabetically, or use the checkbox to temporarily disable a parameter without deleting it. The rebuilt URL updates instantly.
When "Decoded" is active, the editor shows human-readable values — e.g. "hello world" instead of "hello%20world". Edits made in decoded view are automatically re-encoded when building the output URL. Switching to "Encoded" shows raw percent-encoded strings, useful when you want to paste a pre-encoded value verbatim.
The fragment (also called the hash) is the part after the # symbol. It is not sent to the server — it is used by browsers to scroll to a page section, or by single-page applications for client-side routing. You can edit it in the URL Components section of the editor, and it is appended last to the rebuilt URL.
If no protocol is detected (no scheme followed by ://), the tool prepends https:// internally before parsing with the browser URL API. This lets you paste hostnames like "api.example.com?key=val" and still get a valid breakdown. The displayed components reflect the actual structure without the added protocol.
Related Tools
JSON to YAML
Convert JSON to YAML format instantly - Free online JSON to YAML converter
XML to YAML
Convert XML to YAML format for configuration migration - Free online XML to YAML converter
CSV to YAML
Convert CSV spreadsheet data to YAML format - Free online CSV to YAML converter
TSV to YAML
Convert TSV tab-separated data to YAML format - Free online TSV to YAML converter