URL Encode Decode Online
Encode text for safe URL usage or decode percent-encoded strings back to readable format. Helpful for query params, redirects, API debugging, and logs.
URL Encode / Decode
Encode special characters for URLs or decode URL-encoded strings back to readable text.
Try examples
What Is URL Encoding?
URL encoding (also called percent-encoding) converts reserved or non-ASCII characters into a safe text format for use in URLs. For example, space becomes %20, question mark becomes %3F, and ampersand becomes %26.
Without proper encoding, query parameters can break or be interpreted incorrectly by browsers, reverse proxies, and backend services.
Common Use Cases
- Build safe query strings for search pages and redirects.
- Decode URLs copied from logs to inspect real parameters.
- Prepare API request payloads that include special characters.
- Handle multilingual text in web links.
URL Encoding Reference
| Character | Encoded | Typical Context |
|---|---|---|
| space | %20 | Search query and title text |
| ? | %3F | Literal question mark in value |
| & | %26 | Nested URL in query parameter |
| = | %3D | Key-value data inside one param |
| / | %2F | Path fragment in value |
Real Debugging Examples
- Broken callback URL: nested
https://...not encoded in one query value. - Chinese query garbled: non-ASCII text sent without encoding.
- Double-decoding issue: backend decodes an already decoded value.
Related Tools
- JWT Decoder
- JSON Formatter
- Base64 Encode Decode
- Unix Timestamp Converter
- Cron Expression Generator
- Cron Expression Parser
Common Mistakes
- Wrong function choice: using
encodeURIComponenton full URL path separators. - Double encode/decode: running transformation twice creates malformed values.
- Ignoring plus behavior:
+can represent spaces in form-style payloads. - Unencoded UTF-8 text: non-ASCII characters can break request parsing.
Recommended Debug Flow
- Identify whether input is full URL, query value, or nested redirect URL.
- Decode once and inspect separators (`?`, `&`, `=`) to confirm structure.
- If decoded value is Base64/JWT payload, continue with Base64 Encode Decode or JWT Decoder.
- Re-encode only the required segment before sending request.
Frequently Asked Questions
When should I URL-encode text?▾
Encode text when putting it into query parameters, path segments, or any URL field that may contain spaces and special characters.
Why does '+' become space after decoding?▾
In form-style encoding, '+' often represents space. This tool handles that behavior when decoding.
What is the difference between encodeURI and encodeURIComponent?▾
encodeURI keeps URL separators, while encodeURIComponent encodes almost all special characters. Query values usually require encodeURIComponent.
Why does my redirect URL break after encoding?▾
Most issues come from encoding the full URL twice or encoding separators in the wrong context.