URL Parser

Break any URL down into its protocol, host, port, path, query parameters, and hash — entirely client-side.

Utilities

How it works

A browser-based tool to parse a URL into its protocol, host, path, query, and fragment components.

All calculations and formatting functions are performed directly in your local browser using standard JavaScript runtimes. Your input is not sent to our servers or stored on remote databases. Like the rest of developerOS, this page counts visits with Google Analytics and Vercel Analytics; they see the page you opened, never what you type into the tool. Privacy policy

Related tools

Regex Tester & Matcher

Test your regular expressions against sample texts with match highlighting, capture group indicators, and flags.

Open tool

Query String Parser & Builder

Parse a URL query string into key-value pairs, or build one from scratch with proper URL encoding.

Open tool

Text & Code Diff Viewer

Compare two text or code snippets side-by-side or unified with additions, deletions, and line-by-line diff highlighting.

Open tool

About the URL Parser

Paste a URL and see it split into protocol, username, password, host name, port, path, query string, hash and origin, with the query parameters listed one by one. Parsing uses the same URL standard that browsers implement.

Internationalised host names are shown in their ASCII (punycode) form and paths are percent-encoded, which is how a browser would send them.

How to use it

Paste an absolute URL, including its scheme such as https://, or press Sample URL.
Read each component and the list of query parameters.
Press Copy Output to take the parsed result.

Worked example

Each component is shown in its own row.

Input

https://user:pw@example.com:8080/a/b?x=1&y=2#top

Result

protocol https:
username user
password pw
hostname example.com
port 8080
pathname /a/b
search ?x=1&y=2
hash #top
query x=1, y=2

Common mistakes and gotchas

The URL needs a scheme. example.com/path and //example.com are not absolute URLs, so the parser reports an invalid URL; add https://.
Credentials in a URL (user:pw@) are shown in plain text. Avoid pasting URLs containing real passwords or tokens into any tool.
The default port for a scheme (443 for https, 80 for http) is omitted by the standard, so port is empty unless the URL names a different one.
The hash never reaches the server: browsers keep the fragment to themselves.

Frequently asked questions

Is the URL requested or visited?

No. It is only parsed as text; nothing is fetched.

Why is my host name shown as xn--...?

That is the punycode form of an internationalised domain, the ASCII representation DNS uses.

Can it read relative URLs?

No. Give it an absolute URL with a scheme.

Related tools

Browse all 26 Toolkit tools

How it works

A browser-based tool to parse a URL into its protocol, host, path, query, and fragment components.

About the URL Parser

Internationalised host names are shown in their ASCII (punycode) form and paths are percent-encoded, which is how a browser would send them.

Common mistakes and gotchas

The URL needs a scheme. example.com/path and //example.com are not absolute URLs, so the parser reports an invalid URL; add https://.

Credentials in a URL (user:pw@) are shown in plain text. Avoid pasting URLs containing real passwords or tokens into any tool.

The default port for a scheme (443 for https, 80 for http) is omitted by the standard, so port is empty unless the URL names a different one.

The hash never reaches the server: browsers keep the fragment to themselves.