search

Found

info Overview

Paste any URL to split it into 6 parts: protocol, host, port, path, query parameters and fragment, each color-coded in a copyable table for debugging.

📘 How to Use

  1. Paste the URL you want to inspect into the input field
  2. Read the color-coded components shown for each part
  3. Review the query parameter and fragment breakdown table

URL Parser & Breakdown

Enter a URL to see each part color-coded
Components will be listed when you enter a URL
Copied

grid_view Related

Article

URL Parser & Breakdown | See Protocol, Host and Query at a Glance

Paste any URL and this tool splits it into six parts: protocol, host, port, path, query parameters and fragment. Each piece is color-coded, and the breakdown table can be copied as plain text.

💡 About this tool

When you are debugging an OAuth redirect, a tracking link, or a webhook callback, you usually need to answer one question fast: what exactly is in this URL? Scanning a long string by eye, it is easy to lose track of where the path ends and the query begins, or to miss a parameter buried after the fifth &.

This tool uses the browser's native URL object to parse the string, then lays out every component in order, from the https:// scheme down to the #fragment. Query parameters are expanded one per line as key = value, so even a heavily encoded query string becomes readable at a glance. It also handles URLs with embedded credentials (user:pass@host), showing the username and password in distinct colors so you can immediately spot when a secret is sitting in plain sight inside a link.

Because parsing happens in the browser, you can inspect internal links, signed URLs, or anything carrying an access token and still read its full structure.

🧐 Frequently Asked Questions

Does it accept partial URLs? It relies on the browser's URL constructor, which requires a scheme. A bare example.com will show an error; prefix it with https:// and it parses fine.

Does it reorder query parameters? No. Parameters appear in the exact order they were written. Nothing is sorted or rearranged.

How are repeated keys like ?a=1&a=2 handled? Both appear as separate rows. The tool does not collapse duplicates or keep only the last value, which matters when a server treats repeated keys as an array.

What happens with percent-encoded characters such as %20? Following the URL spec, the hostname is normalized and the path keeps its percent-encoded form, while query parameter values are decoded into readable text — so a value like %20 shows up as a space in the breakdown.

What if the port is omitted? If no explicit port is present, the port row is hidden. It only appears when a port such as :8080 is written in the URL.

📚 Fun Facts About URLs

The formal grammar of a URL is defined in RFC 3986 as scheme://user:password@host:port/path?query#fragment. A neat detail: the fragment after # is never transmitted to the server — it stays in the browser and is used only to point at an anchor on the page. That is exactly why single-page apps lean on hash-based routing: the part after # never triggers a round trip. Omit the port and the browser silently assumes 80 for http and 443 for https. And if you feed it an internationalized domain name, the hostname is quietly converted to Punycode (the xn-- form) under the hood — a handy thing to remember when a hostname looks different from what you typed.