Skip to content
Shrake DevTools
  • JSON FormatterData & Format
  • JSON ValidatorData & Format
  • JSON MinifierData & Format
  • JSON ↔ YAML ConverterData & Format
  • XML FormatterData & Format
  • Base64 Encoder / DecoderData & Format
  • URL Encoder / DecoderData & Format
  • JWT InspectorData & Format
↑ ↓ to navigate↵ to openEsc to close

URL Parser

Runs locally in your browser. Your input is not uploaded.Free, no sign-up

Break a URL into protocol, credentials, host, port, path, query and fragment.

How to use the URL Parser

  1. Paste a URL, or click Sample.
  2. Read each part, decoded: host, port, path segments, query parameters and fragment.
  3. Check the notes for things like embedded credentials or repeated parameters, and copy any part you need.

The parts of a URL

https://user:pass@shop.example.com:8443/api/orders?status=paid#results

  • Protocol (scheme): https:
  • Credentials: user:pass, best avoided
  • Host and port: shop.example.com, 8443 (443 if left out for https)
  • Path: /api/orders
  • Query: ?status=paid, sent to the server
  • Fragment: #results, stays in the browser and is never sent to the server

Frequently asked questions

Which parser is used?

Your browser's own URL parser (the WHATWG URL Standard), so the result matches what fetch, links and JavaScript's new URL() see. Java's java.net.URI is stricter and may reject some URLs this accepts.

Why is the host shown as xn--…?

Domains with non-ASCII letters (like bücher.de) are sent as punycode (xn--bcher-kva.de). The tool shows the form that goes over the network.