URL Parser & Query Inspector
Inspect URL components and repeated query parameters using the browser URL parser, with an optional base for relative paths.
Processing stays in this browser. Inputs are not sent to a tool-processing server or saved by this utility. Limit: 500,000 characters per input.
Learn with worked examples
How to use URL Parser & Query Inspector
- Paste an absolute URL, or a relative path with an absolute base in the second input.
- Inspect the normalized URL, host, path and query parameter list.
- Check repeated parameters and encoding before changing your request builder.
A reproducible example
Use Load example to try this input, then change one value and inspect the result.
https://example.com:8443/api/search?tag=php&tag=json&q=hello+world#results
Second input:
https://example.com/Preserve repeated query parameters
A URL such as ?tag=php&tag=json contains two tag entries. Converting those directly into a plain object can overwrite one value. This inspector displays an ordered list of key/value pairs so repeated keys remain visible. Match your backend’s interpretation before changing the client.
Understand plus signs and percent encoding
URLSearchParams interprets + as a space in query values. The query q=hello+world is displayed as hello world; a literal plus can be encoded as %2B. The pathname and query-string representation have different encoding rules. Encode components when building a request, rather than encoding an entire assembled URL.
Resolve relative paths explicitly
A relative path requires a base URL. With a base of https://example.com/app/, items resolves below /app/, while /items resolves from the origin root. The normalized output helps diagnose why a frontend sends a request to an unexpected path.
Parsing does not fetch or validate safety
The tool makes no request to the entered address. A syntactically valid URL can still lead to an unsafe destination, expose credentials or fail when fetched. Do not use successful parsing as an SSRF allowlist or evidence that a host exists. This tool uses browser URL semantics, which may differ from another runtime.
Common questions
Does the tool visit the URL?
No. It parses locally without fetching the destination.
Why did the default port disappear?
The browser normalizes URLs and may omit a scheme’s default port. Inspect the normalized output when comparing addresses.
Read the format or engine documentation. Found an edge case? Send a small reproducible example.