URL Encode
URL-encode text so it can be safely placed in a link or query parameter.
About the URL Encoder
URLs can only contain a limited set of characters, so anything else - spaces, ampersands, slashes, question marks, non-Latin letters - has to be percent-encoded. This tool converts your text into that safe form, turning a space into %20, an ampersand into %26 and so on, so it can sit in a link or query string without breaking it.
How to use it
- Type or paste the text you want to make URL-safe.
- Read the percent-encoded result as it updates live.
- Copy it into your query parameter, path segment or form value.
The most common use is building a query string by hand, for example a search term that contains spaces and symbols. Be aware of the distinction between encoding a whole URL and encoding a single component: this tool encodes a value as a component, escaping reserved characters like & and = that would otherwise be interpreted as delimiters. Encoding happens entirely in your browser, so your input is never sent anywhere.
Frequently asked questions
What is the difference between URL encoding and percent encoding?
They are the same thing. Percent encoding is the formal name because each escaped byte is written as a percent sign followed by two hex digits, such as %20 for a space.
Why does a space sometimes become %20 and sometimes a plus sign?
In a URL path or with encodeURIComponent a space becomes %20. The plus sign is used for spaces only in application/x-www-form-urlencoded form data. This tool produces %20.
Should I encode the whole URL or just one value?
Encode individual values such as query parameters, not the entire URL. Encoding the whole thing would escape the slashes and colons that the URL structure needs.
Is my text uploaded when I encode it?
No. The encoding runs locally in your browser, so the text never leaves your device.