URL Encoder
Percent-encode text for safe URL components.
Read the guideRun the tool
The calculation runs in your browser. This tool does not send your input to JVR Software.
More information
Back to the toolWhat it is and when to use it
URL encoding lets text travel inside a URL component without being confused with the punctuation that separates components. Use it for a search phrase, a query parameter value or a single path segment. For an entire query string with multiple fields, use Query Builder so the separators stay meaningful.
How it works
The browser encodes a component with percent escapes derived from UTF-8 bytes. A space becomes %20. Characters such as ampersands and slashes are escaped when they are part of the data. The receiving URL parser can then recover the original text without treating those characters as separators.
How to use it
- Decide which expression is the value and which punctuation belongs to the URL structure.
- Encode the value once and copy the output to the intended component.
- Check the resulting URL with URL Parser or confirm it in the receiving application with synthetic input.
Worked example
Encode Jobs in Cape Town & surrounds to get Jobs%20in%20Cape%20Town%20%26%20surrounds. Insert it after ?q= and it remains one search value. Without the escape for the ampersand, many query parsers would treat what follows as a new field.
Reading the result
Each percent escape represents a byte. A single accented letter or emoji can become several escapes in sequence because UTF-8 uses multiple bytes. Some form handlers write a space as a plus sign in query strings. Component encoding uses %20 and treats a literal plus as data when escaped.
Common mistakes and limits
Encoding the whole URL also encodes structural separators such as the colon and slashes. Encoding a value twice can change %26 to %2526. Decode once at the correct boundary, and use the receiving app’s documented format for spaces and repeated parameters.
