About this tool
Encode text so it can travel safely inside a URL, or decode %-sequences back into readable characters. Component mode encodes everything reserved (right for query parameter values); full-URL mode preserves structural characters like :, / and ? so an entire address stays valid.
URLs only permit a limited character set (RFC 3986); everything else — spaces, ampersands in values, non-Latin scripts — must be percent-encoded. Using the wrong mode is the classic bug: encoding a full URL with component rules destroys it, while under-encoding a query value silently truncates it at the first &.
How to use it
- Paste text or an encoded URL.
- Pick Component (for parameter values) or Full URL mode.
- Click Encode or Decode and copy the output.
Frequently asked questions
Why does a space become %20 — and sometimes +?
Percent-encoding represents a space as %20. The + convention comes from the older form-submission format and is only equivalent inside query strings.
When should I use component mode?
Whenever you are inserting a value into a query string or path segment — it encodes &, =, / and ? so they can't be misread as URL structure.
Can double-encoding cause bugs?
Yes. Encoding an already-encoded string turns % into %25, producing %2520 garbage. Decode first if you are unsure.