ToolsOx

Encode or Decode URLs and Query Parameters with Percent Encoding

Encode URLs and query strings with percent encoding, or decode encoded URLs back to readable text. Handles spaces, special characters, Unicode, and reserved ...

URLs can only contain a limited set of ASCII characters. When you need to include spaces, special symbols, or non-English text in a URL — whether in a query parameter, a path segment, or a fragment identifier — those characters must be percent-encoded. This tool handles that encoding for you, converting problematic characters into their %XX format, and can also decode percent-encoded URLs back to their original form. If you have ever seen '%20' in a URL and wondered what it meant, this is the tool that explains it and lets you convert between formats instantly.

Common Characters and Their Encoded Forms
Here is a quick reference for the characters most frequently needing URL encoding. Bookmark this if you work with URLs regularly — it will save you from guessing.
SpaceEncoded as %20 — the most common encoding. Some systems use + instead of %20 in query strings, but %20 is the correct universal form.
& (Ampersand)Encoded as %26 — critical in query strings because & separates parameters. An unencoded & in a parameter value will split the parameter in two.
= (Equals)Encoded as %3D — separates parameter names from values in query strings. An unencoded = in a value will confuse the parser.
# (Hash)Encoded as %23 — marks the beginning of a URL fragment. An unencoded # will truncate the URL at that point.
? (Question mark)Encoded as %3F — marks the beginning of the query string. Must be encoded when it appears inside parameter values.
/ (Forward slash)Encoded as %2F — separates path segments. Must be encoded in query parameters to avoid being interpreted as a path separator.
URL Encoding Mistakes That Break APIs and Links
URL encoding seems straightforward, but getting it wrong can cause broken links, failed API calls, and security vulnerabilities. These are the mistakes we see most often.

Double encoding

If you encode a URL that is already encoded, the % signs themselves get encoded (becoming %25), producing garbage. Always check whether your input is already encoded before encoding it. This tool's Decode mode lets you check.

Forgetting to encode query parameter values

The parameter name and the = and & delimiters should NOT be encoded, but the values between them often MUST be. For example, in 'search=hello world', the space must become %20: 'search=hello%20world'.

Not handling Unicode properly

Characters like é, ñ, ü, or Chinese characters are encoded as sequences of percent-encoded bytes representing their UTF-8 form. For example, é becomes %C3%A9. This tool handles UTF-8 encoding correctly.

URL Encoding Questions

Related Search Terms
url encoderurl decoder onlinepercent encoding toolurl encoding decoderencode url parametersfree url encoder decoder online no signuphow to encode url parameters with special charactersurl encode space character percent encodingdecode percent encoded url stringurl encoding for API query parameters