URL Encode / Decode
About this tool
Spaces and non-ASCII in a query must be encoded or servers mangle them. This page encodes the value, not the entire link. If the string already has percent signs, decode first so you do not stack %25.
Features
- encodeURIComponent-style encoding
- Decode percent sequences back to text
- Call out double-encoding when % signs pile up
How to use
- Paste a parameter value or an already-encoded string.
- Encode or decode.
- Put only that value back into the query.
- Paths usually want %20 for spaces; form bodies may use +.
When to use it
- A search term or CJK filename must go in a query
- A log line is a run of %E4 sequences
- A copied URL keeps growing and you suspect double encoding
Examples
- The two-character string 中文 often encodes to %E4%B8%AD%E6%96%87.
- hello%20world decodes to hello world.
FAQ
Why does encoded Chinese look unreadable?
Those are UTF-8 bytes in percent encoding. Decode here. Do not encode an already-encoded string.
%20 or + for spaces?
Paths and most queries use %20. application/x-www-form-urlencoded may use +. Check Content-Type.
Why does the string grow every time?
You encoded percent signs again, so % became %25. Decode to the original, then encode once.
Should I encode the whole URL?
No. Leave the scheme, host, and slashes. Encode each parameter value.
Is this Base64?
No. Percent encoding is for URLs. Base64 is a different alphabet.
Is the text uploaded?
No. Encoding stays in the browser.
Back to Encoding Tools Hub
Guides