URL Encoder
Percent-encodes text so it can be dropped safely into a URL or a query string.
Results
What this tool does
A URL has a grammar, and the characters that give it structure — the ampersand between parameters, the equals sign, the slash, the question mark, the hash — cannot also appear inside a value without confusing whatever reads it. Percent-encoding replaces them with their byte values, so a search term containing an ampersand stops looking like the start of a second parameter. Accented text is encoded from its UTF-8 bytes, which is why a single é becomes two percent groups.
Formula
anything that is not a letter, a digit, - . _ ~ becomes %XX (RFC 3986)
Variables
| Symbol | Meaning | Unit |
|---|---|---|
text | Text | — |
OUT | Encoded | — |
SB | Size before | B |
SA | Size after | B |
Worked example
- Textpesquisa de café & chá
- Encodedpesquisa%20de%20caf%C3%A9%20%26%20ch%C3%A1
- Size before22 B
- Size after42 B
Limitations
- The calculation runs entirely in your browser. The values you type are never sent to a server.
Frequently asked questions
Why does it encode ! and ' when my browser does not?
Because JavaScript's encodeURIComponent predates the current standard and leaves !'()* alone, while RFC 3986 lists only letters, digits and the four characters -._~ as unreserved. Encoding the rest is always safe and is what server-side libraries do; leaving them alone is usually safe too. This follows the standard, so the result is identical whether it is produced here or by the checks that verify this site.