URL Parser
Parse, validate, and analyze URLs — component breakdown, query string editor, security and phishing checks, normalization, comparison, and batch parsing, all local to your browser.
Loading tool…
What is inside a URL?
A URL has a defined anatomy, standardised in RFC 3986: a scheme such as https, an optional userinfo section, a host, an optional port, a path, an optional query string, and an optional fragment after the hash. Written out, https://shop.example.com:8443/products/42?ref=email&utm_source=news#reviews contains every one of them.
The query string is where most of the interesting detail lives: key–value pairs separated by ampersands, with values percent-encoded so that spaces, slashes, and non-Latin characters survive transmission. Parsing a URL means splitting these components apart and decoding them, which turns an unreadable tracking link into a clear list of exactly which parameters are being carried and what they say. The fragment, notably, is never sent to the server — it is handled entirely by the browser.
Why we built this tool
Developers parse URLs when debugging redirects and callbacks, auditing analytics parameters, inspecting an OAuth flow, or working out why a link behaves differently than expected. Non-developers do it to see what a long tracking link is actually carrying about them.
Those URLs often contain session identifiers, signed tokens, email addresses, and one-time codes in the query string. Pasting them into a website hands over a live credential in some cases. Ours parses using the browser's built-in URL interface, in your tab, with no request sent — the link is never transmitted, logged, or stored. It also means the tool answers instantly and works with no connection.
Tips and common mistakes
- The fragment after the hash is never sent to the server, which explains a lot of confusing redirect behaviour.
- Strip
utm_and other tracking parameters before sharing a link publicly. - Treat any URL containing a token or a one-time code as a live credential.
- Percent-encoded non-Latin characters expand to several escapes each; that is correct, not corruption.
Open URL Parser with a link
Assistants and scripts can open URL Parser with its input already in the link, after the #, which never leaves your device:
#text=— the text to work on
Example: https://mygadgets.ink/tools/url-parser/#text=... · also compressed gz fields and ?url=. How tool links work
Quick start: using URL Parser
- Paste the URL into the input above.
- Read the broken-out components: scheme, host, port, path, query, and fragment.
- Review the query parameters as a decoded list.
- Look for tracking parameters, tokens, or personal data you did not expect to be there.
- Copy the part you need, or strip the parameters before sharing the link.
For manual encoding work, use URL Encoder/Decoder; to inspect a token found in a link, try JWT Decoder.
The anatomy of a URL
Take https://shop.example.com:443/products/shoes?color=red&size=10#reviews. Its parts:
- Protocol/scheme —
https— how to connect. - Host —
shop.example.com— the server, including any subdomain. - Port —
443— usually implied and hidden. - Path —
/products/shoes— which resource on the server. - Query string —
color=red&size=10— key/value parameters after the?. - Fragment —
reviews— an anchor within the page, after the#.
Parsing separates all of these so you can read or manipulate each one.
The query string is where the interesting stuff lives
Most debugging centers on the query parameters. A single marketing URL might carry a dozen: utm_source, utm_campaign, tracking IDs, and functional parameters that change what the page shows. Parsing lists them cleanly as key/value pairs so you can:
- See every tracking parameter attached to a link.
- Confirm an API call is sending the right arguments.
- Spot a malformed or duplicated parameter causing a bug.
Watch for encoding
Values in a URL are often percent-encoded — a space becomes %20, an & inside a value becomes %26. Parsing shows the raw pieces; to decode a value into readable text, URL Encoder/Decoder handles that layer. The two tools complement each other: parse to split, decode to read.
Common uses
- Debug a broken link by inspecting its parts.
- Audit tracking parameters on a campaign URL.
- Verify an API endpoint's arguments.
- Extract a specific parameter value.