Last updated ·Published ·By the WiserWork team
URL Parser
Extract protocol, host, path, query parameters & more from URLs
| Parameter | Value |
|---|---|
| No parameters found | |
Paste a web address and see it split into protocol, host, hostname, port, pathname, origin, query and fragment, with every query parameter listed as a separate row.
What is the URL Parser?
Every web address is a stack of named parts. Reading left to right there is the scheme, an optional port after the host, a pathname that identifies the resource, a query string introduced by a question mark, and a fragment after the hash that the browser keeps to itself. This page hands your input to the browser's built-in URL constructor and prints eight of those fields side by side, then walks the query string with URLSearchParams so each key and value gets its own table row.
Key Features
- Eight component cards: protocol, host, hostname, port, pathname, hash, origin, query
- Query parameters broken out into a two-column table of keys and values
- Copy as JSON exports every parameter as an indented key-value object
- An empty port falls back to a note about the 80/443 defaults
- Parameter values arrive decoded, so %20 and plus signs read as spaces
Common Use Cases
- Auditing a campaign link to confirm utm_source, utm_medium and utm_campaign are spelled correctly
- Pulling an order or session id out of a long support-ticket link
- Checking whether a redirect target sits on the origin you actually expect
- Turning a messy tracking URL into JSON you can paste into a test fixture
How to Use the URL Parser
- Replace the example address in the box with the URL you want to inspect.
- Include the scheme, since https://example.com parses and example.com on its own does not.
- Read the URL Components grid for the protocol, host, port, path, origin, query and fragment.
- Scroll to the Query Parameters table to see each key beside its decoded value.
- Press Copy as JSON to put the whole parameter set on your clipboard as a formatted object.
Tips for Best Results
- The grid updates as you type, so the Parse URL button is only there if you prefer clicking
- A bare domain reports Invalid URL; prefix it with https:// and the components appear
- Host includes the port and hostname does not, which is the only difference between those two cards
- Repeated keys each get their own row, so you can spot a parameter that was added twice
Why Use WiserWork's URL Parser?
The parsing comes from the URL and URLSearchParams objects already inside your browser, which follow the published specification rather than a homegrown regular expression that guesses at edge cases. The address is only read as text; the page never requests it, so inspecting a one-time sign-in link or a signed download URL does not spend it. Results appear as labeled cards instead of a raw dump, which makes the port and origin easy to check at a glance.
Who Uses the URL Parser?
Marketers and analysts open it to verify UTM tagging before a campaign goes live. Developers and QA engineers use it while tracing redirects, OAuth callbacks and deep links. Support and security teams lean on it to read a suspicious address without clicking through to it.
Frequently Asked Questions
What are the parts of a URL?
A full address runs scheme, host, optional port, pathname, query string and fragment, as in https://example.com:8080/path?key=value#section. The tool labels each of those, plus origin, which is the scheme and host together.
Why does my URL show as invalid?
The URL constructor needs an absolute address with a scheme. Adding https:// to the front usually fixes it, since relative paths such as /about cannot be parsed on their own.
What is the difference between host and hostname?
Hostname is just the domain, while host appends the port when one is present. For example.com:8080 the hostname is example.com and the host is example.com:8080.
Why does the Port card mention 80 and 443?
When no port is written in the address there is nothing to display, so the card notes the defaults instead: 80 for http and 443 for https.
How does a query string work?
Everything after the question mark is a list of key=value pairs joined by ampersands. Order is not meaningful to most servers, and the same key may legitimately appear more than once.
What are UTM parameters?
They are the conventional query keys utm_source, utm_medium, utm_campaign, utm_term and utm_content that analytics tools read to attribute a visit. They are ordinary parameters, so they appear in the table like any other.
Is the fragment sent to the server?
No. The part after the hash stays in the browser and is used for in-page anchors or client-side routing, which is why it never turns up in server logs.
Does the tool open or fetch the URL I paste?
No. It treats the address purely as a string to take apart, so nothing is requested and no redirect or tracking pixel is triggered.
What happens to duplicate parameters in the JSON export?
The table shows every occurrence, but a JSON object holds one entry per key, so a repeated key keeps only its last value. Read the table when duplicates matter.
Are the parameter values shown encoded or decoded?
Decoded. A value stored as New+York or New%20York is displayed as New York, and that is also the form used by the JSON copy.
A URL is a compact record of scheme, location, path, parameters and anchor, and most link problems turn out to be a wrong value in one of those slots. Paste the address here and read the slots directly.