www.urlencoder.org Open in urlscan Pro
2001:41d0:1008:e6c::  Public Scan

Form analysis
1 forms found in the DOM

Name: text — POST https://www.urlencoder.org/

<form method="post" name="text" action="https://www.urlencoder.org/">
  <textarea name="input" id="input" placeholder="Type (or paste) here..." spellcheck="false"></textarea>
  <span class="info"><i class="fas fa-info-circle"></i>To encode binaries (like images, documents, etc.) use the file upload form a little further down on this page.</span>
  <span class="option"><label for="option_text_charset"><select name="charset" id="option_text_charset">
        <optgroup label="Populars">
          <option value="UTF-8" selected="">UTF-8</option>
          <option value="ASCII">ASCII</option>
          <option value="ISO-8859-1">ISO-8859-1</option>
          <option value="ISO-8859-2">ISO-8859-2</option>
          <option value="ISO-8859-6">ISO-8859-6</option>
          <option value="ISO-8859-15">ISO-8859-15</option>
          <option value="Windows-1252">Windows-1252</option>
        </optgroup>
        <optgroup label="Others">
          <option value="ArmSCII-8">ArmSCII-8</option>
          <option value="BIG-5">BIG-5</option>
          <option value="CP850">CP850</option>
          <option value="CP866">CP866</option>
          <option value="CP932">CP932</option>
          <option value="CP936">CP936</option>
          <option value="CP950">CP950</option>
          <option value="CP50220">CP50220</option>
          <option value="CP50221">CP50221</option>
          <option value="CP50222">CP50222</option>
          <option value="CP51932">CP51932</option>
          <option value="EUC-CN">EUC-CN</option>
          <option value="EUC-JP">EUC-JP</option>
          <option value="EUC-KR">EUC-KR</option>
          <option value="EUC-TW">EUC-TW</option>
          <option value="GB18030">GB18030</option>
          <option value="HZ">HZ</option>
          <option value="ISO-2022-JP">ISO-2022-JP</option>
          <option value="ISO-2022-KR">ISO-2022-KR</option>
          <option value="ISO-8859-3">ISO-8859-3</option>
          <option value="ISO-8859-4">ISO-8859-4</option>
          <option value="ISO-8859-5">ISO-8859-5</option>
          <option value="ISO-8859-7">ISO-8859-7</option>
          <option value="ISO-8859-8">ISO-8859-8</option>
          <option value="ISO-8859-9">ISO-8859-9</option>
          <option value="ISO-8859-10">ISO-8859-10</option>
          <option value="ISO-8859-13">ISO-8859-13</option>
          <option value="ISO-8859-14">ISO-8859-14</option>
          <option value="ISO-8859-16">ISO-8859-16</option>
          <option value="JIS">JIS</option>
          <option value="KOI8-R">KOI8-R</option>
          <option value="KOI8-U">KOI8-U</option>
          <option value="SJIS">SJIS</option>
          <option value="UCS-2">UCS-2</option>
          <option value="UCS-2BE">UCS-2BE</option>
          <option value="UCS-2LE">UCS-2LE</option>
          <option value="UCS-4">UCS-4</option>
          <option value="UCS-4BE">UCS-4BE</option>
          <option value="UCS-4LE">UCS-4LE</option>
          <option value="UHC">UHC</option>
          <option value="UTF-7">UTF-7</option>
          <option value="UTF-16">UTF-16</option>
          <option value="UTF-16BE">UTF-16BE</option>
          <option value="UTF-16LE">UTF-16LE</option>
          <option value="UTF-32">UTF-32</option>
          <option value="UTF-32BE">UTF-32BE</option>
          <option value="UTF-32LE">UTF-32LE</option>
          <option value="UTF7-IMAP">UTF7-IMAP</option>
          <option value="Windows-1251">Windows-1251</option>
          <option value="Windows-1254">Windows-1254</option>
        </optgroup>
      </select>Destination character set.</label></span>
  <span class="option"><label for="option_text_separator"><select name="separator" id="option_text_separator">
        <option value="lf">LF (Unix)</option>
        <option value="crlf">CRLF (Windows)</option>
      </select>Destination newline separator.</label></span>
  <span class="option"><label for="option_text_newlines"><input type="checkbox" name="newlines" id="option_text_newlines"><span></span>Encode each line separately (useful for when you have multiple entries).</label></span>
  <span class="option"><label for="option_text_chunks"><input type="checkbox" name="chunks" id="option_text_chunks"><span></span>Split lines into 76 character wide chunks (useful for MIME).</label></span>
  <span class="option"><label for="option_text_live"><button type="button" class="live" id="option_text_live"><i class="fas fa-toggle-off"></i>Live mode OFF</button>Encodes in real-time as you type or paste (supports only the UTF-8 character
      set).</label></span>
  <span class="option"><button type="submit" id="submit_text"><i class="fas fa-chevron-right"></i>ENCODE<i class="fas fa-chevron-left"></i></button><label for="output">Encodes your data into the area below.</label></span>
</form>

Text Content

WE VALUE YOUR PRIVACY

We and our partners store and/or access information on a device, such as cookies
and process personal data, such as unique identifiers and standard information
sent by a device for personalised ads and content, ad and content measurement,
and audience insights, as well as to develop and improve products.
With your permission we and our partners may use precise geolocation data and
identification through device scanning. You may click to consent to our and our
partners’ processing as described above. Alternatively you may access more
detailed information and change your preferences before consenting or to refuse
consenting.
Please note that some processing of your personal data may not require your
consent, but you have a right to object to such processing. Your preferences
will apply to this website only. You can change your preferences at any time by
returning to this site or visit our privacy policy.
MORE OPTIONSAGREE
URLDecode and Encode
Decode Encode

Do you have to deal with URL-encoded format? Then this site is perfect for you!
Use our super handy online tool to encode or decode your data.



ENCODE TO URL-ENCODED FORMAT

Simply enter your data then push the encode button.
To encode binaries (like images, documents, etc.) use the file upload form a
little further down on this page.
UTF-8ASCIIISO-8859-1ISO-8859-2ISO-8859-6ISO-8859-15Windows-1252ArmSCII-8BIG-5CP850CP866CP932CP936CP950CP50220CP50221CP50222CP51932EUC-CNEUC-JPEUC-KREUC-TWGB18030HZISO-2022-JPISO-2022-KRISO-8859-3ISO-8859-4ISO-8859-5ISO-8859-7ISO-8859-8ISO-8859-9ISO-8859-10ISO-8859-13ISO-8859-14ISO-8859-16JISKOI8-RKOI8-USJISUCS-2UCS-2BEUCS-2LEUCS-4UCS-4BEUCS-4LEUHCUTF-7UTF-16UTF-16BEUTF-16LEUTF-32UTF-32BEUTF-32LEUTF7-IMAPWindows-1251Windows-1254Destination
character set. LF (Unix)CRLF (Windows)Destination newline separator. Encode each
line separately (useful for when you have multiple entries). Split lines into 76
character wide chunks (useful for MIME). Live mode OFFEncodes in real-time as
you type or paste (supports only the UTF-8 character set). ENCODEEncodes your
data into the area below.


ENCODE FILES TO URL-ENCODED FORMAT

Select a file to upload and process, then you can download the encoded result.
0 Click (or tap) here to select a file
The maximum file size is 192MB. BINARY (no
conv.)UTF-8ASCIIISO-8859-1ISO-8859-2ISO-8859-6ISO-8859-15Windows-1252ArmSCII-8BIG-5CP850CP866CP932CP936CP950CP50220CP50221CP50222CP51932EUC-CNEUC-JPEUC-KREUC-TWGB18030HZISO-2022-JPISO-2022-KRISO-8859-3ISO-8859-4ISO-8859-5ISO-8859-7ISO-8859-8ISO-8859-9ISO-8859-10ISO-8859-13ISO-8859-14ISO-8859-16JISKOI8-RKOI8-USJISUCS-2UCS-2BEUCS-2LEUCS-4UCS-4BEUCS-4LEUHCUTF-7UTF-16UTF-16BEUTF-16LEUTF-32UTF-32BEUTF-32LEUTF7-IMAPWindows-1251Windows-1254Destination
character set for text files. LF (Unix)CRLF (Windows)Newline separator (for the
"encode each line separately" and "split lines into chunks" functions). Encode
each line separately (useful for when you have multiple entries). Split lines
into 76 character wide chunks (useful for MIME). ENCODE
Working...
Please wait until the encoding process is complete.
Success!
{{ output }} to download the encoded file.
Please note that this file is removed from our system immediately after the
first download attempt or 15 minutes of inactivity.
Error!Something went wrong:{{ error }}


BONUS TIP: BOOKMARK US!




OTHER TOOLS

Base64 Decode Base64 Encode JSON Minify JSON Beautify JS Minify JS Beautify CSS
Minify CSS Beautify


PARTNER SITES

Number System Converter TV Show and Movie Ratings Secure Group Chat



ABOUT

Meet URL Decode and Encode, a simple online tool that does exactly what it says:
decodes from URL-encoding as well as encodes into it quickly and easily.
URL-encode your data without hassles or decode it into a human-readable format.

URL-encoding, also known as "percent-encoding", is a mechanism for encoding
information in a Uniform Resource Identifier (URI). Although it is known as
URL-encoding it is, in fact, used more generally within the main Uniform
Resource Identifier (URI) set, which includes both Uniform Resource Locator
(URL) and Uniform Resource Name (URN). As such it is also used in the
preparation of data of the "application/x-www-form-urlencoded" media type, as is
often employed in the submission of HTML form data in HTTP requests.

Advanced options

 * Character set: Our website uses the UTF-8 character set, so your input data
   is transmitted in that format. Change this option if you want to convert the
   data to another character set before encoding. Note that in case of text
   data, the encoding scheme does not contain the character set, so you may have
   to specify the appropriate set during the decoding process. As for files, the
   binary option is the default, which will omit any conversion; this option is
   required for everything except plain text documents.
 * Newline separator: Unix and Windows systems use different line break
   characters, so prior to encoding either variant will be replaced within your
   data by the selected option. For the files section, this is partially
   irrelevant since files already contain the corresponding separators, but you
   can define which one to use for the "encode each line separately" and "split
   lines into chunks" functions.
 * Encode each line separately: Even newline characters are converted to their
   percent-encoded forms. Use this option if you want to encode multiple
   independent data entries separated with line breaks. (*)
 * Split lines into chunks: The encoded data will become a continuous text
   without any whitespaces, so check this option if you want to break it up into
   multiple lines. The applied character limit is defined in the MIME (RFC 2045)
   specification, which states that the encoded lines must be no more than 76
   characters long. (*)
 * Live mode: When you turn on this option the entered data is encoded
   immediately with your browser's built-in JavaScript functions, without
   sending any information to our servers. Currently this mode supports only the
   UTF-8 character set.

(*) These options cannot be enabled simultaneously since the resulting output
would not be valid for the majority of applications.

Safe and secure

All communications with our servers come through secure SSL encrypted
connections (https). We delete uploaded files from our servers immediately after
being processed and the resulting downloadable file is deleted right after the
first download attempt or 15 minutes of inactivity (whichever is shorter). We do
not keep or inspect the contents of the submitted data or uploaded files in any
way. Read our privacy policy below for more details.

Completely free

Our tool is free to use. From now on, you don't need to download any software
for such simple tasks.

Details of the URL-encoding

Types of URI characters

The characters allowed in a URI are either reserved or unreserved (or a percent
character as part of a percent-encoding). Reserved characters are characters
that sometimes have special meaning. For example, forward slash characters are
used to separate different parts of a URL (or more generally, a URI). Unreserved
characters have no such special meanings. Using percent-encoding, reserved
characters are represented using special character sequences. The sets of
reserved and unreserved characters and the circumstances under which certain
reserved characters have special meaning have changed slightly with each new
revision of specifications that govern URIs and URI schemes.



RFC 3986 section 2.2 Reserved Characters (January 2005) ! * ' ( ) ; : @ & = + $
, / ? # [ ]


RFC 3986 section 2.3 Unreserved Characters (January 2005) 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 - _ . ~


Other characters in a URI must be percent encoded.

Percent-encoding reserved characters

When a character from the reserved set (a "reserved character") has special
meaning (a "reserved purpose") in a particular context and a URI scheme says
that it is necessary to use that character for some other purpose, then the
character must be percent-encoded. Percent-encoding a reserved character means
converting the character to its corresponding byte value in ASCII and then
representing that value as a pair of hexadecimal digits. The digits, preceded by
a percent sign ("%"), are then used in the URI in place of the reserved
character. (For a non-ASCII character, it is typically converted to its byte
sequence in UTF-8, and then each byte value is represented as above.)

The reserved character "/", for example, if used in the "path" component of a
URI, has the special meaning of being a delimiter between path segments. If,
according to a given URI scheme, "/" needs to be in a path segment, then the
three characters "%2F" (or "%2f") must be used in the segment instead of a "/".



Reserved characters after percent-encoding ! # $ & ' ( ) * + , / : ; = ? @ [ ]
%21 %23 %24 %26 %27 %28 %29 %2A %2B %2C %2F %3A %3B %3D %3F %40 %5B %5D


Reserved characters that have no reserved purpose in a particular context may
also be percent-encoded but are not semantically different from other
characters.

In the "query" component of a URI (the part after a "?" character), for example,
"/" is still considered a reserved character but it normally has no reserved
purpose (unless a particular URI scheme says otherwise). The character does not
need to be percent-encoded when it has no reserved purpose.

URIs that differ only by whether a reserved character is percent-encoded or not
are normally considered not equivalent (denoting the same resource) unless it is
the case that the reserved characters in question have no reserved purpose. This
determination is dependent upon the rules established for reserved characters by
individual URI schemes.

Percent-encoding unreserved characters

Characters from the unreserved set never need to be percent-encoded.

URIs that differ only by whether an unreserved character is percent-encoded or
not are equivalent by definition, but URI processors, in practice, may not
always treat them equivalently. For example, URI consumers shouldn't treat "%41"
differently from "A" ("%41" is the percent-encoding of "A") or "%7E" differently
from "~", but some do. For maximum interoperability, URI producers are therefore
discouraged from percent-encoding unreserved characters.

Percent-encoding the percent character

Because the percent ("%") character serves as the indicator for percent-encoded
octets, it must be percent-encoded as "%25" for that octet to be used as data
within a URI.

Percent-encoding arbitrary data

Most URI schemes involve the representation of arbitrary data, such as an IP
address or file system path, as components of a URI. URI scheme specifications
should, but often don't, provide an explicit mapping between URI characters and
all possible data values being represented by those characters.

Binary data

Since the publication of RFC 1738 in 1994, it has been specified that schemes
that provide for the representation of binary data in a URI must divide the data
into 8-bit bytes and percent-encode each byte in the same manner as above. Byte
value 0F (hexadecimal), for example, should be represented by "%0F", but byte
value 41 (hexadecimal) can be represented by "A", or "%41". The use of unencoded
characters for alphanumeric and other unreserved characters is typically
preferred because it results in shorter URLs.

Character data

The procedure for percent-encoding binary data has often been extrapolated,
sometimes inappropriately or without being fully specified, to apply to
character-based data. In the World Wide Web's formative years, when dealing with
data characters in the ASCII repertoire and using their corresponding bytes in
ASCII as the basis for determining percent-encoded sequences, this practice was
relatively harmless; many people assumed that characters and bytes mapped
one-to-one and were interchangeable. However, the need to represent characters
outside the ASCII range grew quickly and URI schemes and protocols often failed
to provide standard rules for preparing character data for inclusion in a URI.
Web applications consequently began using different multi-byte, stateful, and
other non-ASCII-compatible encodings as the basis for percent-encoding, leading
to ambiguities as well as difficulty interpreting URIs reliably.

For example, many URI schemes and protocols based on RFCs 1738 and 2396 presume
that the data characters will be converted to bytes according to some
unspecified character encoding before being represented in a URI by unreserved
characters or percent-encoded bytes. If the scheme does not allow the URI to
provide a hint as to what encoding was used, or if the encoding conflicts with
the use of ASCII to percent-encode reserved and unreserved characters, then the
URI cannot be reliably interpreted. Some schemes fail to account for encoding at
all and instead just suggest that data characters map directly to URI
characters, which leaves it up to individual users to decide whether and how to
percent-encode data characters that are in neither the reserved nor unreserved
sets.



Common characters after percent-encoding (ASCII or UTF-8 based) newline space "
% - . < > \ ^ _ ` { | } ~ %0A or %0D or %0D%0A %20 %22 %25 %2D %2E %3C %3E %5C
%5E %5F %60 %7B %7C %7D %7E


Arbitrary character data is sometimes percent-encoded and used in non-URI
situations, such as for password obfuscation programs, or other system-specific
translation protocols.
Switch to mobile version
2012-2022 urlencoder.org
Privacy policy Contact

This website uses cookies. We use cookies to personalise content/ads and to
analyse our traffic.