URL Encode and Decode
Percent-encode or decode text for URLs and query strings. Useful next to Base64 when +, / or = break in a URL—or when an API double-escaped a payload. For tokens in URLs, prefer Base64URL over percent-encoding standard Base64.
URL encoding vs Base64URL
Percent-encoding turns unsafe URL characters into %XX. Base64URL changes the Base64 alphabet so tokens never need % escapes. Prefer Base64URL for JWTs and API tokens; use this tool for query strings, paths and form bodies.
AI agent tip
When an agent builds a callback URL with state=…, Base64URL the state blob first, then only percent-encode if the whole URL still needs it. Double-encoding is a common agent bug.
자주 묻는 질문
When should I URL-encode Base64?
Only if you must put standard Base64 in a query string. Better: use Base64URL so + and / never appear.
What is the difference between + and %20?
In application/x-www-form-urlencoded bodies, spaces become +. In path segments and modern query encoding, spaces are usually %20. This tool shows both interpretations when relevant.
댓글 (0)
“URL Encode and Decode”에 대한 질문, 아이디어, 버그가 있으신가요? 댓글을 남기거나 도구를 평가하거나 다른 사람에게 답글을 달아 주세요.
아직 댓글이 없습니다. 첫 번째로 의견을 남겨 주세요!