Enter the text that you wish to encode or decode:
URL Encode/decode text strings using online tools. For global interoperability, URIs must be encoded uniformly. To map a wide range of characters used globally into the 60 or so characters allowed in URIs, the following two-step process is used:
URL Decoding and Encoding is a simple online tool that does exactly that: decoding from URL encoding and encoding quickly and easily. URL encodes or decodes data into human-readable format without any hassle.
URL encoding, or per cent encoding, is a mechanism for encoding information in a Uniform Resource Identifier (URI). Although known as URL encoding, it is more commonly used within the base Uniform Resource Identifier (URI) set, which includes both Uniform Resource Locators (URLs) and Uniform Resource Names (URNs). Therefore, it is also used for data preparation for the "application/x-www-form-urlencoded" media type, often used when submitting HTML form data in HTTP requests.
The encoding scheme does not include a character set for text data, so the encoding process must specify which character set is used. Usually UTF-8, but it could be something else. If unsure, try the options available or use the auto-detect option. This information is used to convert the decoded data into our website's character set to display all characters and symbols correctly. This is irrelevant to files, as there is no need to apply web-safe conversions to them.
Newline characters are converted to a per cent-encoded format because encoded data typically consists of continuous text. Before decoding, all unencoded whitespace is removed from the input to protect its integrity. This option is useful to decode multiple independent data items separated by line breaks.
If you turn on this option, the entered data will be decoded immediately using the JavaScript functions built into your browser without transmitting the information to our servers. Currently, this mode only supports the UTF-8 character set.
All communication with our servers occurs over a secure SSL-encrypted connection (https). Uploaded files are deleted from our servers immediately after they are processed, and downloadable files are deleted immediately after the first download attempt or after 15 minutes of inactivity, whichever is shorter. We do not store or inspect the content of submitted data or uploaded files. Please read our privacy policy below for more information.
Our tools are free to use. From now on, you don't need to download any software for this simple task.
The free online URL encoder/decoder tool works when you append a text string to the space in the link. Then, just click the Encode or Decode button to see the results immediately.
This is useful when replacing an encoded JavaScript URL with barely readable text with more readable text. URLs typically contain non-alphanumeric characters or characters encoded as % (per cent sign), followed by little or no alphanumeric text. This will encode spaces in the text as + symbols.
URLs can only be communicated to the Internet using the ASCII character set. Because these URLs contain characters outside the ASCII set, you must convert the URLs to a usable ASCII format. This URL encoding replaces unsafe ASCII characters with a per cent sign (%) followed by two hexadecimal digits. URL encoding replaces spaces with a plus sign (+) or %20.
URL encoding means encoding certain characters by replacing them with one or more triplet characters with the per cent character "%" followed by two hexadecimal digits. Three two hexadecimal digits represent the numeric value of the character being replaced.
The term URL encoding is slightly imprecise because the encoding procedure is not limited to Uniform Resource Locators (URLs) but can also be applied to other Uniform Resource Identifiers (URIs), such as Uniform Resource Names (URNs). Therefore, the term per cent encoding is preferred.
Online URL encoding, or Percent-encoding, is the procedure of encoding specific information in a Uniform Resource Identifier (URI) under specific circumstances. Although it is more commonly known as URL encoding, it is typically used within a set of base Uniform Resource Identifiers (URIs) that contain both Uniform Resource Locators (URLs) and Uniform Resource Names (URNs).
This online URL encoding is also utilized for data preparation and HTML form data submission in HTTP requests. Any characters that need to be changed are replaced with a per cent sign (%) and a two-digit hexadecimal value representing a character from the corresponding ISO character set.
Characters allowed in a URI are either reserved or unreserved (or the per cent sign, part of the per cent encoding). Reserved characters represent characters that may have special meaning. A good example of this is the slash character commonly used to separate different parts of a URL. On the other hand, unreserved characters have no special meaning.
Reserved characters are displayed using their character array when using per cent encoding. The set of reserved and unreserved characters and the conditions under which certain reserved characters have special meaning have changed slightly each time the specifications governing URIs and URI schemes have been revised.
Suppose a particular character in the reserved set has a special meaning in a particular context, and the URI scheme says it is important to use that particular character for another purpose. In that case, that character should be percent-encoded.
Percent-encoding a reserved character usually requires converting the character to its byte value in ASCII and then representing it as a hexadecimal pair. The number preceding the per cent sign (%) is then used in the URI instead of the reserved characters.
Fnon-ASCII characters are usually converted to a byte array in UTF-8, with each byte value represented as mentioned above. Reserved characters that have no reserved use in a particular context may also be encoded as percentages but are no different semantically from non-reserved characters.
Let me give you an example. "/" is still considered reserved but generally has no reserved use unless a particular URI scheme specifies otherwise. This is why there is no need to percent-encode characters with no reserved purpose.
Because the per cent character (%) already serves as a symbol for per cent-encoded octets, it must be per cent-encoded as %25 so that users can use them as data within a URI.
Many URI schemes involve expressing arbitrary data, such as an IP address or a selected file system path, as components of a URI. A URI scheme specification must provide an unambiguous mapping between URI characters and all other possible data values those characters represent.
Characters allowed in URIs are reserved, unreserved, or per cent characters part of per cent encoding. Reserved characters sometimes have a special meaning, while unreserved characters have no meaning. Per cent encoding allows unacceptable characters to appear as acceptable characters.
The set of reserved and unreserved characters and the circumstances in which certain reserved characters have special meaning have changed slightly with each revision of the specifications governing URIs and URI schemes.
When data entered into an HTML form is submitted, the form field names and values are encoded and sent to the server as an HTTP request message using the GET or Post methods or via email. The encoding used by default is based on an early version of the regular URI per cent encoding rules, with several modifications, such as normalizing newlines and replacing spaces with "+" instead of "%20".
The MIME type for data encoded in this way is application/x-www-form-urlencoded, currently defined in the HTML and XForms specifications (still outdated). The CGI specification also includes rules for how web servers decode this data type and make it available to applications.
