Developer Workflow

Parse a URL query string for debugging

Break a pasted URL into host, path, query parameters, repeated keys, and fragments so redirects, tracking links, and API callbacks are easier to debug.

Open Url Parser

Problem

Full URLs hide multiple layers of structure in one line. A broken redirect or tracking link may fail because a parameter was split at the wrong ampersand, a fragment was copied as part of the value, or a nested URL was never encoded before transport.

When to use this

A redirect URL sends users to the wrong path or drops a return parameter.
UTM, campaign, or affiliate parameters look present but analytics records different values.
An OAuth, SSO, or webhook callback includes a nested URL that is hard to inspect.
A support ticket includes a long link and you need to identify host, path, query keys, and fragments before editing it.

Steps

Step 1
Paste the complete URL
Copy the full link from the browser, log entry, webhook payload, or support ticket. Keep the protocol, host, path, query string, and fragment intact.
Step 2
Separate structure from values
Use URL Parser to split protocol, hostname, pathname, query, and hash. This confirms whether the suspicious text is URL syntax or a parameter value.
Step 3
Inspect repeated and nested parameters
Open Query String Parser for the query section when keys repeat or a value contains another URL. Repeated keys may be intentional, but they should be visible before editing.
Step 4
Encode only the broken value
If a value contains `?`, `&`, `=`, `#`, or spaces, encode that value with URL Encoder and Decoder instead of encoding the entire URL.

Example

Debug a return URL with tracking parameters

Input

https://login.example.com/callback?next=https://app.example.com/search?q=url parser&utm_source=newsletter#complete

Output

host=login.example.com, path=/callback, next=https://app.example.com/search?q=url parser, utm_source=newsletter, hash=complete

Common mistakes

Editing a long URL before parsing it

Changing a raw URL first can hide the original failure. Parse first, then edit one value at a time.

Encoding the full URL

Encoding the whole URL turns separators such as `?` and `&` into data. Encode only the nested value unless the whole URL is being transported as one value.

Ignoring fragments

Anything after `#` is a fragment and may not be sent to the server. If a required value appears there, the backend may never receive it.

FAQ

Should I start with URL Parser or Query String Parser?

Start with URL Parser when you have a full URL. Switch to Query String Parser when you only need to inspect the part after `?`.

Why does a URL work in the browser but fail in an API callback?

Browsers and server frameworks may normalize encoding, plus signs, repeated keys, or fragments differently. Parsing the URL makes those boundaries visible.

Can this fix broken UTM tags?

It can help identify whether UTM keys were dropped, repeated, or nested inside another value. After parsing, fix only the incorrect value and test the link again.