🔗 URL Encoder & Decoder
Encode and decode URLs, query strings, and URI components. Parse URL parameters instantly.
Last updated: November 8, 2026 · By the BoltQuickTools team
Make text safe for a URL, or read a URL that has been encoded
A search term with an ampersand breaks a link, a redirect parameter arrives as a wall of percent signs, or a log shows a query string you need to read. This page handles those three jobs: percent-encoding text, decoding it, and splitting a URL into parts.
The three tabs
- Encode percent-encodes everything in Input except letters, digits and
- _ . ! ~ * ' ( ). - Decode turns percent sequences back into text.
- Parse URL lists the protocol, host, hostname, port, path and hash, then every query parameter.
Choose a tab, paste into Input, and the conversion runs automatically on paste. If you type instead, press Convert. Switching tabs does not rerun anything, so press Convert after changing tab. Copy Output copies the Output box and Clear empties the input and the result.
Examples
Encoding price=10€ & tax/fee? gives:
price%3D10%E2%82%AC%20%26%20tax%2Ffee%3F
The euro sign becomes three bytes because encoding goes through UTF-8. Decoding caf%C3%A9%20au+lait gives café au+lait.
Parsing https://user:[email protected]:8443/search?q=red+shoes&size=9&size=10#top lists:
| Field | Value |
|---|---|
| Protocol | https: |
| Host | shop.example.com:8443 |
| Hostname | shop.example.com |
| Port | 8443 |
| Path | /search |
| Hash | #top |
| q | red shoes |
| size | 9 |
| size | 10 |
The summary reports 3 query parameters. The username and password in the URL are not listed.
Mistakes this tool will not catch for you
- Encode treats a full URL as plain text.
https://example.com/a b?x=1becomeshttps%3A%2F%2Fexample.com%2Fa%20b%3Fx%3D1, which no longer works as a link. That output is right when the URL is a value inside another URL, as with a redirect parameter. Otherwise encode only the part that needs it. - Plus signs depend on the tab. Decode leaves
+alone, as in the example above, while Parse URL treats it as a space in query values, because that is the form-encoding rule. If Decode shows plus signs where you expected spaces, your text was form-encoded. - A stray percent sign is an error. Decoding
100%shows an error, worded "Error: URI malformed" in Chrome. The whole input fails, not only that character. Encode the percent sign as%25first. - Parse URL needs a scheme.
example.com/xis rejected. The message says to start with http:// or https://, but other schemes such asmailto:are accepted too. - Copy Output does not copy Parse URL results. That tab hides the Output box, and the button only reads that box. It copies an earlier result if one is there. Select the parsed rows by hand instead.
- No partial encoding. There is no option to keep slashes or other characters. Encoding is always all or nothing.
URL encoding questions
Why is a space %20 here and + somewhere else?
Both are in use. %20 works anywhere in a URL. A plus sign means a space only in form-style query strings, and that is what browsers produce when submitting forms. This page's Encode tab always writes %20, and the query string builder writes +.
Is encoding the same as hiding the data?
No. Anyone can reverse it. It also differs from Base64, which represents binary data as text. Neither one protects a value.
Can I build a request with these values?
The API tester sends requests from your browser, and the HTTP methods reference explains which method suits a given request.