URL Encoder / Decoder
Enter the text that you wish to encode or decode:
About URL Encoder / Decoder
How do URL encoding and decoding work?
The query string, commonly known as the Uniform Resource Identifier, frequently uses URL encoding (URI). The only special symbols on which users truly wish to apply URL encoding are those. If you wish to have your URL encoded or decoded, this free web tool will do the trick.
When adding special characters to a URL parameter, often known as percent encoding or percent encoding, this online URL Encoder/Decoder tool is quite helpful. Unacceptable characters are replaced during the URL encoding process with the percent sign (a%) and two additional hexadecimal numbers. If you want to determine the source of an email campaign, URL decoding is effective.
What types of URI characters are there?
There are either reserved or unreserved characters that can be used in URIs (or a percent sign as part of a percent-encoding). When a character is reserved, it may have a unique meaning. The slash character, which is frequently used to divide different parts of a URL, is an excellent illustration of this. Unreserved characters, on the other hand, have no specific significance.
The reserved characters are expressed using a distinctive character arrangement when percent-encoding is used. With each update to the specifications that govern URIs and URI schemes, the sets of reserved and unreserved characters as well as the circumstances under which specific reserved characters have special significance have slightly changed.
Advanced Options:
Character set: When encoding textual data, you must mention the character set that was used because the encoding method does not include this information. The most common option is UTF-8, although there are numerous more; if you are unsure, experiment with the settings or use the auto-detect option. The decoded data is converted using this information to the character set of our website so that all letters and symbols can be properly displayed. Note that since files don't require any web-safe conversions, this is useless for them.
Decode each line individually: Since continuous text is typically used for the encoded data, even newline characters are turned into their percent-encoded equivalents. To protect the integrity of the input, all non-encoded whitespaces are removed before decoding. If you want to decode several independent data items that are separated by line breaks, you should use this option.
In real-time: When you choose this option, no data is sent to our servers because the entered data is immediately decrypted using the JavaScript features built into your browser. Only the UTF-8 character set is supported by this option at the moment.
Information about URL-encoding
URI character types
A URI may only include reserved or unreserved characters (or a percent character as part of a percent-encoding). Characters that are sometimes reserved have unique meaning. For instance, various portions of a URL are separated by forward slash characters (or more generally, a URI). There are no such particular meanings for unreserved characters. Reserved characters are represented by unique character sequences when employing percent-encoding. With each new revision of the specifications governing URIs and URI schemes, a little adjustment is made to the sets of reserved and unreserved characters as well as the conditions under which specific reserved characters have unique meaning.
Characters with a percent-encoding reserved
When a URI scheme specifies that a character from the reserved set must be used for another purpose and the character has specific meaning (a "reserved purpose") in a particular context, the character must be percent-encoded. A reserved character is percent-encoded by first translating it to its appropriate ASCII byte value, which is then represented as a pair of hexadecimal digits. The reserved character is then substituted with the numbers in the URI, followed by a percent sign ("%"). (To represent each byte value for a non-ASCII character, the character is often translated to its UTF-8 byte sequence.)