Query String Parser

Written byOleh Soloninupdated 25 September 2026

URL or query string

Result

Parametersq = привет page = 2 utm_source = newsletter
Parameter count3
Base URLhttps://example.com/search

Long tracking URLs, made legible

Split a URL into its query parameters and decode them, so percent-encoded values become readable text.

Marketing and analytics URLs turn into unreadable strings of parameters and percent-codes. Reading them by eye is slow and easy to get wrong.

This splits the query into one parameter per line and decodes each value, so %D0%BF%D1%80%D0%B8%D0%B2%D0%B5%D1%82 comes back as actual words.

How to use

Paste a whole address or just the query string after the question mark.
Read the parameters: encoded values are shown already decoded.
Check the count — a repeated key is counted as many times as it appears.

What an address is made of

An address has fixed separators, and each opens a different part. The key detail sits at the end: everything after the hash stays in the browser and is never sent to the server. That is why the fragment is left out of the parameter list even if it contains an equals sign.

The default example shows why decoding matters: q=%D0%BF%D1%80%D0%B8%D0%B2%D0%B5%D1%82 is simply the Russian word for hello. The percent groups hide that entirely; the parser shows the value straight away.

Every row comes from the parser on this page: three parameters and a base address. An ampersand inside a value is encoded as %26, or the parser, like the server, takes it for the end of the parameter. Only the first = separates name from value: x=a=b parses as name x and value a=b, though writing the second one as %3D is safer.
Part	Separator before it	In the example	Sent to the server
base address	—	https://example.com/search	yes
parameter q	?	привет	yes
parameter page	&	2	yes
parameter utm_source	&	newsletter	yes
fragment	#	none in the example	no

Repeated keys

The same key can appear several times in one address, and that is not an error: it is how multi-select filters are sent. The parser lists every occurrence separately and counts them all.

What the server does with them is up to the server: PHP keeps the last value, many frameworks build a list, a few keep the first. With repeated keys, the answer to "what will the server receive" is in its documentation, not in the address.

Both rows come from the parser on this page. The second shows a repeated key and a fragment that stays out of the parameters.
Address	Parameters	What the parser shows
…/search?q=привет&page=2&utm_source=newsletter	3	three distinct keys
…/?color=red&color=blue#top	2	color = red and color = blue; the #top fragment is not counted

What this calculator shows

Every parameter as a name and decoded value
How many parameters the URL carries
The base URL with the query stripped off

What to keep in mind

Accepts a full URL or a bare query string.
Plus signs are decoded as spaces, following form-encoding conventions.

FAQs

What are utm parameters?

Tags analytics tools read to attribute a visit: source, medium, campaign and so on. They are meant for attribution, though a site can also read them to change what it shows.

Why do URLs contain % followed by numbers?

That is percent-encoding. Characters outside the safe URL set are stored as their byte values in hexadecimal; a character takes one to four bytes in UTF-8 — two for an accented or Cyrillic letter, three for a Chinese one — and each byte becomes its own group, so a word becomes a long run of them.

Can a parameter appear more than once?

Yes, and it is common for multi-select filters. Each occurrence is listed separately here; how a server treats duplicates varies — some keep the last, some build a list.

Is anything after the # included?

No. The fragment is handled by the browser and never sent to the server, so it is excluded from the parameter list.

Why does a plus sometimes turn into a space?

Because in form data sent as application/x-www-form-urlencoded a plus means a space. A literal plus in a parameter value is therefore written %2B — otherwise a phone number with a country code reaches the server with a space where the plus was.

How long can an address be?

The protocols set no limit, but implementations do: older browsers and some servers cut off at around two thousand characters. Anything larger belongs in a POST body rather than the query string.

Worked example

A tracked search link

Input: https://example.com/search?q=%D0%BF%D1%80%D0%B8%D0%B2%D0%B5%D1%82&page=2&utm_source=newsletter

Output: q = привет · page = 2 · utm_source = newsletter

Note: The decoded value shows what was really searched for, which the raw percent-codes completely hide.

Useful links

All tools in Dev Tools

Query String Parser

Result

Related tools

URL Encoder / Decoder

UTM Link Builder

Base64 Encoder / Decoder

HTTP Status Code Lookup

Useful links