DEVELOPER TOOL · PRIVATE
URL Encoder Online
Percent-encode text for use in URL components.
Encode special characters so text can safely appear in a URL query component. Paste the input, make the change, then read the result before you copy it elsewhere.
Encode values rather than an entire already-structured URL when possible.
Ready — input is processed locally.
This utility runs on the current device for the supported workflow. Kaazo does not need the pasted input to calculate the result.
URL Encoder: the job it actually does
Encode special characters so text can safely appear in a URL query component.
Encode the component, not blindly the whole URL
Query values often need escaping because spaces, ampersands, slashes and other characters can have structural meaning in a URL. Encoding an entire URL as one component can also make it unusable.
Encoding a component is different from encoding an entire URL; separators such as :, /, ? and & may need to remain structural.
The point where URL Encoder stops helping
Use URL parsing tools when you need to inspect or rebuild scheme, host, path and query parts separately.
Example and result checks
When a search term is “tea & biscuits”, the ampersand should be encoded if the phrase is one query parameter value. Otherwise, the destination may interpret it as another parameter. Use the output inside the appropriate URL component; do not expect the full address to remain navigable if you encode every separator.
After constructing a link, open it and confirm the recipient receives the intended phrase. For characters outside plain ASCII, the percent-encoded form represents bytes of the text encoding; copying only part of a multi-byte sequence will break it. Treat signing, redirect validation and safe-link checking as separate tasks.
FAQ
What does URL Encoder actually do?
Encode special characters so text can safely appear in a URL query component.
What should I check before I use the output?
Query values often need escaping because spaces, ampersands, slashes and other characters can have structural meaning in a URL. Encoding an entire URL as one component can also make it unusable. Encoding a component is different from encoding an entire URL; separators such as :, /, ? and & may need to remain structural.
Does formatted or converted output prove the data is valid for my application?
No. URL Encoder can perform the syntax or data operation described here, but your application can still impose its own schema, business rules, encoding or security requirements.
Related tools
After URL Encoder, validate the output before feeding it into another transform. The data-format guide has broader context if you need it.