Skip to content

URL Parser

Break any URL into its parts (scheme, host, port, path segments, query parameters and fragment), edit the query parameters in a table, and get a correctly encoded URL back. Handy for debugging links, tracking parameters and API calls.

Runs in your browserFreeNo sign-up

Processed on your device. Files and text stay in your browser and are not uploaded to our servers. How privacy works

How to use the url parser

  1. Paste a URL. Everything is parsed instantly using the browser's own URL parser.
  2. Read the components table and the path segments; copy any part with its button.
  3. Edit, add or remove query parameters. Values are shown decoded so you can read them.
  4. Copy the rebuilt URL, or the percent-encoded version when you need to nest it inside another URL.

Features

  • Parses scheme, credentials, hostname, port, origin, path, query and fragment with the standard WHATWG URL parser
  • Query parameters as an editable table, including repeated keys
  • Path segments decoded individually
  • Rebuilt URL with correct percent-encoding, plus an encoded copy for embedding
  • Shows punycode for internationalised domain names

Anatomy of a URL

https://user@www.example.com:8443/shop/items/42?colour=blue#reviews reads as: scheme https, optional userinfo, host www.example.com, port 8443, path /shop/items/42, query colour=blue, and fragment reviews. The fragment is never sent to the server; browsers keep it for in-page navigation and client-side routing.

Query strings are key=value pairs joined by &. The same key can appear more than once; how that is interpreted depends on the application. Special characters are percent-encoded (%20 for a space in paths, + or %20 in query strings), which is why a URL copied from a browser may look different from what you typed.

Frequently asked questions

Why did the tool change my URL slightly?

The rebuilt URL is normalised: the hostname is lower-cased, default ports are dropped, an empty path becomes /, and characters are consistently percent-encoded. Browsers do exactly the same before sending a request.

Why is the password hidden?

Credentials in URLs are a bad idea and are logged in surprising places. The tool masks the password field and never includes it in the copy buttons.

Does it handle URLs without https://?

Yes. Input without a scheme is treated as https://, so example.com/page parses as expected. Other schemes such as mailto: or ftp: parse but have no host or query in the same sense.

Other tools people use alongside URL Parser.

You might also like

Something useful from another corner of VoltKit.