URL Encoding and Decoding Online
URL encoding converts special characters and Cyrillic text into %XX percent-encoding format for safe transmission in HTTP requests. Used in APIs, UTM parameters, deep links, and GET query strings.
Frequently asked questions
What is the difference between encodeURI and encodeURIComponent?
encodeURI encodes a full URL while leaving reserved characters (/, ?, &, =, #) untouched. encodeURIComponent encodes everything, including those characters — it is used for individual parameter values in query strings.
Why do URLs need to be encoded?
URLs can only contain ASCII characters. Cyrillic text, spaces, brackets, and other characters must be percent-encoded into %XX format. Without encoding, the request may be misinterpreted by the server or browser.
What is %20 and why is + sometimes used instead?
%20 is the standard space encoding per RFC 3986. In query strings, + has historically been used as an alternative for spaces. Both are accepted by most servers, but %20 is more universally reliable.
Need a full SEO audit?
Tools help with targeted tasks. For systematic growth — request a free review of your site.