ToolHarbor
Developer Tools

URL Parser

Parse a URL into protocol, host, path, and params.

Use the tool

Use URL Parser to break a full URL into readable parts before debugging redirects, tracking links, API calls, or routing issues.

Dev Workbench

URL Parser

Parse a URL into protocol, host, path, and params.

Input

Result

Run the tool to see output.
Lines: 0Chars: 0

Why use URL Parser

  • Extract UTM parameters from marketing links before publishing or reporting.
  • Check protocol, hostname, path, query string, and hash fragments in complex URLs.
  • Debug redirect targets, encoded values, and broken route parameters.
  • Share a readable URL breakdown with developers, marketers, or support teams.

About this tool

URL parsing for campaign and routing QA

URL Parser separates a long link into protocol, host, path, query parameters, and fragment. This makes campaign tags, route values, and encoded data easier to inspect.

Find query and UTM issues quickly

Marketing and analytics links often fail because a parameter is missing, duplicated, encoded twice, or attached after the fragment. Parsing exposes those problems before the link goes live.

Check decoded values

After parsing, review decoded parameter names and values carefully. Spaces, ampersands, plus signs, and percent-encoded characters can change how a destination app receives the link.

Example usage

Input

https://example.com/shop?utm_source=newsletter&utm_medium=email#sale

Output

Host: example.com, Path: /shop, utm_source: newsletter, Fragment: sale

Practical guide for URL Parser

Best practices

  • Parse campaign links before publishing ads, emails, and partner URLs.
  • Check whether nested URLs are encoded exactly once.
  • Keep fragments separate from server-side query parameters.

Common mistakes

  • Putting tracking parameters after the # fragment.
  • Double-encoding URLs and creating unreadable parameter values.
  • Assuming every malformed URL is parsed the same way by all browsers.

How this tool works

  1. Step 1

    Open URL Parser and review the default example input.

  2. Step 2

    Paste your own input or upload source data when required.

  3. Step 3

    Run URL Parser to generate output instantly in the browser.

  4. Step 4

    Verify the output using the preview and formatting helpers on the page.

  5. Step 5

    Copy the final result and continue with a related tool if needed.

Use related links to continue your workflow and keep your output consistent across ToolHarbor pages.

URL EncoderEncode URLs and query values safely.URL DecoderDecode URL-encoded text instantly.Query String ParserParse query strings into JSON key-value data.HTTP Header ParserParse raw HTTP headers into structured JSON.URL Slug ValidatorCheck if text is a valid URL slug.

Continue exploring

Previous: HTML Escape / UnescapeNext: URL Slug ValidatorMore in Developer ToolsBrowse all tools

Popular workflows

JSON FormatterMerge PDFCrop Image OnlineTrim VideoCompress VideoMP4 to GIF

FAQ

What parts of a URL can this parser show?

It can show the protocol, hostname, port, path, query string, individual parameters, decoded values, and fragment when those parts are present.

What is the difference between query and fragment?

The query string comes after ? and is sent as part of the URL. The fragment comes after # and is usually handled by the browser or client app.

Can this help with UTM debugging?

Yes. Paste a campaign URL to inspect utm_source, utm_medium, utm_campaign, and other parameters before using the link.

Why do decoded values look different?

URL encoding turns reserved characters into percent-encoded sequences. Decoding makes values readable but can reveal spaces, symbols, or nested URLs.