How URL encoding works
A link may only use a small set of characters, and some of them have jobs: ? starts the query, & separates values, = joins a name to its value, # starts a fragment and / separates folders. To put any other character in a link, or one of those as plain data, it is written as its bytes: a % and two hex digits for each byte.
Letters, digits and - . _ ~ never need encoding. Characters beyond plain English, like é or emoji, are first turned into their UTF-8 bytes, so é (2 bytes) becomes %C3%A9 and 😀 (4 bytes) becomes %F0%9F%98%80.
Here it is with your numbers:
- Take the first character that isn’t a letter, digit or one of - . _ ~: space (U+0020).
- In UTF-8 it is 1 byte: 20 in hex.
- Write a % before each byte: %20.
It means a space becomes %20 in a link.
Source RFC 3986 · Uniform Resource Identifier (URI): Generic Syntax, section 2 ↗RFC 3629 · UTF-8, a transformation format of ISO 10646 ↗
What changed in your text
| Character | UTF-8 bytes | Encoded |
|---|---|---|
| space U+0020 | 20 | %20 |
| & U+0026 | 26 | %26 |
| : U+003A | 3A | %3A |
| % U+0025 | 25 | %25 |
| ! U+0021 | 21 | %21 |
%20 or +?
Both mean a space, in different places. In the address itself, a space is %20. When a web form sends what you typed (the part after ? on many search pages), browsers write each space as +, encode a typed + as %2B, and also leave * alone and encode ~. Choose “+ (HTML forms)” to encode or decode that way; otherwise a + is kept as a +.
Source WHATWG URL Standard · application/x-www-form-urlencoded (Review Draft, August 2026) ↗
URL encoding chart
The codes for the punctuation people meet most often in links.
| Character | Encoded |
|---|---|
| space | %20 |
| ! | %21 |
| " | %22 |
| # | %23 |
| $ | %24 |
| % | %25 |
| & | %26 |
| ' | %27 |
| ( | %28 |
| ) | %29 |
| + | %2B |
| , | %2C |
| / | %2F |
| : | %3A |
| = | %3D |
| ? | %3F |
| @ | %40 |
FAQs
What does URL decode mean?
It turns percent codes back into the characters they stand for: %20 back into a space, %C3%A9 back into é. Each % and two hex digits is one byte, and the bytes are read as UTF-8 text.
Source RFC 3986 · Uniform Resource Identifier (URI): Generic Syntax, section 2 ↗
What is %20 URL decode?
%20 is a space. 20 is the hex number of the space character, so a space in a link is written %20. In data sent from an HTML form, a space is written as + instead.
What is %3D in URL?
%3D is the equals sign, =. It is encoded when an = is part of a value rather than the sign that joins a name to its value, as in q=1%3D2.
What is %27 encoded?
%27 is the straight apostrophe, '. It is one of the reserved characters, which should be encoded when they are part of the data. A curly apostrophe (’) is not ASCII, so it becomes its 3 UTF-8 bytes, %E2%80%99.
Sources
- RFC 3986: Uniform Resource Identifier (URI): Generic Syntax, section 2
- WHATWG URL Standard: application/x-www-form-urlencoded (Review Draft, August 2026)
- RFC 3629: UTF-8, a transformation format of ISO 10646