Skip to content
Allin

URL parser

Break a URL into protocol, host, port, path, query and parameters — percent-encoding decoded, repeated keys kept. Plain text or JSON.

Open URL parser and you get an answer straight away, with no account to create. You will find it under Web & network, with Key-value to JSON parser and URL encoder / decoder for the neighbouring cases.

How to use it

  1. Open the tool — no signup or install needed.
  2. Enter your input or adjust the available options.
  3. Get your result instantly, then copy or download it.

Frequently asked questions

What does URL parser do?

Break a URL into protocol, host, port, path, query and parameters — percent-encoding decoded, repeated keys kept. Plain text or JSON.

When would I actually use this?

Getting usable data out of something that was never meant to be parsed: pulling every address out of a pasted thread, turning a column of lines into a JSON array or an SQL IN clause, renaming a hundred identifiers from snake_case to camelCase in one pass.

What is the most common mistake?

Trusting an extraction to be exhaustive. A pattern that catches every address in the sample will still miss the one wrapped across a line break, the one written with a display name, and the one an email client turned into a link — count what came out against what you expected before you use the list.

How is URL parser different from Key-value to JSON parser?

They sit next to each other but answer different questions: Key-value to JSON parser is the one to open when you need it to parse 'key: value' or 'key = value' lines into a JSON object. Works on a pasted block or on a file you drop in. Pick whichever matches what you're starting from — both are free.

Is there a tool for the next step?

URL encoder / decoder is the closest one after this: Encode and decode URLs and query parameters.

Where do the figures come from?

Extraction runs on patterns, not on a parser: it recognises the common shapes of an address, a URL or an IP rather than validating them against their specification. That is the right trade for a paste, and the wrong one for input you are about to store.

Further reading

All guides
GuideHTTP Status Codes Explained: The Ones That Actually Get Confused301 against 308, 302 against 307, 401 against 403, 404 against 410 — plus what Retry-After on a 429 or a 503 actually promises. The pairs where picking the wrong code changes behaviour, not just wording.ExplainerSemicolon, Tab, Pipe: Choosing a Delimiter That Survives the TripWhy the reader's language decides the delimiter, what the converter does to the quoting when you switch, what the sep= first line really is, and the count of quoted cells on the same export written five ways.GuideURL Encoding Explained: Percent-Encoding and Where It BitesPercent-encoding is decided per URL component, which is the whole source of the confusion. A slash is legal in a path and must be escaped in a query value; a space is %20 in a path and may be + in a form body. Here are the exact RFC 3986 sets, the three JavaScript functions that disagree, and the traps.ComparisoncamelCase, snake_case, kebab-case: Which One, and Why You Rarely Get to ChooseThe conventions are not taste. A hyphen is the minus operator, so kebab-case cannot be an identifier in most languages - which is exactly why CSS and URLs use it. Plus the acronym round-trip that silently corrupts names, and the rule that fixes it.ExplainerBig O Notation for Beginners: O(1), O(n), O(n squared), and O(log n) ExplainedBig O describes how an algorithm's work grows as input grows. Here is what O(1), O(n), O(n squared), and O(log n) mean and why the difference matters.ExplainerWhat Is UTF-8 and Unicode? Code Points, Byte Encoding, and Why UTF-8 WonUnicode assigns every character a code point; UTF-8 encodes those code points in one to four bytes. Here is how it works and why it beat the alternatives.