www.url-encode-decode.com Open in urlscan Pro
54.144.68.44  Public Scan

Form analysis
3 forms found in the DOM

POST

<form method="POST" id="cap">
  <div class="col-md-6">
    <textarea class="form-control" name="string" id="string" rows="15" placeholder="Enter the text that you wish to encode or decode."></textarea>
    <br>
    <button class="btn btn-primary" type="submit" name="action" value="Encode" style="vertical-align: top;"><span class="glyphicon glyphicon-arrow-right"></span> Encode url</button>
    <button class="btn btn-primary" type="submit" name="action" value="Decode" style="vertical-align: top;"><span class="glyphicon glyphicon-arrow-left"></span> Decode url</button>
  </div>
  <div class="col-md-6">
    <textarea class="form-control" name="string2" id="string2" rows="15" placeholder="Your results will appear here." disabled=""></textarea>
  </div>
</form>

POST /login.php

<form method="POST" action="/login.php">
  <input class="form-control" type="text" name="username" placeholder="Email Address"><br>
  <input class="form-control" type="password" name="password" placeholder="Password"><br>
  <input class="form-control btn btn-primary" type="submit" value="Login">
</form>

POST /join.php

<form method="POST" action="/join.php">
  <input class="form-control" type="text" name="email" placeholder="Email Address"><br>
  <input class="form-control" type="password" name="password" placeholder="Password"><br>
  <input class="form-control btn btn-primary" type="submit" value="Join Now">
</form>

Text Content

Toggle navigation
URL Encode/Decode From Dan's Tools
 * Web Dev
   * HTML/JS/CSS Playground
   * HTML Color Codes
   * CSS Fonts
   * Online Diff Tool
   * .htaccess Generator
   * RegEx Testing
   * RGB & HEX Color Explorer
   * RGB to HEX Color Converter
   * TimeStamp Converter
   * Website Speed Test
   * Favicon.ico & App Icon Generator
   * Online Image Editor
   * CSS Sprite Generator
   * Keyword Tool
     
 * Conversion
   * Data
     * CSV To HTML Converter
     * CSV To JSON Converter
     * CSV To TSV Converter
     * CSV To XML Converter
     * JSON To CSV Converter
     * JSON To HTML Converter
     * JSON To TSV Converter
     * JSON To XML Converter
     * XML To CSV Converter
     * XML To HTML Converter
     * XML To JSON Converter
     * XML To TSV Converter
     * Convert Files
   * Numbers
     * Binary Converter
     * Binary To Decimal Converter
     * Binary To Hex Converter
     * Binary To Octal Converter
     * Unit Converter
     * Decimal To Binary Converter
     * Decimal To Hex Converter
     * Decimal To Octal Converter
     * Hex To Binary Converter
     * Hex To Decimal Converter
     * Hex To Octal Converter
     * Data Size Converter
     * Octal To Binary Converter
     * Octal To Decimal Converter
     * Octal To Hex Converter
   * Strings
     * Binary To String Converter
     * Hex To String Converter
     * HTML Entities Escape
     * HTML Entities Unescape
     * String To Binary Converter
     * String To Hex Converter
     * Strip and Remove HTML Tags
     * Strip and Remove XML Tags
     * Word Counter
     * XML Entities Escape
     * XML Entities Unescape
 * Encode/Decoders
   * Base64 Decode
   * Base64 Encode
   * MD5 Hash Generator
   * SHA-1 Hash Generator
   * SHA-256 Hash Generator
   * SHA-512 Hash Generator
   * URL Encode/Decode
 * Formatters
   * CSS Formatter
   * GO Formatter
   * HTML Beautifier & Formatter
   * Javascript Formatter
   * Javascript Obfuscate
   * JSON Formatter & Beautifier
   * JSON Editor
   * JSON Validator
   * Perl Formatter
   * PHP Formatter
   * Python Formatter
   * Ruby Formatter
   * SQL Formatter
   * XML Formatter & Beautifier
   * CSS Minify
   * Javascript Minify
   * JSON Minify
 * Internet
   * Email Validator
   * Is It Up Or Down
   * Default Router Settings
   * User Manuals
   * What is my IP
 * Join
 * Login


URL ENCODE/DECODE




Encode url Decode url


--------------------------------------------------------------------------------


URL ENCODE AND DECODE TOOL

Use the online tool from above to either encode or decode a string of text. For
worldwide interoperability, URIs have to be encoded uniformly. To map the wide
range of characters used worldwide into the 60 or so allowed characters in a
URI, a two-step process is used:

 * Convert the character string into a sequence of bytes using 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 be encoded as: Fran%C3%A7ois

(The "ç" is encoded in UTF-8 as two bytes C3 (hex) and A7 (hex), which are then
written as the three characters "%c3" and "%a7" respectively.) This can make a
URI rather long (up to 9 ASCII characters for a single Unicode character), but
the intention is that browsers only need to display the decoded form, and many
protocols can send UTF-8 without the %HH escaping.


WHAT IS URL ENCODING?

URL encoding stands for encoding certain characters in a URL by replacing them
with one or more character triplets that consist of the percent character "%"
followed by two hexadecimal digits. The two hexadecimal digits of the triplet(s)
represent the numeric value of the replaced character.

The term URL encoding is a bit inexact because the encoding procedure is not
limited to URLs (Uniform Resource Locators), but can also be applied to any
other URIs (Uniform Resource Identifiers) such as URNs (Uniform Resource Names).
Therefore, the term percent-encoding should be preferred.


WHICH CHARACTERS ARE ALLOWED IN A URL?

The characters allowed in a URI are either reserved or unreserved (or a percent
character as part of a percent-encoding). Reserved characters are those
characters that sometimes have special meaning, while unreserved characters have
no such meaning. Using percent-encoding, characters which otherwise would not be
allowed are represented using allowed characters. The sets of reserved and
unreserved characters and the circumstances under which certain reserved
characters have special meaning have changed slightly with each revision of
specifications that govern URIs and URI schemes.

According to RFC 3986, the characters in a URL have to be taken from a defined
set of unreserved and reserved ASCII characters. Any other characters are not
allowed 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 PIECE OF TEXT

RFC 3986 does not define according to which character encoding table non-ASCII
characters (e.g. the umlauts ä, ö, ü) should be encoded. As URL encoding
involves a pair of hexadecimal digits and as a pair of hexadecimal digits is
equivalent to 8 bits, it would theoretically be possible to use one of the 8-bit
code pages for non-ASCII characters (e.g. ISO-8859-1 for umlauts).

On the other hand, as many languages have their own 8-bit code page, handling
all these different 8-bit code pages would be a quite cumbersome thing to do.
Some languages do not even fit into an 8-bit code page (e.g. Chinese).
Therefore, RFC 3629 proposes to use the UTF-8 character encoding table for
non-ASCII characters. The following tool takes this into account and offers to
choose between the ASCII character encoding table and the UTF-8 character
encoding table. If you opt for the ASCII character encoding table, a warning
message will pop up if the URL encoded/decoded text contains non-ASCII
characters.


WHEN AND WHY WOULD YOU USE URL ENCODING?

When data that has been entered into HTML forms is submitted, the form field
names and values are encoded and sent to the server in an HTTP request message
using method GET or POST, or, historically, via email. The encoding used by
default is based on a very early version of the general URI percent-encoding
rules, with a number of modifications such as newline normalization and
replacing spaces with "+" instead of "%20". The MIME type of data encoded this
way is application/x-www-form-urlencoded, and it is currently defined (still in
a very outdated manner) in the HTML and XForms specifications. In addition, the
CGI specification contains rules for how web servers decode data of this type
and make it available to applications.

When sent in an HTTP GET request, application/x-www-form-urlencoded data is
included in the query component of the request URI. When sent in an HTTP POST
request or via email, the data is placed in the body of the message, and the
name of the media type is included in the message's Content-Type header.

EXTERNAL LINKS

 * More information about percent-encoding (Wikipedia)
 * URL encoding with Java (UTF-8 character encoding, source code available)

RELATED TOOLS:

HTML Entities Escape

Base64 Encode

--------------------------------------------------------------------------------



 * Follow @danstools00

© 2014-2019 Dan's Tools | About | Privacy | Tesla Referral Code

×Close


LOGIN

If you don't already have an account, Register Now




Close
×Close


JOIN

Join to access discussion forums and premium features of the site.





Close
×Close


PLEASE SHARE!

Thank you for using my tool. If you could share this tool with your friends,
that would be a huge help:
Tweet



Or follow us to learn about our latest tools:
Follow @danstools00

Close