URL Encoder
Encode unsafe URL characters.
01 Overview
About URL Encoder
URL Encoder converts characters that are unsafe or ambiguous in a URL — spaces, ampersands, question marks, non-English letters and symbols — into percent-encoded sequences like %20, so a value survives browsers, servers and APIs without being misinterpreted or splitting the URL's structure. Encode individual parameter values, not the whole address: encoding an entire URL would also encode its slashes and colons, which are structural. It runs entirely in your browser, so links and parameter values stay private.
02 Workflow
How to use URL Encoder
- 1Paste the valueAdd the text or parameter value you want to encode — a search term, a file name, user input. It stays on your device.
- 2Run the encoderUnsafe characters are replaced with their percent-encoded equivalents locally in your browser.
- 3Review the outputConfirm spaces, ampersands and special characters have been converted.
- 4Insert and testPut the encoded value into your query string, link or API request in place of the raw text, then test the URL to confirm the server receives the intended value.
03 Good to know
Frequently Asked Questions
What characters get URL encoded?
Characters that have special meaning in URLs — such as spaces, ampersands, question marks and hashes — plus non-ASCII characters and symbols that are not safe in a URL. Safe characters like letters, digits and hyphens are left alone.
Should I encode a whole URL or just its values?
Usually just the values. Encoding a whole URL would also encode its slashes, colons and question marks, which would break its structure. Encode each query value separately and assemble the URL from the encoded parts.
What does %20 mean in a URL?
It is the percent-encoded form of a space. Encoding replaces each unsafe character with a percent sign followed by two hexadecimal digits representing that character.
What does %26 mean in a URL?
It is the percent-encoded form of an ampersand. An unencoded ampersand separates query parameters, so a value containing one must be encoded as %26 for the server to receive it as part of the value rather than as a separator.
Why does my link break when I paste a search term with an ampersand in it?
Because the ampersand splits the query string into separate parameters, so the server reads your search term as two different values. Encode the value first, and the ampersand becomes %26, which the server reads back as part of the search term.
Should I encode spaces as %20 or as a plus sign?
Use %20, which is the general percent-encoding for a space and works everywhere. A plus sign is also read as a space inside form-style query strings, but %20 is unambiguous and is the safer choice.
Do I need to encode non-English characters in a URL?
Yes. Characters outside the basic ASCII set, such as accented letters or non-Latin scripts, must be percent-encoded so browsers and servers handle them consistently. Encoding them avoids broken links and garbled parameter values.