URL Parser and Query String Editor
Paste any URL to see its scheme, host, port, path, query parameters and fragment, with every percent code decoded. Edit the parameters in a table and copy the rebuilt link, with each value encoded once. It runs in your browser and nothing is uploaded.
1 thing to check
- A plus sign in the query is read as a space, as HTML forms do. If a plus should stay a plus, as in Base64 data, it has to be written as %2B.
- Scheme
- https
- Host
- example.com
- Path
- /shop/red%20shoes
- Decoded
- /shop/red shoes
- Fragment
- reviews
- =
- =
- =
- =
Values are shown decoded, with a plus sign read as a space as a form would read it. Edit them as plain text, and the rebuilt URL encodes each value once.
https://example.com/shop/red%20shoes?q=cats%20%26%20dogs&sort=price&bin=E%2BAXQB&utm_source=news%20letter#reviews
Related Tools
[5 suggestions]URL Encoder / Decoder
Encode URI components or decode percent-encoded URLs safely and reliably.
Developer & WebUTM Link Builder
Live-generate URL tracking links with campaign source, medium, name, content, and term parameters.
SEO & MarketingBase64 Encoder / Decoder
Easily encode plain text to Base64 format or decode Base64 back to readable text.
Developer & WebRedirect Rule Generator
Generate 301 and 302 redirect syntax for Apache .htaccess, NGINX, Next.js, and Cloudflare/Netlify.
SEO & MarketingHyperlink Generator
Make a hyperlink as HTML, Markdown and BBCode, build mailto links, add new tab and rel options, or convert a list of URLs.
Developer & WebAbout the URL Parser and Query String Editor
A URL has a scheme, an optional username and password, a host, an optional port, a path, a query string and a fragment. This tool uses your browser's own URL parser for the split, so it agrees with how the browser reads the link, and then it decodes the path segments and the query parameters for reading. The query is read the way HTML forms and URLSearchParams read it, where a plus sign means a space, and a value written as %2B stays a plus. That difference is why the tool warns when a plus sign appears in the query: a Base64 value in a link, for example, is corrupted when its plus signs are read as spaces. It also warns about double encoding, where a percent sign was itself encoded as %25, about a lone percent sign that breaks decoding, about spaces, about a username or password inside the link, about http links, about repeated parameters and about punycode hosts that start with xn--. When you edit a parameter you type the plain value, and the rebuilt URL encodes it once with percent-encoding, using %20 for a space or, if you choose, a plus. The path and fragment are kept as they were. If you paste a link without a scheme, the tool assumes https and says so. Links such as mailto: that have no host are not supported. Nothing you paste leaves your browser.
Why does the tool show a plus sign as a space?▾
In a query string, HTML forms and URLSearchParams read a plus sign as a space. If the plus is meant literally, as in Base64 data, it has to be written as %2B. The tool warns whenever a plus appears in the query.
What is double encoding?▾
It happens when a value is encoded twice. The first pass turns a space into %20, and the second turns the percent sign into %25, giving %2520. Decode once and check whether the result still holds percent codes.
Does editing a parameter encode it correctly?▾
Yes. You type the plain value, such as cats & dogs, and the rebuilt URL writes it once as cats%20%26%20dogs. The keys are encoded the same way.
Does it work with URLs that have no https at the start?▾
Yes. A link such as example.com/page?x=1 is read as https and the tool says so. Links without a host, such as mailto: addresses, are not supported.