Know whether you are encoding the whole URL or one value
A full URL and a single query parameter should not always be encoded the same way. Mixing those cases is a common source of broken links.
Copy or inspect the parameter table.
URL Encoder/Decoder
브라우저 내부 처리
Encode or decode URLs and inspect query string parameters.
Common URL encoding mistakes
Double encoding
Encoding an already encoded value can turn spaces into patterns like %2520 and break callback or redirect logic.
Inspect the parsed query table
After encoding or decoding, review the query parameter table so you can confirm the structure instead of trusting the raw string alone.
Where this tool is most useful
Redirect and callback debugging
Helpful for reviewing login redirects, OAuth callbacks, and payment return URLs that carry long parameter chains.
Marketing link QA
It pairs well with the UTM Generator when campaign URLs need a final validation pass. Use the Query builder tab above to assemble key-value pairs, then switch to the encode tab to verify the result.
Reproducing API requests
When a request URL is long or full of reserved characters, checking it alongside API Request Tester makes encoding issues easier to isolate.
Encoding checks
encodeURI and encodeURIComponent differ
encodeURI treats the input as a whole URL and leaves ?, & and / alone; encodeURIComponent treats it as one value and encodes everything. Always use the latter for query values, or an & inside the value becomes a separator.
Seeing %25 means double encoding
% encodes to %25, so re-encoding an already-encoded value produces forms like %2520. It happens when a framework and your own code both encode. Decode exactly once — decoding twice creates special characters after your filter has run.
Non-Latin text expands per byte
URL encoding encodes bytes, not characters. A Korean syllable is three UTF-8 bytes, so it becomes nine characters such as %EC%95%88. The charset used before encoding changes the result, so check that step first when integrating with legacy systems.