URL Encode / Decode
Last updated:
Jsonic's URL Encode tool applies percent-encoding to strings, converting special characters like spaces (%20), ampersands (%26), and slashes (%2F) so they can be safely used in URL query parameters or form data. The Decode button reverses the operation. This tool uses encodeURIComponent semantics, suitable for individual parameter values.
How to URL encode or decode a string
- Select Encode or Decode mode.
- Paste your text into the left panel.
- Click Encode or Decode.
- Use Swap to reverse the operation.
- Click Copy to copy the result.
FAQ
What is percent-encoding?
Percent-encoding (also called URL encoding) replaces special characters with a % followed by two hex digits. For example, a space becomes %20 and & becomes %26.
When should I encode a URL?
Encode individual query parameter values before assembling a URL. Do not encode an entire URL at once — that would encode the : and / characters in the scheme and path.
What is the difference between encodeURI and encodeURIComponent?
encodeURI leaves characters like / : ? # intact (safe for encoding a full URL). encodeURIComponent encodes everything except letters, digits, and - _ . ~ — safe for encoding individual parameter values. This tool uses encodeURIComponent behavior.
Is my data sent to a server?
No. Encoding and decoding run entirely in your browser.
Does this support Unicode characters?
Yes. Non-ASCII characters (like Chinese, emoji, or accented letters) are first encoded as UTF-8 bytes, then percent-encoded.
What does + mean in a URL?
In application/x-www-form-urlencoded encoding (HTML forms), + represents a space. In standard percent-encoding (RFC 3986), + is a literal plus sign. This tool uses RFC 3986 — spaces become %20, not +.
Can I decode a full URL at once?
Yes. Paste the full URL and click Decode. It will decode all percent-encoded sequences. Note that some characters like %2F (/) may change the apparent path structure.