URL Encoder Decoder: Percent-Encoding Tool
Need a reliable URL Encoder Decoder? Use this tool to URL encode online free, convert special characters to URL encoding, or decode URL with % symbols online according to the official RFC 3986 web standard.
What is URL Encoding and Percent-Escaping?
URL encoding (also called percent-encoding) converts reserved symbols, spaces, and non-ASCII characters into standard percent escape sequences (%HEX). This ensures browsers, servers, and APIs transmit URLs, path components, and query parameters cleanly without breaking core protocol syntax.
URIs rely on a defined subset of the ASCII character set. When parameters include spaces, ampersands, slashes, or emojis, an online percent encoding converter for query strings translates each raw byte into a valid UTF-8 hexadecimal pair.
Unsafe Character Byte (UTF-8) → % + Hexadecimal ValueFor example, when wondering how to encode a URL with spaces and ampersands, space turns into %20 and an ampersand becomes %26.
How Data Translation Works Step-by-Step
Step 1: Character Classification — The parser reads your raw string character by character to detect if each symbol belongs to the unreserved set (A-Z, a-z, 0-9, -, _, ., ~).
Step 2: UTF-8 Byte Conversion — Reserved or non-ASCII characters convert directly to their underlying UTF-8 byte stream. For instance, the letter é produces two bytes: 0xC3 and 0xA9.
Step 3: Percent Escape Assembly — Each byte receives a leading % prefix followed by two uppercase hexadecimal digits (e.g., %C3%A9).
Step 4: Decoding Reconstruction — When you decode URL with % symbols online, the engine identifies each %XX escape sequence, converts the hex digits back into raw bytes, and decodes the UTF-8 buffer into original text.
The Master Character Conversion Matrix
Compare how standard RFC 3986 rules and form-encoded data process reserved characters:
| Character Type | Literal Input | Standard RFC 3986 | application/x-www-form-urlencoded |
|---|---|---|---|
| Space Character | [space] | %20 | + or %20 |
| Ampersand Separator | & | %26 | %26 |
| Forward Slash | / | %2F | %2F |
| Question Mark | ? | %3F | %3F |
| Equals Declaration | = | %3D | %3D |
Query Strings, RFC 3986 & Security
Passing unencoded data inside a query string breaks key-value parameter pairs. For example, passing title=Rock & Roll makes servers read Roll as a separate key with an undefined value. Encoding the query parameter into title=Rock%20%26%20Roll preserves the string intact.
Proper URL escaping also protects backend APIs from parameter pollution and injection attacks. By converting user input into percent-encoded strings before appending to redirects or webhook URLs, your application safely separates data values from routing directives.
Frequently Asked Questions
What is URL encoding and why is it used?
URL encoding converts reserved characters and unsafe symbols into ASCII-compatible percent-encoded sequences (%HEX). It ensures web servers and browsers transmit query strings and URI paths reliably without misinterpreting syntax delimiters.
What does %20 mean in a URL?
%20 is the percent-encoded representation of a standard space character. In hexadecimal, ASCII byte 32 (a space) equals hex 20. When placed in a URI path or query parameter, %20 represents a space safely.
What characters need to be encoded in a URL?
All characters outside the unreserved RFC 3986 set (A-Z, a-z, 0-9, -, _, ., ~) require encoding when used as data. This includes reserved delimiters (: / ? # [ ] @ ! $ & ' ( ) * + , ; =) and non-ASCII UTF-8 characters.
What is the difference between URL encoding and Base64 encoding?
URL encoding replaces specific reserved bytes with %HEX sequences while keeping plain text readable. Base64 encoding converts arbitrary binary data into a fixed 64-character ASCII alphabet, fundamentally altering the entire input string.
Why do some URLs have percent signs?
Percent signs serve as escape sequence indicators in percent-encoding. The character directly following a % sign contains the two-digit hexadecimal byte value representing a special character or non-ASCII symbol.
URL Encoding & Decoding Engine
* URI transformations strictly conform to RFC 3986 (Uniform Resource Identifier Generic Syntax) specifications and execute 100% locally.
Check out 4 similar collection of utilities calculators