Building links with parameters
When a parameter value contains spaces or accents, it must be encoded so the URL does not break.
URL encoder
Encode or decode text for use in URLs.
🔒 This file is processed in your browser. It is never uploaded anywhere.
…
What it is for
Web addresses accept only a limited set of characters. Spaces, accented letters and symbols such as the ampersand or question mark either carry their own meaning within a URL or are simply not allowed, so they have to be swapped for a sequence that is.
That is why a link copied by hand sometimes fails, or breaks halfway. A space becomes %20, an accented character becomes a two-group sequence, and if that conversion does not happen, the browser reads the address differently or rejects it.
The problem appears above all when building links with parameters: an internal search, a share link, an API call where the value contains spaces or accents. Encoding that value is what makes the link arrive intact.
How it works
- Type or paste text containing special characters (spaces, accents, symbols).
- Click "Encode" to turn it into a valid URL, or "Decode" for the reverse.
- Copy the result, ready to use in a link or URL parameter.
When to use it
Decoding long links
Decoding a URL full of symbols reveals which parameters it actually carries.
Sharing searches
Links containing a search term need encoding if that term is more than a single unaccented word.
Practical tips
- Encode only the parameter value, not the whole URL: encoding the slashes and question marks stops the address working.
- The plus sign has a special meaning and can be read as a space depending on context. When in doubt, encode it.
- If a link pasted into a message gets cut off, it usually contains unencoded characters.
- Do not confuse this encoding with Base64: they solve different problems.
Frequently asked questions
Why does a link break with spaces or accented letters?
URLs don't allow those characters directly; they need to be encoded (for example, a space becomes %20) to navigate correctly.
Is this the same as Base64?
No, they're different encodings: this one is specifically meant to make text valid inside a URL, not to represent binary data.