Skip to content
GigAI Tools

URL Parser, Break a URL Into Its Components Online

Paste a link and see it decomposed the way a browser does (scheme, host, port, path segments, decoded query parameters, fragment and origin) then watch it rebuild live so you can verify every part. Runs entirely in your browser: no request is ever made to the URL.

100% browser processingFree · no sign-up

What is the url parser?

GigAI URL Parser breaks any URL into scheme, host, path, query parameters and fragment, decodes every percent-encoded value, and lets you edit parameters and rebuild the URL - all in your browser. Paste a 500-character tracking link and see exactly what's in it. Nothing is sent anywhere.

The GigAI URL Parser takes any absolute URL and splits it into the exact components defined by the WHATWG URL standard (the same parsing engine browsers use) so what you see here is what your code, your CDN and Googlebot see. Paste a link (or drop one in) and get a clean, labelled breakdown: protocol/scheme, optional userinfo, hostname, port, the full pathname plus its individual segments, the raw query string, and the hash fragment, alongside derived values like origin, the registrable domain, subdomain and TLD, and whether the connection is secure. Every query parameter is listed in a table with keys and automatically percent-decoded values, so a messy ?utm_source=news&ref=a%2Fb&q=hello%20world becomes readable at a glance, invaluable for auditing tracking tags, debugging redirect chains, spotting duplicate or leaking parameters, and confirming canonical URLs. The rebuilt URL updates as you edit, letting you confirm the components round-trip and that no encoding is lost. Because parsing happens locally with the native URL API and TextEncoder, nothing is fetched or uploaded. You can safely inspect staging links, signed URLs and internal endpoints. When you need to go further, jump to the URL Encoder / Decoder for component encoding or the UTM Campaign Builder to construct tagged links.

Difficulty:
Easy
Typical time:
~30s
Processing:
100% browser processing

Last updated

How to use the url parser

  1. 1

    Paste your URL

    Drop an absolute URL like https://example.com/path?query=1#section into the input. Include a scheme (https://) so it parses as an absolute address.

  2. 2

    Read the breakdown

    Review the components table (protocol, host, port, path, search, hash, origin) and the derived domain, subdomain and TLD.

  3. 3

    Inspect the parameters

    Scan the query-parameter table for each decoded key and value. Spot duplicates, empty values or unexpected tracking tags.

  4. 4

    Confirm the rebuilt URL

    Check the live rebuilt URL to verify the components round-trip cleanly, then copy the JSON or download the breakdown.

What URL Parser includes

  • Full component breakdown

    Scheme, userinfo, hostname, port, pathname, search and hash: every part of the URL laid out in a labelled table using the browser's own WHATWG parser.

  • Decoded query-parameter table

    Each ?key=value pair is listed separately with its value percent-decoded, so tracking tags and encoded arguments become instantly readable.

  • Path segments split out

    The pathname is broken into its individual segments so you can see route structure, slugs and locale prefixes at a glance.

  • Derived domain intelligence

    Origin, registrable domain, subdomain and TLD are computed for you, plus flags for HTTPS and IP-literal hosts.

  • Live rebuilt URL

    The normalised URL is reassembled from the parsed parts as you edit, so you can confirm everything round-trips with no encoding lost.

  • 100% in your browser

    Parsing uses the native URL API locally. No request is made to the address you paste, so staging, signed and internal URLs stay private.

Why use our url parser

Debug links in seconds

Stop squinting at a wall of query string. A structured table shows exactly which parameters are present, duplicated or double-encoded.

Audit tracking and canonicals

See every utm_* and ref parameter decoded, and confirm the origin and path of a canonical or redirect target match what you expect.

Match how machines read URLs

Because it uses the same standard as browsers and Node, the breakdown reflects how your code, server and search crawlers actually interpret the address.

Keep private URLs private

Nothing is fetched or uploaded, so signed download links, staging hosts and internal API URLs never leave your machine.

Built for the way you work

From quick one-off fixes to daily workflows, see how people put this tool to use.

  • Web developer

    Debug a redirect or callback URL

    Paste a long OAuth or redirect URL to read every query parameter and confirm the state, code and redirect_uri values are exactly what you expect.

  • SEO specialist

    Audit tracking parameters and canonicals

    Decode a shared campaign link to check its utm_* tags, and verify a canonical URL's origin and path match the intended page.

  • Data / analytics

    Extract and read query strings

    Turn a captured request URL into a clean key/value table of decoded parameters, ready to reason about or paste into a spec.

  • QA / support

    Compare two links component-by-component

    Parse a working and a broken URL side by side to pinpoint the differing segment, missing parameter or wrong host causing the issue.

Supported formats

Accepts URL and Text, and produces JSON, all processed locally in your browser.

Input formats
  • URL
  • Text
Output formats
  • JSON

Frequently asked questions

Common problems, solved

Hit a snag? Here are quick fixes for the issues people run into most.

  • It says 'that isn't a valid absolute URL'.

    The URL API needs a scheme. Add https:// (or the correct protocol) to the front, bare hosts like example.com/path or protocol-relative //example.com won't parse until you prefix a scheme.

  • A parameter value shows odd characters or spaces.

    That's the decoded value, %20 becomes a space and %2F becomes /. The parser shows the human-readable form. Use the URL Encoder if you need the percent-encoded version back.

  • Two parameters have the same key.

    That's valid. A query string can repeat a key (?id=1&id=2). Every occurrence is listed in order so you can see duplicates, which often cause servers to pick only the first or last value.

  • The domain / subdomain looks wrong for a multi-part TLD.

    Domain detection is a best-effort split on the last two labels, so it can misjudge multi-part suffixes like .co.uk. Trust the hostname field for the exact host. Treat domain/subdomain as a convenience hint.

Get the most out of it

  • Always include the scheme (https://). The parser needs it to treat the input as an absolute URL.

  • Watch for double-encoding: if a decoded value still contains % sequences, the URL was encoded twice.

  • Repeated query keys are shown in order: the server usually keeps only the first or last, so remove accidental duplicates.

  • Use the rebuilt URL to confirm nothing changed after normalisation. The URL API may lowercase the host and drop default ports.

  • For IP-literal or localhost hosts the domain/subdomain fields are skipped by design: rely on the hostname and port instead.

What's new

Recent updates and improvements to the url parser.

  1. Initial release, full WHATWG component breakdown, decoded query-parameter table, path segments, derived domain/subdomain/TLD and a live rebuilt URL.

  2. Added duplicate-parameter detection, HTTPS and IP-literal flags, copy-per-value buttons, JSON export and keyboard shortcuts.

  3. Added shareable links, ready-made example URLs (redirect, tracking, deep link) and clearer errors for protocol-relative and bare-host input.

Your privacy is built in

Every URL you paste is parsed entirely in your browser with the native URL API. No request is ever made to the address and nothing is uploaded, stored or logged. That means you can safely inspect signed download links, staging hosts, internal endpoints and tokens. Close the tab and every trace is gone.

  • Runs in your browser
  • No uploads
  • Nothing stored

Ready to try the url parser?

Free, private and instant. URL Parser runs right in your browser.