Digite o texto que você deseja codificar ou decodificar:
You have a URL with spaces, special characters, or non-English letters, and it breaks when you paste it into a browser or a piece of code. This URL Encoder / Decoder converts those problematic characters into a format that every web server and browser understands, and it can reverse the process too. It is for web developers handling query parameters, marketers tracking campaign URLs, and anyone who has ever clicked a link that did not work because of a stray symbol or space in the address.
Paste your URL, choose encode or decode, and get back a clean, standards-compliant result instantly. No more broken links from characters that browsers misinterpret.
URLs can only contain a limited set of characters from the ASCII character set. Letters, numbers, and a handful of symbols like hyphens and underscores are always safe. Everything else, including spaces, ampersands, question marks, non-English characters, and even some punctuation marks, must be encoded to work correctly. Encoding replaces each unsafe character with a percent sign followed by two hexadecimal digits that represent the character's code.
Without encoding, a URL containing a space might break in half when pasted into a browser. A URL with an ampersand in a query parameter value might be misinterpreted as a new parameter separator. Decoding is equally important when you need to read or debug a URL that has already been encoded. A string full of percent signs and numbers is hard for a human to parse. Decoding turns it back into readable text. The tool handles both directions so you can work with URLs in whatever form they arrive.
URL encoding converts characters that are not allowed in URLs into a format that is safe for transmission. Each unsafe character is replaced with a percent sign followed by its two-digit hexadecimal ASCII code. For example, a space becomes %20. URL decoding reverses this process by identifying percent-encoded sequences and converting them back to their original characters. The encoding standard is defined in RFC 3986, which specifies which characters are reserved, unreserved, and need to be percent-encoded.
You are building a search feature on your website and the query parameter needs to handle user input like "coffee & tea". If you put that directly into a URL, the ampersand breaks the query string because browsers interpret it as a parameter separator. You paste "coffee & tea" into the encoder. It returns "coffee%20%26%20tea". You use this encoded version in your URL as /search?q=coffee%20%26%20tea. The server receives the correct query, decodes it back to "coffee & tea", and your search works. The user never sees the encoded version. The browser handles it transparently.
URL encoding, also called percent-encoding, converts characters that are not allowed in URLs into a safe format. Each unsafe character is replaced with a percent sign followed by a two-character hexadecimal code. This ensures URLs work across all browsers and servers without misinterpretation.
Spaces, non-ASCII characters like accented letters or symbols from other alphabets, and reserved characters like ampersands, question marks, equals signs, and hash symbols all need encoding when they appear in URL paths or query parameter values. Alphanumeric characters and a few symbols like hyphens, underscores, periods, and tildes are safe and do not need encoding.
These are two JavaScript functions that handle encoding differently. encodeURI encodes a complete URL and leaves characters like slashes, colons, and question marks intact because they are part of the URL structure. encodeURIComponent encodes individual query parameter values more aggressively and will encode those structural characters too. The tool typically performs the equivalent of full URL encoding suitable for any context.
Decode a URL when you have a percent-encoded address and need to read it in plain text. This is common when debugging tracking parameters, analyzing campaign URLs, or inspecting query strings from server logs. Decoding turns strings like "hello%20world" back into "hello world".
No. An encoded URL functions identically to the original. The browser and server automatically handle the encoding and decoding. You just need to make sure the URL is properly encoded before using it in HTML, JavaScript, or any context where unencoded characters could break the syntax.
You can, but it will produce incorrect results. Double-encoding turns a space into %2520 instead of %20 because the percent sign itself gets encoded. If you are unsure whether a URL is already encoded, decode it first. If it does not change, it was in plain text and ready to encode. If it becomes more readable, it was encoded and you have now decoded it.
