URL Encoder/Decoder
Encode or decode URLs and query parameters using standard UTF-8 percent-encoding. Choose full URL or component mode for accurate results.
URL Encoder/Decoder tool
Use Full URL for complete links. Use Component for query parameter values.
Privacy: All operations are performed locally in your browser.
When to use URL encoding
- Building query strings (e.g. search parameters)
- Sending data via GET requests
- Handling special characters in URLs
Practical usage
- Encoding query parameters before sending requests
- Fixing broken URLs with spaces or special characters
- Decoding encoded API responses
Encoding ensures URLs are safely transmitted without misinterpretation by browsers or servers.
- Encode: Converts unsafe characters to %HH format using UTF-8.
- Decode: Converts percent-encoded text back to readable form.
- Full URL: Preserves reserved URL syntax.
- Component: Encodes everything except A-Z a-z 0-9 - _ . ~.
How to interpret: If a URL contains spaces, symbols, or non-ASCII characters, encoding ensures it is correctly processed by browsers and servers without breaking the request.
Examples
- "hello world" → hello%20world
- "email=test@example.com" (component) → email%3Dtest%40example.com
FAQ
- What does a URL encoder do?
It converts unsafe characters in a URL into percent-encoded format (e.g., space becomes %20) so they can be safely transmitted over HTTP.
- What is the difference between encodeURI and encodeURIComponent?
encodeURI is for full URLs and does not encode reserved characters like ?, =, and &. encodeURIComponent encodes almost all non-alphanumeric characters and is suitable for query parameter values.
- Does URL encoding encrypt data?
No. URL encoding is not encryption. It only transforms characters into a safe transport format.
- Which character set is used?
This tool uses UTF-8, which is the standard encoding for modern web URLs.
- Is my data sent to a server?
No. All processing is done locally in your browser.