We use cookies for analytics to improve your experience. Your files are never uploaded — all processing happens locally in your browser. Read our Privacy Policy
Encode URLs and special characters online for free. Instant URL encoding for safe web transmission.
URL encoding replaces unsafe characters with percent-encoded equivalents (%XX where XX is the hexadecimal byte value). Spaces become %20, ampersands become %26, and so on. This ensures special characters don't break URL parsing — because URLs can only contain a limited set of ASCII characters.
| Input | Calculation | Result | Context |
|---|---|---|---|
| hello world | space → %20 | hello%20world | (query parameter) |
| name=John&age=30 | Encode & and = | name%3DJohn%26age%3D30 | (nested parameter) |
| café résumé | Encode UTF-8 | caf%C3%A9%20r%C3%A9sum%C3%A9 | (international text) |
When constructing URLs with query parameters that contain spaces, special characters, or non-ASCII text, URL-encode the values to prevent broken requests.
UTM parameters and tracking URLs need proper encoding to handle campaign names with spaces or special characters.
Constructing search URLs programmatically? The search term needs URL encoding to handle spaces, quotes, and other special characters.
URL encoding is also called "percent encoding" because every encoded character starts with a % sign. The spec (RFC 3986) defines exactly which characters are "safe" in URLs: A-Z, a-z, 0-9, and -._~ (unreserved characters). Everything else should technically be encoded.
Special characters in URLs (&, =, ?, #, space) have reserved meanings. Encode user input before putting it in query parameters to prevent URL parsing errors and injection attacks.
In query strings, spaces can be encoded as + or %20. %20 is more universally safe and works in both path segments and query parameters.
URLs can only contain ASCII characters, and many ASCII characters have special meanings in URLs. The ? character starts a query string, & separates parameters, # denotes a fragment, and spaces aren't allowed at all. If your data contains any of these characters, they must be percent-encoded (%XX format) to avoid breaking the URL structure.
For example, searching for "Tom & Jerry" needs to become "Tom%20%26%20Jerry" in a URL, or the & would be interpreted as a parameter separator.
| Character | Encoded | Why |
|---|---|---|
| Space | %20 or + | Not allowed in URLs |
| & | %26 | Parameter separator in query strings |
| = | %3D | Key-value separator in query strings |
| ? | %3F | Starts query string section |
| # | %23 | Starts fragment/anchor section |
| / | %2F | Path separator (encode in values only) |
Decode percent-encoded URLs back to readable text with our URL Decoder
URL Encoder on InchTool is designed to deliver professional results without compromising your privacy or charging hidden fees. Unlike most online alternatives that require uploads to remote servers, subscriptions, or account creation, InchTool runs everything directly in your browser using client-side JavaScript and modern Web APIs.
Whether you are a student, freelancer, small business owner, or developer, URL Encoder gives you reliable, professional-grade results without the overhead of installing desktop software or paying for monthly subscriptions. Bookmark this page and come back whenever you need it — no login required, ever.
URL Encoder processes everything locally in your browser. Your files and data never leave your device — there are no uploads, no server-side processing, and no cloud storage involved.
InchTool uses client-side JavaScript, the HTML5 Canvas API, and WebAssembly to deliver instant results with zero privacy risk. This architecture means your sensitive documents, personal photos, and confidential data stay exactly where they belong — on your device.
InchTool is free and always will be. If you find it useful, consider supporting us so we can keep building more privacy-first tools.
☕ Support on Ko-fiLooking for social media video tools? Check out our partner site SocialMediaVideoDownload.com