URL Encoder, Decoder & Parser
Percent-encode or decode text for use in URLs, or paste a full URL to see its protocol, host, path, query parameters and fragment. Choose the right kind of encoding for the job: a single component, a whole URL or an HTML form. Everything runs in your browser; the text you enter is never uploaded, opened or fetched.
Result
Query parameters
This URL has no query parameters.
| # | Name | Value (decoded) |
|---|
Examples
How common characters are written in each style:
| Character | URL component | Form data | Whole URL |
|---|---|---|---|
| space | %20 | + | %20 |
& | %26 | %26 | & |
/ | %2F | %2F | / |
é | %C3%A9 | %C3%A9 | %C3%A9 |
€ | %E2%82%AC | %E2%82%AC | %E2%82%AC |
😀 | %F0%9F%98%80 | %F0%9F%98%80 | %F0%9F%98%80 |
Formula & Methodology
Percent-encoding writes each unsafe byte as % followed by two hexadecimal digits. Text is first converted to UTF-8, so é becomes %C3%A9 (two bytes) and an emoji becomes four escapes. Decoding reverses this and rejects sequences that are not valid UTF-8.
Parsing uses the browser’s standard URL parser (the WHATWG URL Standard), so the result matches what a browser would do. The URL is only analysed: it is never fetched or opened.
Notes and limitations
- Use component encoding for one value and whole-URL encoding for a complete address. Encoding a whole URL as a component also escapes its slashes and colons.
- Form data differs from component encoding: a space is +, and a literal + must be %2B. Decode with the “+ is a space” option for query strings from forms.
- Only absolute URLs can be parsed. A bare query string such as a=1&b=2 is not a URL, but you can paste it after a ? to see its parameters.
- Internationalised host names are shown in their ASCII (punycode) form, as a browser would send them.
- Very long inputs (over 1,000,000 characters) are rejected.
How to Use
- Choose Encode, Decode or Parse a URL.
- Type or paste your text. For encoding, pick the style that matches where the text will be used.
- Read the result. In Parse mode you see each part of the URL and a table of its query parameters.
- If the text is invalid, the message gives the position of the first problem.
- Copy the result.
Frequently Asked Questions
Is my text or URL sent anywhere?
No. Encoding, decoding and parsing happen in your browser. The URL is only analysed as text: it is never opened, fetched or sent to ToolQuarter or analytics.
What is the difference between encodeURI and encodeURIComponent?
encodeURIComponent escapes nearly everything, including / ? & = and #, so it is right for a single value. encodeURI keeps those structural characters, so it is right for a whole address. Using the wrong one either breaks the URL or leaves unsafe characters in it.
Why does a + sometimes mean a space?
In HTML form data (the part after ? in many forms) a space is written as +. In other parts of a URL a + is just a plus sign. Turn on “Treat + as a space” when decoding form data.
Why does decoding fail with “not valid UTF-8”?
Percent escapes represent bytes. If the bytes do not form valid UTF-8 text (for example, text that was encoded as Latin-1), they cannot be turned into characters safely, so the tool reports the position instead of guessing.
Can I parse a relative URL?
Only absolute URLs, which start with a scheme such as https://, have all the parts this tool shows. For a relative path, add a scheme and host in front of it.
Last updated: