What is URL encoding?
URLs can only be transmitted securely over the internet using a limited set of ASCII characters. When a URL contains spaces, emojis, or reserved characters (like `?`, `&`, or `=`), they must be converted into a valid format using **percent encoding**. This process replaces unsafe characters with a `%` followed by two hexadecimal digits.
What is URL decoding?
URL decoding is the reverse process. If you have ever copied a messy web link filled with `%20` or `%2F`, URL decoding converts those percent-encoded values back into their original, human-readable characters.
URL encoding vs URL decoding
Encoding converts special characters into a safe format for web transmission (e.g., converting a space to `%20`). Decoding restores the percent-encoded string back to its original state (e.g., converting `%20` back into a space).
URL component encoding vs full URL encoding
Our tool offers two distinct modes: * **URL Component (`encodeURIComponent`)**: This mode encodes almost all special characters. It is designed specifically for encoding individual values *inside* a URL, such as a query parameter (e.g. `?search=my search value`). This is the most common use case. * **Full URL (`encodeURI`)**: This mode encodes the string but intentionally ignores reserved structural characters like `:`, `/`, `?`, and `#`. This is used when you have a complete, valid URL that happens to contain spaces or Unicode characters, and you want to encode the entire string without breaking the URL structure.
What characters are encoded?
URL encoding targets **reserved characters** and non-ASCII characters. * **Unreserved characters** (never encoded): `A-Z a-z 0-9 - _ . ~` * **Reserved characters** (encoded in Component mode): `: / ? # [ ] @ ! $ & ' ( ) * + , ; =` For example, the reserved ampersand `&` becomes `%26`, and a standard space becomes `%20`.
When should I URL encode something?
You should primarily use URL Component encoding for: * **Query parameter values**: Ensuring spaces and symbols don't break the URL. * **API requests**: Sending data safely inside GET requests. * **Form data**: Traditional `application/x-www-form-urlencoded` payloads. * **Redirect parameters**: Passing a return URL safely as a parameter. Do not use Component encoding on an entire valid URL (like `https://example.com`), as it will encode the `://` and break the link.
Examples
**Basic Text** Input: `Hello World` Output: `Hello%20World` **Reserved Characters** Input: `hello world & test` Output: `hello%20world%20%26%20test` **Unicode (UTF-8)** Input: `Hello, नमस्ते` Output: `Hello%2C%20%E0%A4%A8%E0%A4%AE%E0%A4%B8%E0%A5%8D%E0%A4%A4%E0%A5%87`
URL encoding is NOT encryption
URL encoding is simply a standard data format. It provides absolutely no security, confidentiality, or cryptographic protection. Never use URL encoding to "hide" passwords or sensitive data.
Privacy
Your input is processed locally in your browser and is not sent to WordTools Pro servers. All encoding and decoding operations happen quickly on your own device.
Frequently Asked Questions
URL encoding (also known as percent encoding) is a mechanism for converting characters that are not allowed in web addresses into a universally accepted format, using a percent sign (%) followed by hexadecimal digits.
encodeURIComponent is used for individual pieces of a URL (like a search query) and encodes almost everything. encodeURI is used for an entire complete URL and preserves structural characters like slashes (/) and question marks (?).
In the ASCII table, the space character corresponds to the hexadecimal value 20. Therefore, percent encoding represents a space as %20.
In the historical application/x-www-form-urlencoded specification (commonly used when submitting HTML forms), spaces were converted to plus signs (+). However, in modern standard URL encoding (RFC 3986), spaces should be encoded as %20.
Yes. Our encoder fully supports UTF-8 Unicode. You can safely encode Emojis, Japanese, Hindi, and any other non-Latin characters.
No. URL encoding offers zero security. It is only meant to format data for transport over the web. Anyone can instantly decode it.
Yes, this tool is 100% free to use online with no limitations.
No. Your input is processed entirely locally in your browser and is not sent to WordTools Pro servers.