TOOL · 03
URL Encoder / Decoder
Encode or decode URL components. Choose between full-URI encoding and single-component encoding.
Input
Output
About URL encoding
URL encoding (percent-encoding) converts special characters into a form safe for transmission in a URL. “Encode component” escapes all reserved characters, while “Encode URI” keeps structural characters intact.
Features
Two modes
Encode a whole URI or a single component — the right escaping for each job.
Instant decode
Turn percent-encoded strings back into readable text in one click.
100% private
Runs entirely in your browser — your URLs never leave the page.
Free forever
No registration, no limits, no watermarks.
How to use
-
1
Paste a URL or text
Drop in a full URL or the single value you need to escape.
-
2
Choose the mode
Encode component for query-parameter values, Encode URI to keep / : ? & intact, or Decode.
-
3
Copy the result
One click copies the encoded or decoded string.
Use cases
Query parameters
Safely embed user input, spaces and non-ASCII characters in query strings.
API requests
Build correct request URLs when parameters contain reserved characters.
Debugging
Decode ugly percent-encoded URLs from logs or analytics into readable form.
Redirect links
Encode a target URL before placing it inside another URL.
Example
q=hello world&lang=中文q=hello%20world&lang=%E4%B8%AD%E6%96%87Encode component escapes & = ? and friends — use it for values. Encode URI keeps the URL structure readable — use it for whole addresses.
FAQ
What is the difference between the two encode modes?
Encode component escapes every reserved character (& = ? / : …) — right for a single parameter value. Encode URI keeps structural characters so a full URL stays valid.
Why does a space become %20 and not +?
Percent-encoding represents a space as %20. The + for spaces comes from form encoding (application/x-www-form-urlencoded), a related but different convention.
Is decoding safe?
Yes — decoding only interprets %XX sequences locally in your browser. Nothing is sent anywhere.