URL Encoder/Decoder
Escape/unescape URLs with two encoding modes
How to Use
URLs may only contain letters, digits and a few symbols — Chinese characters, spaces, &, = and others must be percent-encoded (like %E4%B8%AD), or parameters get truncated or mis-parsed. This comes up constantly when building callbacks, redirect links and share URLs.
How to use: paste your text and pick a mode — "Component mode" escapes every reserved character and suits a single parameter value; "Full URL mode" keeps structural characters like : / ? & = and suits a complete link. Then click encode or decode.
FAQ
What's the difference between encodeURI and encodeURIComponent?
encodeURI keeps URL structural characters (: / ? & = #) and is meant for whole URLs; encodeURIComponent escapes those too and is meant for a single parameter value. If a value contains & or =, you must use the latter.
Why is a space sometimes %20 and sometimes +?
%20 is the standard percent-encoding and valid everywhere; + is a legacy form-encoding convention (application/x-www-form-urlencoded) accepted only in query strings by some servers. Prefer %20 for modern APIs.
Is my URL uploaded?
No. Encoding and decoding run entirely in your browser — nothing is transmitted.