Enter the text that you wish to encode or decode:
If you wish to encode or decode a line or paragraph of text, then you can use this free online tool. In the first step, you can convert the given data strings to a string to byte by using UTF-8 encoding And in second step convert, all the bytes in %HH except the ASCII letters and digits that are used in your date. By this free utility, you can Encodes or decodes a string so that it matches to the Uniform Resource Locators Specification - URL (RFC 1738). To know more about URL encoding, you can Google this term “Encodes or decodes”.
URL encoding and URL decoding can easily, modify a string so that it respects the convention forced by the Uniform Resource Locators requirement. The RFC 1738 URL specification state that only a little set of characters be able to be used in a URL construction.
The upper case letters (A to Z), lower- case letters (a to z), digits/ numbers (0 to 9), as well as numerous ‘reserved’ signs/symbols (period, closing/opening bracket, dollar sign, underscore, single quote, plus sign, asterisk, exclamation, (-) Hyphen) can be included in this conversion system.
reserved characters list, their purpose with encoding:
|
Character |
Purpose in URL |
Character encode |
|
/ |
Used to separate domains & directories |
%2F |
|
# |
Separates anchors |
%23 |
|
+ |
Indicates a space |
%2B |
|
% |
Indicates an encoded character |
%25 |
|
@ |
Separate user & pass details from the domain |
%40 |
|
: |
Separate protocol from address |
%3B |
|
<space> |
Space, not recommended in URLs |
+ or %20 |
|
? |
Separate query string |
%3F |
The URL specification RFC 1738 system clearly explain to use only small number of specific characters can be used in a URL Encoding. These characters are listed here:
All offending characters are replaced by a % and a two-digit hexadecimal value that represents the character in the proper ISO character set. Here are a couple of examples: