Encode or decode URLs, query values, and special characters with a clean button-driven workflow that stays fast on desktop and mobile.
Processed locally in your browser. No data is uploaded.
Mode
Full URL mode keeps structural URL characters intact. Component mode is better for a query value, path segment, or form field.
Examples
URL encoding is the process of turning characters that are unsafe, reserved, or ambiguous inside a URL into percent-encoded text. Instead of sending a raw space, for example, the browser sends %20. This keeps the final URL readable to browsers, servers, and routing layers that expect a strict format.
The same idea applies to Unicode text, punctuation, symbols, and query values. A good URL encoder helps you avoid broken links, malformed redirects, and query strings that stop working because special characters were pasted directly into a URL.
Some characters already have a meaning inside URLs. A question mark starts the query string, an ampersand separates parameters, and an equals sign separates a parameter name from its value. If those characters appear inside user input and are not encoded, the browser may interpret them as structure instead of data.
That is why values such as hello world, name=alex taylor, or a path segment with Unicode text should be encoded before use. Encoding makes sure your data stays data instead of accidentally changing how the URL is parsed.
Full URL mode behaves like encodeURI. It is designed for an entire URL, so characters such as :, /, ?, &, and = stay in place. URL Component mode behaves like encodeURIComponent, which is stricter and better for a single query value or path part.
hello world becomes hello%20world.
& and = should be encoded when they are part of a value, not query structure.
https://example.com/search?q=hello world&lang=en is usually best handled in full URL mode.
Use full URL mode when you are transforming a complete link.
Use component mode for a single value such as a search term, redirect target, or folder name.
If decoding fails, double-check whether the input was encoded as a full URL or as an individual component.
Building query strings
Encode user-entered values before appending them to search URLs or API request links.
Debugging redirects
Decode long redirect URLs or callback values to inspect what a browser or service is really sending.
Working with Unicode text
Safely encode names, non-English words, emoji, and special characters before using them in URLs.
Preparing path segments
Encode a slug, folder name, or file label when only one part of the URL should be transformed.
Reading encoded logs
Decode encoded URLs copied from browser logs, analytics exports, or error reports.
Testing frontend behavior
Quickly compare full URL encoding versus component encoding without leaving the browser.
Encode as late as practical, close to the point where a URL is built. That keeps your app logic easier to debug and reduces the chance of double encoding. When in doubt, treat a complete URL and a single component as different inputs and use the matching mode.
If you are decoding copied data from logs or browser output, avoid editing the string manually before decoding it. A missing percent sign or incomplete hexadecimal pair is enough to make decoding fail. Keeping the original text intact gives you the best chance of a clean result.
URL encoding converts unsafe or reserved characters into percent-encoded values so browsers and servers can read them reliably. For example, a space becomes %20 and other special characters become encoded sequences.
Encode a URL when it contains spaces, Unicode text, query values, or reserved characters that could break routing or query parsing. Encoding keeps the final URL valid and predictable.
encodeURI is for a complete URL and leaves structural characters such as :, /, ?, &, and = in place. encodeURIComponent is for a smaller part of the URL, such as a query value or path segment, and encodes those characters too.
Decoding fails when the input contains malformed percent-encoded sequences such as a stray % sign or incomplete hexadecimal values. It can also fail when the wrong mode is used for the kind of text you pasted.
Yes. All encoding and decoding happens directly in your browser with no backend processing. That makes it suitable for sensitive URLs, query strings, and test data.
No. The tool runs entirely client-side in your browser. Nothing is uploaded, stored, or sent to any server.
