Encode URLs for safe transmission or decode encoded URLs back to readable text.
URL encoding converts characters that are not allowed in URLs into a format that can be transmitted. For example, a space becomes %20.
When passing data in query strings, when including special characters in URLs, or when working with APIs that require encoded parameters.
encodeURIComponent encodes all special characters including /, ?, # and &. Use it for individual parameter values. encodeURI only encodes characters not allowed in a full URL.
A URL encoder converts text into a format that's safe to use in a web address. URLs can only contain certain characters, so spaces, accented letters, and symbols like &, ?, and = must be converted into a special percent-encoded form (for example, a space becomes %20). A URL decoder reverses this, turning encoded strings back into readable text. This is essential whenever data is passed through a URL, such as in query strings and search parameters.
If you've ever seen a web address full of %20 and %3A, that's percent-encoding at work. It exists because URLs have a limited set of allowed characters, and anything outside that set must be encoded to avoid breaking the link or being misinterpreted. The ConvertDox URL tool encodes and decodes strings in your browser, handling both full URLs and individual components like query parameters. Nothing is uploaded — your data stays on your device.
Encode values like search terms or names so they pass safely in a URL's query parameters.
Decode a percent-encoded URL to read what it actually contains when troubleshooting.
Encode parameters correctly when constructing API request URLs by hand.
Encode URLs containing spaces or symbols so they work when pasted or shared.
Understand how form values are encoded when submitted through a URL.
Encode campaign or tracking values added to marketing URLs.
Yes, completely free with no signup and no usage limits.
URL encoding (percent-encoding) converts characters that aren't allowed in URLs into a safe format, like turning a space into %20, so data passes through web addresses correctly.
Whenever you put text containing spaces, symbols, or non-English characters into a URL — especially in query parameters — encoding prevents the link from breaking.
No. Encoding and decoding happen entirely in your browser. Your data is never sent to or stored on any server.
Both represent a space. The + form is used in form submissions (application/x-www-form-urlencoded), while %20 is used in the path and elsewhere. Both are valid in their contexts.
Double-encoding happens when you encode text that's already encoded, turning %20 into %2520. If your decoded result still looks encoded, decode it again.