URL Encode Decode

URL ENCODER







URL DECODER









URL Encode Decode Tool

What is URL encoding?

URL encoding is a way of converting binary data to a string of characters. It is a way of displaying the data in a more human way.
URL encoding is when you manually encode a URL, something like a file:// or http://, to use it in a web browser. The problem with this is that it is very broken. Since the file system doesn't know what a URL is, it will just store it as a string, which is very broken. This means that if you have a link to a file that is a string, like a string that is "file:///myfile.txt
The answer is that URL encoding is a method of getting a URL to look like the original, by removing the first few characters from the end of the line because some browsers stop parsing a URL after that.
URL encoding is the process of converting a file's characters to ones that are easier for the web browser to interpret. This is done by changing the character encoding from a text encoding (which is typically UTF-8) to a more machine-readable encoding.

Use the above-mentioned web tool to encode or decode a text string. URIs must be encoded identically for global compatibility. A two-step procedure is utilised to map the large variety of characters used globally into the 60 or so allowable characters in a URI:

Convert the character string to a byte sequence using the UTF-8 encoding.

Convert every byte that isn't an ASCII letter or numeric to percent HH, where HH is the byte's hexadecimal value.

For example, the string François would be encoded as: Fran% C3% A7ois
(In UTF-8, the "ç" is encoded as two bytes C3 (hex) and A7 (hex), which are subsequently represented as the three characters "percent c3" and "percent a7," respectively.) This can result in a relatively lengthy URI (up to 9 ASCII characters for a single Unicode letter), however the goal is that browsers will only show the decoded form, and many protocols can deliver UTF-8 without the percent HH escaping.

What exactly is URL encoding?

URL encoding refers to the process of replacing certain characters in a URL with one or more character triplets composed of the percent character " percent " followed by two hexadecimal digits. The numeric value of the replacement character is represented by the triplet's two hexadecimal digits.

The name URL encoding is somewhat misleading because the encoding technique is not restricted to URLs (Uniform Resource Locators), but may also be used to other URIs (Uniform Resource Identifiers) such as URNs (Uniform Resource Names). As a result, the phrase percent-encoding should be used instead.


Which Characters Can Be Used in a URL?

The characters that can be used in a URI are classified as reserved or unreserved (or a percent character as part of a percent-encoding). Reserved characters are ones who have particular meaning at times, whereas unreserved characters do not. Characters that would normally be forbidden are represented by authorized characters when employing percent-encoding. With each version of the standards that govern URIs and URI schemes, the sets of reserved and unreserved characters, as well as the situations under which particular reserved characters have special significance, have altered slightly.

RFC 3986 requires that the characters in a URL be drawn from a predefined set of unreserved and reserved ASCII characters. Other characters are not permitted in a URL.
The unreserved characters can be encoded, but should not be encoded. The unreserved characters are:

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 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 0 1 2 3 4 5 6 7 8 9 - _ . ~
The reserved characters have to be encoded only under certain circumstances. The reserved characters are:

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

Encoding/Decoding a Text RFC 3986 does not specify which character encoding table non-ASCII characters (such as the umlauts ä, ö, ü) should be encoded in. Because URL encoding comprises a pair of hexadecimal digits, and a pair of hexadecimal digits is equivalent to 8 bits, one of the 8-bit code pages might conceivably be used for non-ASCII characters (e.g. ISO-8859-1 for umlauts).
On the other hand, because each language has its own 8-bit code page, managing all of these multiple 8-bit code pages would be a time-consuming task. Some languages are too large to fit within an 8-bit code page (e.g. Chinese). As a result, RFC 3629 recommends using the UTF-8 character encoding table for non-ASCII characters. This is taken into consideration by the following utility, which allows you to select between the ASCII character encoding table and the UTF-8 character encoding table. If the ASCII character encoding table is used, a warning notice will appear if the URL encoded/decoded content contains non-ASCII characters.

When and why would you want to utilise URL encoding?

When data input into HTML forms is submitted, the form field names and values are encoded and transmitted to the server in an HTTP request message using method GET or POST, or, more traditionally, by email. The default encoding is based on an early version of the generic URI percent-encoding rules, with a few tweaks such as newline normalization and replacing spaces with "+" rather than "percent 20." The MIME type of data encoded in this manner is application/x-www-form-URL encoded, which is presently described (although in a very archaic manner) in the HTML and XForms standards. Furthermore, the CGI specification includes criteria for how web servers decode this sort of data and make it available.
Application/x-www-form-URL encoded data is included in the query component of the request URI when delivered in an HTTP GET request. When data is transferred through HTTP POST or email, it is placed in the message's body, and the name of the media type is provided in the message's Content-Type header.
Meet URL Decode and Encode, a simple web application that does exactly what it says: fast and easily decodes from URL-encoding and encodes into it. You may easily URL-encode your data or decode it into a human-readable format.

URL-encoding, sometimes known as "percent-encoding," is a method of encoding data in a Uniform Resource Identifier (URI). Although it is referred to as URL-encoding, it is really utilized more broadly inside the main Uniform Resource Identifier (URI) set, which includes both Uniform Resource Locator (URL) and Uniform Resource Name (URL) (URN). As such, it is also used to prepare data of the "application/x-www-form-URL encoded" media type, which is frequently used in the submission of HTML form data in HTTP requests.

Options for advanced users

Character set:
Because our website employs the UTF-8 character set, your input data is sent in that format. If you wish to change the data to another character set before encoding, select this option. It should be noted that in the case of text data, the encoding scheme does not include the character set, thus you may need to supply the correct set during the decoding process. When it comes to files, the binary option is the default, which means that no conversion is performed; this option is necessary for everything except plain text documents.
Newline separator:
Because Unix and Windows systems utilise various line break characters, the selected choice will replace either variation inside your data prior to encoding. This is somewhat unnecessary for the files section because files already have the proper separators, but you may specify which one to use for the "encode each line separately" and "break lines into chunks" routines.
Encode each line individually:
Even newline characters are transformed to percent-encoded forms. If you want to encode numerous independent data items separated by line breaks, use this option. (*)
Split lines into chunks:
If you select this option, the encoded data will form a continuous text with no whitespaces, so check it if you wish to break it up into different lines. The character limit used is established in the MIME (RFC 2045) protocol, which says that encoded lines cannot be longer than 76 characters. (*)
When you choose this option, the input data is immediately encoded using your browser's built-in JavaScript capabilities, without transferring any information to our servers. This mode currently only supports the UTF-8 character set.

secure and safe


All communications with our servers take place via secure SSL encrypted connections (https). We remove submitted files on our servers as soon as they are processed, and the resulting downloadable file is destroyed after the first download attempt or after 15 minutes of inactivity (whichever is shorter). We do not store or examine the supplied data or uploaded files in any manner. For additional information, please see our privacy statement.

Free of charge


Our tool is completely free to use. You no longer need to download any software for such easy activities.