N
NJHTools

URL Parser

Paste a URL to split it into protocol, host, port, path, query string and hash, with every query parameter decoded in an editable table. Change, add or remove parameters and the URL is rebuilt instantly, using your browser's own URL parser.

Examples:

URL components

Protocol
https:
Username
user
Password
••••
Hostname
shop.example.com
Port
8443(default for https: is 443)
Host
shop.example.com:8443
Origin
https://shop.example.com:8443
Pathname
/en/products/blue shoes
Search
?size=42&color=navy&tag=sale&tag=new
Hash
#reviews
Full URL (href)
https://user:p@ss@shop.example.com:8443/en/products/blue shoes?size=42&color=navy&tag=sale&tag=new#reviews

Path segments (3)

  1. 1en
  2. 2products
  3. 3blue shoes

Query parameters (4)

Values are shown decoded. Edit them and the URL above is rebuilt and re-encoded live.

How to parse a URL

  1. Paste a URL. Paste any absolute URL, or click an example. If you forget the https:// prefix, the parser offers to add it for you.
  2. Read the components. See the protocol, username, password (masked), hostname, port, origin, pathname, query string and hash, each with a copy button. Toggle decoding to turn %20 back into spaces.
  3. Edit query parameters. Change a parameter name or value, remove one with ×, or add a new one. The URL is rebuilt and re-encoded as you type.
  4. Parse many at once. Switch to Batch, paste one URL per line, and copy or download the results as CSV.

Percent-encoding in URLs

URLs may only contain a limited set of ASCII characters, so anything else is percent-encoded as UTF-8 bytes: a space becomes %20, é becomes %C3%A9, and a literal & inside a value must be %26 so it is not read as a parameter separator. In query strings a + also means a space, which is why this tool writes spaces in rebuilt query strings as +.

To encode a single value yourself use encodeURIComponent(); use encodeURI() only for a whole URL, because it leaves ? & = / untouched.

Common URL mistakes

  • No scheme. example.com/page is a relative path, not a URL, and localhost:3000is read as a scheme called "localhost". Always start with https:// or http://.
  • Repeated keys. ?tag=a&tag=b is valid and common; servers differ in whether they keep the first, the last or all values.
  • Unencoded # or ?. A # in a value cuts off the rest of the URL as a fragment. Encode it as %23.

Related tools

Frequently Asked Questions

What are the parts of a URL?↓

In https://user:pass@shop.example.com:8443/en/shoes?size=42#reviews, the scheme is https, the credentials are user:pass, the hostname is shop.example.com, the port is 8443, the path is /en/shoes, the query string is ?size=42 and the fragment (hash) is #reviews. The origin is the scheme, host and port together: https://shop.example.com:8443.

What is the difference between host and hostname?↓

hostname is the domain or IP address only (example.com), while host also includes the port when one is written in the URL (example.com:8080). When the URL uses the scheme's default port, such as 443 for https, the port is empty and host equals hostname.

How do I get query parameters from a URL in JavaScript?↓

Use new URL(href).searchParams. For example, new URL("https://a.com/?q=shoes&page=2").searchParams.get("page") returns "2", and getAll("tag") returns every value of a repeated key. URLSearchParams decodes percent-encoding and turns + into a space for you.

Why does my URL show xn-- in the domain?↓

Domain names can only contain ASCII, so internationalized domains (IDNs) are converted to punycode with an xn-- prefix. 한국.kr becomes xn--3e0b707e.kr and bücher.example becomes xn--bcher-kva.example. The parser shows both forms; browsers display the Unicode form unless it could be used for look-alike spoofing.

Is the hash (#fragment) sent to the server?↓

No. Everything after # stays in the browser: it is used to scroll to an element or by single-page apps for routing, and it never appears in server logs or the HTTP request. Data that the server needs must go in the path or the query string.

Is it safe to paste URLs that contain passwords or tokens?↓

Yes. Parsing uses your browser's built-in URL API and nothing is sent anywhere. The password field is masked by default. Still, avoid putting credentials in URLs in real use, because they end up in browser history, logs and Referer headers.

All Text & Dev Tools →

Last updated: