What does it do?
It breaks a URL — no matter how long — into a table of decoded parameters. Tracking links, OAuth redirects and search URLs become readable in a second:
%C3%A9 and + are decoded, so caf%C3%A9+con+leche reads café con leche.- Repeated keys are listed one by one.
- Parameters in the fragment (
#access_token=…) get their own section.
- Values that are JSON, JWT, Base64 or nested URLs (
redirect_uri) are recognised and decoded below the value.
How to use it
- Paste a URL. The scheme is optional:
example.com/?a=1 works too.
- Use the search box to find a parameter among dozens.
- Edit any value: the rebuilt URL appears at the bottom, correctly encoded.
Anatomy of a URL
https://shop.example.com/search?q=coffee&page=2#reviews
└─┬─┘ └──────┬───────┘└──┬──┘└──────┬──────┘└──┬───┘
scheme host path query fragment
Frequently asked questions
›What happens with repeated parameters like tag=a&tag=b?
Each one is shown in its own row, numbered, and kept in the same order when the URL is rebuilt. Many frameworks read them as an array.
›Why are there parameters after the #?
The fragment is never sent to the server, so OAuth implicit flows and single-page apps use it to pass data such as access_token. The tool parses it like a query string.
›Is a + a space?
In the query string, yes: the application/x-www-form-urlencoded format reads + as a space, and that is how browsers and URLSearchParams decode it.