Quickly encode or decode URI components and web query parameters for safe HTTP transmission.
Uniform Resource Identifiers (URIs) and URLs are strictly constrained to a limited set of ASCII characters defined in RFC 3986. When web applications transmit query parameters, form submissions, or authentication tokens containing special characters, non-ASCII symbols, or reserved delimiters (such as spaces, question marks, slashes, or ampersands), those characters must be converted into standard percent-encoded sequences.
Percent-encoding replaces unsafe or reserved ASCII characters with a percent sign ('%') followed by the two-character hexadecimal value of the character in UTF-8. For example, a blank space is encoded as '%20', an ampersand as '%26', and a slash as '%2F'. Without proper encoding, web servers and API gateways misinterpret parameter boundaries, resulting in broken URLs, HTTP 400 Bad Request errors, or security vulnerabilities such as HTTP parameter pollution.
CodeGraf's URL Encoder and Decoder allows engineers, marketers, and webmasters to effortlessly switch between standard URL encoding (encodeURI) and component encoding (encodeURIComponent), inspect incoming webhook payloads, and ensure clean API communications.
Ensure Google Analytics campaign URLs, UTM tags, and landing page URLs are percent-encoded to prevent link tracking truncation.
Safely encode callback URLs and state parameters required by identity providers like Google, GitHub, and Auth0.
Encode complex search filters, JSON parameters, and dynamic user inputs before appending them to HTTP GET requests.
encodeURI is meant for complete URLs and does not encode characters that have special structural meaning in a URL (such as :, /, ?, #, and &). encodeURIComponent encodes all reserved characters, making it mandatory for query string parameter values.
In query string form data (application/x-www-form-urlencoded), spaces are traditionally replaced with a plus sign (+). In standard RFC 3986 percent-encoding (used by JavaScript and modern APIs), spaces are encoded as %20. Both are valid in query parameters.
Yes. Failure to encode user input in URLs can expose applications to HTTP Parameter Pollution (HPP), Cross-Site Scripting (XSS), and Open Redirect vulnerabilities.
Yes. Our encoder uses standard UTF-8 percent-encoding, properly translating multi-byte unicode characters into their corresponding multi-byte hex sequences (e.g. '🚀' becomes '%F0%9F%9A%80').
We architect custom enterprise platforms, scalable SaaS products, mobile applications, and high-load APIs for companies across the globe.