URL encode and decode
Percent-encode or decode text, pick between component and full-URL mode, and edit the query parameters of a URL in a table.
Your data never leaves your browser
Paste API responses and tokens safely: nothing is sent anywhere.
Use “Component” for a value inside a URL (it also encodes / ? & =). Use “Full URL” to keep the address structure.
Input
Output
Next, try one of these tools
How to use
- 1Choose Encode, Decode or the URL parser.
- 2Paste your text or URL and pick the right mode.
- 3In the parser, edit the parameters in the table and watch the URL rebuild.
- 4Copy the result.
Common uses
Building a query string
Encode a search phrase or a redirect address before adding it to a link.
Reading a long URL
Decode an address full of %XX escapes to see the real Arabic path or parameters.
Editing tracking parameters
Open a URL in the parser, remove the tracking parameters and copy the clean link.
Debugging redirects
Check whether a value was encoded once, twice or not at all.
Tips and limits
- Encode each value separately, then join them with & and =. Encoding a whole query string with Component mode also escapes the & and = signs.
- Double encoding (%2520 instead of %20) is a classic bug. If decoding once still leaves % signs, decode again.
- A plus sign means a space only in form-style query strings. In a path it is a literal plus.
- Arabic letters are encoded as UTF-8 bytes, so one letter becomes two escapes, like %D9%85.
Percent-encode, decode and take a URL apart
URLs can only carry a limited set of characters, so spaces, symbols and non-English letters are written as percent escapes such as %20 or %D9%85. This tool encodes and decodes them in two modes. “Component” (encodeURIComponent) escapes everything that has a special meaning in a URL, which is right for a single query value. “Full URL” (encodeURI) keeps the address structure such as :, /, ? and &, which is right for a whole link. Decoding reports exactly where a malformed escape is instead of failing silently, and can treat + as a space for form data.
The URL parser splits a link into protocol, host, port, path, query parameters and hash. Edit the parameters in a table, add or remove rows, and the URL is rebuilt with correct encoding, which makes it easy to adjust Arabic paths and query values. Encoded values often show up inside other formats: decode a token body with Base64 or the JWT decoder, read an API response with the JSON formatter, and see how a JWT travels in headers in what a JWT is.
Step-by-step guides
Frequently asked questions
What is URL encoding?
It replaces unsafe characters in a URL with a percent sign and two hexadecimal digits, so the address stays valid.
What is the difference between encodeURI and encodeURIComponent?
encodeURI keeps characters that structure a URL, such as / ? & =. encodeURIComponent escapes them too, so use it for a single value.
How do I decode a URL?
Choose Decode, paste the text and pick the matching mode. If an escape is malformed, the tool shows where.
Does it work with Arabic URLs?
Yes. Arabic paths and query values are encoded and decoded as UTF-8 and shown readably in the parser.
Does my text leave the browser?
No. Encoding, decoding and parsing all run locally in your browser.