Online URL Encoder / Decoder

Search Engine Optimization

URL Encoder / Decoder

Enter the text that you wish to encode or decode:

About URL Encoder / Decoder

Use the net tool from on top of to either encode or decode a string of text. For worldwide ability, URIs need to be encoded uniformly. To map the wide selection of characters used worldwide into the sixty around allowed characters in an exceedingly URI, a ballroom dancing method is used:

Convert the character string into a sequence of bytes victimisation the UTF-8 cryptography
Convert every computer memory unit that's not AN ASCII letter or digit to %HH, wherever HH is that the positional notation price of the computer memory unit
For example, the string: François ,would be encoded as: François 

(The "ç" is encoded in UTF-8 as 2 bytes C3 (hex) and A7 (hex), that are then written because the 3 characters this will create a URI rather long (up to nine ASCII characters for one Unicode character), however the intention is that browsers solely have to show the decoded kind, and plenty of protocols will send UTF-8 while not the %HH escaping.

What is Url Encoding?

URL cryptography stands for encoding sure characters in an exceedingly computer address by replacement them with one or additional character triplets that contains the % character "%" followed by 2 positional notation digits. the 2 positional notation digits of the triplet(s) represent the numeric price of the replaced character.

The term computer address cryptography may be a bit inexact as a result of the encoding procedure isn't restricted to URLs (Uniform Resource Locators), however can even be applied to the other URIs (Uniform Resource Identifiers) like URNs (Uniform Resource Names). Therefore, the term percent-encoding ought to be most popular.

Characters Allowed in URL

The characters allowed in an exceedingly URI are either reserved or unreserved (or a % character as a part of a percent-encoding). Reserved characters are those characters that typically have special that means, whereas unreserved characters don't have any such that means. victimisation percent-encoding, characters that otherwise wouldn't be allowed are delineated  victimisation allowed characters. The sets of reserved and unreserved characters and also the circumstances beneath that sure reserved characters have special that means have modified slightly with every revision of specifications that govern URIs and URI schemes.

According to RFC 3986, the characters in an exceedingly computer address need to be taken from an outlined set of unreserved and reserved ASCII characters. the other characters aren't allowed in an exceedingly computer address.

The unreserved characters may be encoded, however shouldn't be encoded. The unreserved characters are:

A B C D E F G H I J K L M N O P alphabetic character R S T U V W X Y Z a b c d e f g h i j k l m n o p q r s t u v w x y z zero one a pair of three four five six seven eight nine - nine . ~

The reserved characters need to be encoded solely beneath sure circumstances. The reserved characters are:

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

When You Should Use This Tool?

When information that has been entered into hypertext markup language forms is submitted, the shape field names ANd values are encoded and sent to the server in an hypertext transfer protocol request message victimisation methodology GET or POST, or, traditionally, via email. The cryptography utilized by default is predicated on a really early version of the overall URI percent-encoding rules, with variety of modifications like newline standardisation and replacement areas with "+" rather than " ". The MIME sort of information encoded this fashion is application/x-www-form-urlencoded, and it's presently outlined (still in an exceedingly} very superannuated manner) within the hypertext markup language and XForms specifications. additionally, the CGI specification contains rules for a way internet servers decode information of this kind and create it out there to applications.

When sent in AN hypertext transfer protocol GET request, application/x-www-form-urlencoded information is enclosed within the question element of the request URI. once sent in AN hypertext transfer protocol POST request or via email, the information is placed within the body of the message, and also the name of the media sort is enclosed within the message's Content-Type header.