All tools

URL Encode / Decode

Encode / Decode

Percent-encode and decode URLs

Query parameters with spaces or special characters break links and API calls unless they're percent-encoded first, and this handles both directions: encoding a raw string to make it link-safe, or decoding a percent-encoded string from a browser address bar or server log back into something readable. It uses component-style encoding, the same escaping `encodeURIComponent` does in JavaScript, which is the correct choice for individual query values rather than an entire URL (encoding a whole URL this way will also escape the `://` you actually want to keep). This is a different job from HTML entity encoding, and from URL Parser, which breaks a URL into its structural pieces rather than just encoding or decoding a string.

urlencodedecodepercent

How to use URL Encode / Decode

  • 1.Paste a URL or query string with spaces and special characters, then encode it to make it safe to embed in a link or HTTP request.
  • 2.Decode a percent-encoded string (e.g. from a browser address bar or server log) back into readable text.
  • 3.Use it to debug why a query parameter isn't being read correctly by an API — often caused by double-encoding or missing encoding.

Frequently asked questions

What's the difference between encodeURIComponent and encodeURI?
This tool uses component-style encoding (like encodeURIComponent), which escapes more characters — the right choice for encoding individual query parameter values rather than a full URL.
Why do spaces sometimes become `+` and sometimes `%20`?
`+` is the historical convention for spaces in `application/x-www-form-urlencoded` form data, while `%20` is the standard percent-encoding used everywhere else, including query strings and paths.
Can I encode an entire URL, not just a parameter?
Yes, though be aware that encoding an entire URL with component-style encoding will also escape `://` and other structural characters — for full URLs you typically only want to encode individual parameter values.
Is this the same as HTML entity encoding?
No — HTML entity encoding (e.g. `&`) is different from URL/percent-encoding. Use the HTML Entities tool for that instead.

Use via API, SDK, or MCP

cURL# Free: 1,000 req/day · Pro: 10,000 req/day
curl -X POST https://api.utilix.tech/v1/tools/url-encode \
  -H "Authorization: Bearer utx_live_..." \
  -H "Content-Type: application/json" \
  -d '{"input":"hello world&foo=bar","mode":"encode"}'

Get an API key from your dashboard · Full API docs →

Related tools

Base32 Encode / DecodeEncode and decode Base32 with Standard, Extended Hex, Crockford, and z-base-32 alphabetsEncode / DecodeBase58 / Base62 EncoderEncode and decode text as Base58 (Bitcoin-address style) or Base62 (alphanumeric, URL-safe)Encode / DecodeBase64Encode and decode Base64 stringsEncode / Decode