URL Encoder / Decoder

Enter the text that you wish to encode or decode:

About URL Encoder / Decoder

URL Encoder / Decoder

Use the web tool from above to either encode or decode a string of text. For worldwide interoperability, URIs have to be encoded identically. To map a wide selection of characters used around the world during the URI to about 60 allowed characters, a two-step process is used:

Convert character strings into a sequence of bytes using UTF-8 encoding
Convert each byte not to the ASCII letter or digit% HH, where HH is the hexadecimal value of the byte

What is URL encoding?

URL encoding refers to replacing some characters with one or more character triangles during a URL, with the "%"% character "%" followed by two hexadecimal digits. The 2 hexadecimal digits of the triple (s) represent the numeric value of the substituted character.

The term URL encoding may be a bit accurate as the encoding process is not limited to just URLs (Uniform Resource Locators), but can also be applied to other URIs (Uniform Resource Identifiers) such as URNs (Uniform Resource Name). Therefore, the term percent-encoding should be preferred.

What characters are allowed during URL?

The characters allowed during the URI are either reserved or unreserved (or a percentage character as part of percent-encoding). Reserved characters are characters that sometimes have special meaning, whereas unreserved characters have no such meaning. Using percent-encoding, characters would not otherwise be represented using allowed characters. The sets of reserved and unreserved characters and therefore the circumstances in which certain reserved characters have special meaning have changed slightly with each modification of the specifications governing the URI and URI schemes.

According to RFC 3986, the characters during the URL must be taken from the mentioned set of unreserved and reserved ASCII characters. Other characters are not allowed during the URL.

Unreserved characters are often encoded, but should not be encoded. Unreserved characters are:

A B C D E F G H I J K L M N O P Q R S S T U V W X X Z Z a b c d e f g h i j j k m m n n p p o r s u t v v y z 0 1 2 3 4 5 6 7 8 9 - _. ~

Reserved characters should only be encoded under certain circumstances. The reserved characters are:

! * '(); : @ & = + $, /? % # []

When and why would you employ URL encoding?

When the data entered in the HTML form is submitted, the shape field name and value are encoded and sent to the HTTP request message on the server via method GET or POST, or, historically, email. The encoding employed by default is approximated on a truly early version of the overall URI percentage-encoding rules, with a variety of modifications such as newline normalization and spaces with "+" instead of "". The MIME data is thus encoded application / x-www-form-urlencoded, and it is currently defined (still in a very old fashioned way) within HTML (XForms) specifications. In addition, the CGI specification has rules for web servers to decode such data and make it available to applications.

When sent in an HTTP GET request, the application / x-www-form-urlencoded data request is included within the query component of the NRI. When sent via an HTTP POST request or email, the information is placed in the body of the message, and therefore includes the name of the media type within the content-type title of the message.