How to use URL Encoder / Decoder
Percent encoding protects reserved characters when text becomes one component of a URL. This tool applies component encoding, which is appropriate for a query value or path segment rather than an entire address.
Unicode text is converted safely, and decoding reverses valid percent sequences. Keeping the scheme, host and structural separators outside the input avoids encoding characters that define the URL itself.
A reliable workflow
- Choose Encode for raw text or Decode for an encoded component
- Paste one query value or path segment
- Convert, then insert the result with a URL API rather than string concatenation
Worked example
Encode the included campaign value containing spaces, an ampersand and Chinese text
campaign=summer launch&city=上海Reserved separators and UTF-8 bytes become percent sequences suitable for one query value. The result is a component, not a complete encoded URL
When this tool helps
- Encode search terms containing spaces or ampersands
- Inspect a callback parameter copied from a browser
- Prepare Unicode text for a query value
Accuracy and safety notes
- Encoding is not encryption and does not conceal data
- Do not repeatedly decode untrusted input without knowing how many encoding layers are expected
Frequently asked questions
Does XXF upload or store my data?+
No. The conversion runs locally in your browser. Your input is not sent to XXF, stored on a server or used for training.
Does this encode an entire URL?+
It uses URL-component encoding, which is ideal for individual path or query values. Keep protocol and hostname separators outside the input.