URL Encoder / Decoder
Enter the text that you wish to encode or decode:
About URL Encoder / Decoder
Use the online tool from above to either encode or decode a string of text. For worldwide interoperability, URIs have to be encoded uniformly. To map the wide range of characters used worldwide into the 60 or so allowed characters in a URI, a two-step process is used:
- Convert the character string into a sequence of bytes using the UTF-8 encoding
- Convert each byte that is not an ASCII letter or digit to %HH, where HH is the hexadecimal value of the byte
For example, the string: François, would be encoded as Fran%C3%A7ois
This web page encodes or decodes a string using URL Encoding. URL Encoding is used when placing text in a query string to avoid it being confused with the URL itself. It is normally used when the browser sends form data to a web server. URL encoding, also known as Percent-encoding, is a mechanism for encoding information in a Uniform Resource Identifier (URI) under certain circumstances. Although it is known as URL encoding it is, in fact, used more generally within the main Uniform Resource Identifier (URI) set, which includes both Uniform Resource Locator (URL) and Uniform Resource Name (URN). As such it is also used in the preparation of data of the "application/x-www-form-urlencoded" media type, as is often used in the submission of HTML form data in HTTP requests.
Why would you utilize URL Encoding?
While data that has been entered in HTML forms are submitted, the form field values and names are encoded and transferred to the server in an HTTP request message utilizing the POST or GET method, or, historically, by email. The encoding utilized by default is specifically based on an early version of the general URI per cent encoding guidelines, with some modifications, for example, newline normalization and changing spaces with "+" rather than "%20". The MIME data type encoded this way is x-www-form-URL encoded, and it is presently defined in the X-Forms and HTML specifications. Moreover, the CGI specification includes rules for how servers decode this type of data and make it available to apps. While sent in HTTP GET request, x-www-form-URL encoded data is contained in the query section of the requested web URL. While sent in a POST HTTP request or via email, the information is located in the message body, and the name of the media type is involved in the Content-Type header of the message.
