URL Parser

Paste a link to see exactly how a browser reads it: scheme, user name, host, port, path segments, every query parameter (decoded) and the fragment. The parameters are editable, so you can change a value, remove tracking parameters or add new ones and copy the correctly encoded result.

URL & HTTP Runs in your browser

Parse a URL

JavaScript is required. This tool runs in your browser, so please enable JavaScript to use it. The instructions below are still available.

How to Use the URL Parser

Paste a URL into the box.
Read the components table; percent-encoded values are shown decoded.
Edit, remove or add query parameters in the editor.
Copy the rebuilt URL, which is encoded correctly for you.

About This Tool

Developers debugging redirects and API calls, marketers cleaning up campaign links, and support staff checking what a long, encoded URL really contains.

Input: A URL · Output: URL components and rebuilt URL.

Features and Limitations

Features

Uses the browser's own WHATWG URL parser, the same one that loads pages.
Shows the default port for the scheme when none is given.
Decodes percent-encoding and plus signs in parameter values.
Repeated keys (for example ?tag=a&tag=b) are kept in order.

Limitations

Internationalised domain names are shown in their punycode (xn--) form, as browsers send them.
Relative URLs such as /path?x=1 need a scheme and host; https:// is added only when the input looks like a host name.
The tool does not visit the URL or follow redirects.
Results are computed in your browser; nothing you enter is sent to a server.

Example

In https://shop.example.com:8443/en/products?q=blue%20mug#reviews the host is shop.example.com, the port 8443, the path segments en and products, the parameter q is “blue mug” and the fragment is reviews.

Frequently Asked Questions

What is the difference between host and hostname?

hostname is just the domain or IP address; host also includes the port when one is given, for example shop.example.com:8443.

Is the fragment sent to the server?

No. Everything after # stays in the browser. It is used for in-page anchors and by single-page apps, so servers and analytics on the server side never see it.

Why do spaces appear as %20 or +?

URLs cannot contain raw spaces. In paths they are encoded as %20; in query strings from HTML forms they are often encoded as +. Both decode to a space.

Can I remove tracking parameters with this?

Yes. Remove utm_*, fbclid, gclid or similar rows in the editor and copy the rebuilt URL.