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.
Câu hỏi thường gặp
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.
Bình luận (0)
Có câu hỏi, ý tưởng hoặc phát hiện lỗi trong “URL Encode and Decode”? Hãy để lại bình luận, đánh giá công cụ hoặc trả lời người khác.
Chưa có bình luận nào. Hãy là người đầu tiên chia sẻ ý kiến!