Developer Tools
URL Encoder / Decoder
URL Encoder / Decoder is part of Toolspire and is ready as soon as this page loads. Percent-encode text for a URL or decode %-escaped links back into readable text — as you type. Pick the right encoding for a parameter, a whole URL or form data, and edit query parameters in a table.
On this page
What you can do here
Live, both ways
Results update as you type. Switch between Encode and Decode and the result carries over.
Right encoding, explained
Each mode says when to use it, so a URL doesn’t break because its slashes or ampersands were encoded.
Clear errors
Instead of “URIError: malformed URI”, see which character is wrong and why.
Query parameter editor
Read long tracking URLs at a glance, fix a value, remove a parameter, and get a correctly encoded URL back.
Batch mode
Turn on Each line separately to encode or decode a whole list of values or URLs at once.
Private
URLs with tokens or personal data stay on this device.
The sequence
How to encode or decode a URL
- 1
Choose Encode or Decode
Pick Encode to make text safe for a URL, or Decode to read an encoded link.
- 2
Pick what you’re encoding
Use Parameter value for a single value, Whole URL for a complete link, or Form data for form posts.
- 3
Paste your text
The result appears as you type. Problems are pointed out with the exact character.
- 4
Copy or edit
Copy the result, or edit the query parameters in the URL parts table and copy the updated URL.
Worth knowing
- URL Encoder / Decoder on Toolspire: three encodings for three jobs: parameter value (encodeURIComponent), whole URL (encodeURI) and form data (application/x-www-form-urlencoded, spaces as +).
- Encodes text as UTF-8, so Hindi, other Indian scripts, ₹ and emoji become the %E0%A4… sequences every browser and server understands.
- The decoder turns %20 and + back into spaces and shows exactly where an invalid sequence like “50%off” or broken UTF-8 is.
- Spots double encoding (%2520) and decodes again with one click.
- Paste a full URL to see its host, path, fragment and every query parameter decoded in a table — edit, add or remove parameters and copy the updated URL.
- Optional strict RFC 3986 mode and line-by-line conversion. Everything runs in this tab.
Which encoding should I use?
| You have | Use | Example |
|---|---|---|
| A value for ?q= or a path segment | Parameter value | chai & samosa → chai%20%26%20samosa |
| A complete URL with spaces or Hindi | Whole URL | https://x.in/a b → https://x.in/a%20b |
| Data for an HTML form or POST body | Form data | chai & samosa → chai+%26+samosa |
Common percent-encodings
| Character | Encoded | Character | Encoded |
|---|---|---|---|
| space | %20 (or + in forms) | & | %26 |
| / | %2F | = | %3D |
| ? | %3F | # | %23 |
| % | %25 | + | %2B |
| @ | %40 | ₹ | %E2%82%B9 |
FAQ
Questions about URL Encoder / Decoder
Where does URL Encoder / Decoder run?
What is URL encoding?
Should a space be %20 or +?
What’s the difference between encodeURI and encodeURIComponent?
Why does decoding fail with “malformed URI”?
What is double encoding?
Is my URL sent anywhere?
Keep going
Related tools
Last updated Report a problem or suggest a feature