URL Formatter, Parser & Query Inspector

Normalize and format a URL, inspect every component, and optionally sort query parameters without sending a network request.

Browser-local

URL input

Paste an absolute URL to parse

Parsed output

Parsed URL components and query parameters

Formatted URL
https://api.example.com:8443/v1/users?id=42&id=43&debug=true#profile
Protocol
https:
Hostname
api.example.com
Port
8443
Pathname
/v1/users
Query string
?id=42&id=43&debug=true
Hash
#profile
Decoded query parameters
KeyValue
id42
id43
debugtrue

How to parse query strings

Paste an absolute URL and run the inspector. PayloadHarbor separates the scheme, host, port, pathname, decoded query parameters, and fragment so you can copy the structured result.

Repeated query keys are preserved in order and represented as arrays in the JSON query object.

URL inspection behavior

The parser uses the browser-compatible URL API. It validates structure only; it does not fetch the page, contact the host, follow redirects, or confirm that the remote service exists.

Normalize and format URLs safely

The formatted output normalizes the scheme and hostname, removes default ports when the URL standard permits it, and preserves the path, fragment, and query values. Optional query sorting orders keys deterministically while keeping repeated values.

URL formatting questions

What does URL formatting change?
It applies browser-standard normalization and can sort query keys while preserving paths, fragments, and values.
Does the formatter open or request the URL?
No. Parsing and formatting use the local browser URL API without contacting the host.
Are tracking parameters removed?
No. The formatter preserves query parameters and never removes them automatically.

What this URL Parser does

Use this URL formatter and URL parser to normalize a full URL and inspect its protocol, hostname, port, pathname, query string, decoded query parameters, and hash fragment. It supports API debugging, redirect review, OAuth callback checks, deterministic formatting, and query parameter parser workflows.

When developers use it

  • Parse query string values copied from API logs, browser devtools, OAuth redirects, and webhook callback URLs.
  • Inspect whether a URL uses the expected host, port, path, hash fragment, and repeated query parameters.
  • Copy structured URL components as JSON before adding them to tests, documentation, or support notes.

Privacy, input, and output

URL parsing runs locally in your browser with the standard URL API. PayloadHarbor does not fetch the URL or upload it to a server.

Paste an absolute URL and run Parse URL. The output shows a normalized copyable URL, optional sorted query keys, decoded fields, a query parameter table, repeated parameter order, and a JSON object.

Validation rules and limitations

  • Input must be an absolute URL with a scheme and hostname, such as https://api.example.com/search?q=test.
  • The inspector validates URL structure only; it does not check DNS, HTTP status, redirects, or whether the remote host exists.