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 online tool to encode or decode a string of text. For worldwide interoperability, URIs have to get encoded. It is to map the wide range of characters used worldwide to the 60. You can also allow characters in a URI; a two-step process gets used:

  • Convert the character string into a sequence of bytes with the UTF-8 encoding
  • Convert each byte that is not an ASCII letter or digit to %HH, where HH is the hexadecimal value of the byte

For example, the string: François, would get analyzed as Fran%C3%A7ois.

(The"ç" gets encoded in UTF-8 as 2 bytes C3 (hex) and A7 (hex). It can then get composed as the 3 characters"%c3" and"percent a7".) It ma ake a URI quite long (up to 9 ASCII characters to get one Unicode character). But the intention is that browsers only should display the decoded type. Many protocols may send UTF-8 without the %HH escaping.

What is URL encoding?

URL encoding represents encoding certain characters in a URL. It is by supplanting them with at least one character trios. The trio comprises the percent character "%" trailed by two hexadecimal digits. The two hexadecimal digits speak to the numeric estimation of the replaced name.

The term URL encoding is inexact because the encoding process is not confined to URLs. It may also apply to some other URIs (Uniform Resource Identifiers), such as URNs (Uniform Resource Names). Thus, the term percent-encoding ought to get preferred.

Which Characters allow in a URL?

The characters allowed at a URI are either allowed or unreserved. Reserved characters are those characters who have special meaning. Unreserved personalities don't have any such significance. Characters that otherwise would not get allowed represented using allowed characters. The reserved and unreserved names have changed with every revision that governs URIs.

Under RFC 3986, the URL characters are from a set of unreserved and reserved ASCII characters. Any other characters are not allowed in a URL.

The unreserved Characters may get encoded but should not get 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 need to get encoded only under certain circumstances. % # [ ]

Encoding/Decoding a Piece of Text

RFC 3986 doesn't define according to which Character encoding table non-ASCII personalities. URL encoding entails a pair of hexadecimal digits. It would be possible to use one of those 8-bit code pages for non-ASCII personalities (e.g., ISO-8859-1 to get umlauts).

Many languages have their 8-bit code page; handling these pages would be difficult. Some languages don't even fit into an 8-bit code page (e.g., Chinese). Thus, RFC 3629 proposes to use the UTF-8 character encoding table. It is to get non-ASCII characters. The following tool considers this. It selects between the ASCII with the UTF-8 character encoding table. You opt for the ASCII character encoding table; a warning message will pop up.

When and why do you use URL encoding?

Information that gets entered into HTML forms gets submitted. The form field names and values get encoded and sent to the server in an HTTP request message. The encoding relies on a very early version of the general URI percent-encoding rules. It uses many alterations like normalization and replacing spaces with"+" rather than"%20".

The MIME type of data encoded in this manner is application/x-www-form-urlencoded. It gets defined from the HTML and XForms specifications. The CGI contains rules for how web servers decode data and make it available to applications.

Once sent in an HTTP GET petition, application/x-www-form-urlencoded information gets included. When sent in an HTTP POST request or via email, the information gets placed in this message's body. The title of this media type gets included in the message of the Content-Type header.

How to Use URL Encoder/Decoder Tool?

The free online URL Encoder/Decoder tool works when you add a string of text to space. Then, all you have to do is click the"Encode" or"Decode" button, showing the results immediately. Also, check here for convert ugly URLs to SEO & user-friendly URLs by using the Free URL Rewriter Tool.

This will come in handy once you want to turn encoded JavaScript URL using readable text into more readable text. The URL includes a non-alpha numerical correspondence or character. It will get encoded into"%" (percent symbol), followed by several alphanumeric texts. Then, the white spaces in a reader will get encoded by the "+" symbol.

URLs can only get carried over into the Internet using the ASCII character set. These URLs include characters outside the ASCII set. The URL gets converted into a useable ASCII format. This URL encoding gets Used to replace dangerous ASCII characters. It uses a percentage sign (%) followed by two hexadecimal digits. URL encoding replaces a space with a plus sign (+)or with %20.