URL Encoder and Decoder
Prepare query parameter values, redirect URLs, callback data, and API examples. Encoding follows `encodeURIComponent`, while decoding reports malformed percent escapes instead of silently changing them.
URL component processingLocal
Ready.
Data handling notes
- Processing runs locally without sending the URL to a server.
- The encoder is intended for URL components, not an entire URL with separators.
- Invalid percent sequences produce an explicit decoding error.
Before you rely on the result
This tool is intended for fast inspection and routine preparation. It can save time, but it does not replace review when the result affects production systems, security settings, business data, or legal obligations.
- Check representative inputs instead of assuming one example covers every edge case.
- Do not paste secrets, private customer data, or credentials unless you have confirmed the page processes that data locally and the use is allowed by your organization.
- Copy the output into your own workflow only after checking formatting, timezone, encoding, or syntax assumptions.
- Encoding tools transform representation, not trust. Decoded text can still be unsafe, misleading, or unsuitable for direct execution.
Real examples
Encode a redirect parameter
Encode the value before placing it inside another query string.
Input
https://example.com/callback?next=/dashboard&lang=zh
Output
https%3A%2F%2Fexample.com%2Fcallback%3Fnext%3D%2Fdashboard%26lang%3Dzh
Decode a copied query value
Decode tracking or callback parameters before checking what data is being passed.
Input
name=%E5%BC%A0%E4%B8%89&city=Beijing
Output
name=张三&city=Beijing
FAQ
Should I encode a complete URL?Usually no. Encode individual parameter values so `:`, `/`, `?`, and `&` can keep their structural role.
Why can decoding fail?Incomplete percent escapes and invalid UTF-8 byte sequences are not valid encoded components.