DevToolPal
EN

URL Parser

Break a URL into protocol, host, port, path, query parameters and fragment, decode them, and edit the query to rebuild the URL.

Runs locally, never uploaded

Options

URL

Result

Result appears here

What this tool does

The URL Parser breaks a web address into its components and decodes each one: protocol, username and password, host, port, path, query string and fragment. Query parameters are listed in a table, one row per parameter, with repeated keys kept in order, so a long tracking or API URL becomes readable at a glance.

Internationalized domain names are shown both in their punycode form (as they travel over the network) and decoded to Unicode, and the port line shows the default port of the protocol when the URL does not name one.

How to use it

  1. Paste a URL into the input, or press Sample.
  2. Read the components in the result panel. Each value has a copy button.
  3. Edit, add or remove query parameters in the table. The input updates with the rebuilt URL, ready to copy.

Malformed percent-encoding (for example %zz) does not stop the parser; the raw text is shown and the parameter is marked as badly encoded.

Example

https://user:p%40ss@www.example.com:8080/docs/getting%20started/?q=caf%C3%A9+au+lait&tag=js#install

This URL has the protocol https, user user with password p@ss, host www.example.com, port 8080, the decoded path /docs/getting started/, the parameters q = café au lait and tag = js, and the fragment install.

Tips

  • Use the parser to check redirect and callback URLs: a stray # or an unencoded & inside a value changes where the parameters end.
  • To encode or decode a single value instead of a whole URL, use the URL Encode/Decode tool.
  • Everything runs locally in your browser; URLs containing tokens are not uploaded anywhere.

FAQ

› How does the parser read a URL?

With the same WHATWG URL algorithm your browser uses, so the host, port and path you see are exactly what a browser would request. The query string is additionally split by hand so you see each parameter both raw and decoded.

› Can I paste a URL without https://?

Yes. Inputs such as example.com/page or localhost:3000/api are read as https:// URLs, and the result notes that the protocol was assumed.

› Why does a + become a space?

In HTML form encoding, + stands for a space in the query string. If your server treats + literally, turn off Decode + as space in the options.

› What happens when I edit a parameter?

The query string is rebuilt with proper percent-encoding and written back to the input, so the URL above always matches the table. Removing every parameter removes the ? as well.