Encode URLs and query string parameters by converting reserved characters to percent-encoded equivalents. Compliant with RFC 3986. Handles spaces, ampersands, and all special characters.
Key Features
Complies strictly with RFC 3986 percent-encoding standards
Choice between encoding full URI (keeping protocol/host intact) or component-only
Encodes spaces as either %20 or + depending on your parameter requirement
Instant live encoding as you type or paste
How to Use
Paste your URL or query parameter value into the input box.
Choose encoding mode (Full URL vs Component/Query parameter).
Click "Encode URL" to percent-encode reserved characters.
Copy the encoded URL string for use in API calls or web links.
Example
Sample input
search query & special=100%
Sample output
search%20query%20%26%20special%3D100%25
Edge Cases
Already partially encoded strings
Unicode characters outside ASCII
Path segments vs query values
Frequently Asked Questions
When should I encode a component versus a full URL?
Use component encoding for query parameter values so that characters like "&", "=", and "?" are safely escaped. Use full URL encoding to preserve "https://" and path slashes.
Should spaces be encoded as %20 or +?
RFC 3986 standard uses %20 for URL path and query parameters. HTML form data historically uses "+". For REST APIs, %20 is generally preferred.
Why is URL encoding necessary?
Certain characters have reserved structural meanings in URLs (like "?" for queries and "&" for separators). Encoding prevents query corruption and injection errors.
Privacy notice: when you run this tool, your input is sent over HTTPS to our server, processed in memory and returned. It is not stored or logged. Avoid pasting live secrets such as private keys or passwords.