Enter the text that you wish to encode or decode:
URL coding is generally used when the browser sends data to a web server. You can use our tool to automatically URL encode or decode a text string for global interoperability.
or
Decode the text: the gibberish string will be deleted and the text will be transformed into a readable format.
URL coding and URL decoding, commonly known as 'percentage coding', change a string to respect the regulations imposed by the Uniform Resource Locator specification.
The RFC 1738 universal resource locator specification dictates that solely a little set of characters are often employed in a universal resource locator structure.
These characters are: uppercase letters (A to Z), lowercase letters (a), digits (0 to 9), as well as several "reserved" symbols (dollar sign, underline, period, closing/opening) square bracket, single quote, asterisk, exclamation, plus sign and dash).
All offensive characters must be replaced by a%, followed by the two-digit hexadecimal value represented by the symbol in the ISO character set (for example, @ becomes% 40); otherwise, you might have problems trying to pass information through a URL.
In the past, people manually encoded the special characters in their encoding string. This was a tedious task that would generally result in human error. We build this tool to help you encode/decode URLs in seconds.
URL encoding refers to the encoding of certain characters in a Uniform Resource Locator (URL). URL encoding is a two-step process: the character string is encoded in a sequence of bytes and then each byte that is not an ASCII letter or a digit is also converted to a hexadecimal value of the byte.
Sometimes, reserved characters have special meanings, and URL encoding allows them to maintain their special character sequences. In other words, if a reserved character has a reserved purpose in a given context, the URL scheme dictates that it is encoded in a URL.
A URL encoding converts the character to its corresponding byte value in ASCII. This new value (two digits preceded by a%) will be used in the URL instead of the reserved character.
Here is a list of reserved characters, their purpose, and coding:
|
Personaje |
URL purpose |
Character encoding |
|
/ |
Used to separate domains and directories |
% 2F |
|
# |
Separated anchors |
%23 |
|
+ |
Indicate a space |
% 2B |
|
% |
Indicates an encoded character |
%25 |
|
@ |
Separate user details and pass domain |
%40 |
|
: |
Protocol separated from the address |
% 3B |
|
<space> |
Space, not recommended in URLs. |
+ o% 20 |
|
? |
Separate query string |
% 3F |
Strictly speaking, you should always encode the URL, especially if your link or text contains non-alphabetic characters, numbers or special characters that are used outside your normal context.
Unreserved characters (upper and lower case, digits and symbols '-', '_', '.', '~') Can be encoded, but must not be encoded.
