Encode and decode URL components instantly. Auto-converts as you type. Your data never leaves your browser.
Text Input
URL-Encoded Output
Pro tip
Broken URLs in API calls? Git AutoReview catches URL encoding issues, malformed query strings, and hardcoded endpoints in your PRs.
Type or paste text into the input and the tool encodes or decodes it automatically. Switch between Encode and Decode mode with the toggle button or Ctrl+Enter. No button click needed — results appear as you type.
Building API query strings is the most common use case. When you pass user input as a URL parameter, special characters like &, =, and spaces must be encoded or the URL breaks. A search query "red shoes & hats" becomes "red%20shoes%20%26%20hats" in a URL.
OAuth redirect URLs frequently need double encoding. The redirect URI itself is a URL parameter, so it must be percent-encoded. This is where most OAuth integration bugs come from — missing or incorrect URL encoding.
Webhook payloads, form submissions, and API request bodies sometimes use application/x-www-form-urlencoded format where all values are URL-encoded. Debugging these requires a quick decoder.
International domain names and paths with non-ASCII characters (like /блог/ or /日本語/) need encoding for HTTP. Modern browsers handle this automatically in the address bar, but API clients and scripts often do not.
encodeURI leaves URL-structural characters alone — colons, slashes, question marks, ampersands.
encodeURIComponent encodes everything except letters, digits, and a few safe chars (- _ . ~). This tool uses it — safer default for parameter values.
Double encoding: encoding an already-encoded string turns %20 into %2520. The server decodes only once and gets a literal %20 instead of a space. Always encode raw values, not already-encoded strings.
Encoding the full URL: if you encode "https://example.com/path?q=test" with encodeURIComponent, the slashes and colons get encoded too, breaking the URL. Use encodeURIComponent only for parameter values, not the full URL.
Forgetting to encode: passing raw user input into a URL without encoding is a security risk (URL injection) and a bug source. Always encode user-provided values.
URLs often contain API keys, session tokens, user data, and internal endpoints. Decoding them on a server exposes this data to a third party. This tool runs entirely in your browser — nothing leaves your machine.
Auto-converts as you type. Press Ctrl+Enter to toggle between encode and decode mode. Press Ctrl+Shift+C to copy the output.
It swaps characters that would break a URL — spaces, ampersands, non-ASCII text — into %XX sequences that HTTP can handle safely. Without it, a search query with & in it would accidentally start a new parameter.
Yes. Encoding and decoding runs entirely in your browser using the built-in encodeURIComponent() and decodeURIComponent() functions. Your data is never sent to any server.
encodeURI leaves URL-structural characters alone (colons, slashes, question marks, ampersands). encodeURIComponent encodes everything except letters, digits, and a few safe chars — it is the safer choice for parameter values, which is what this tool uses.
URL encode whenever you pass user input as a URL parameter, build query strings programmatically, include special characters in API requests, or embed URLs inside other URLs.
Characters like & and = and ? have jobs inside URLs — an unencoded & starts a new parameter, a space can terminate the URL entirely. Encoding turns them into literal text so they stop doing those jobs.
Both represent spaces in URLs. %20 is the standard percent-encoding. The + sign is an older convention used only in query strings. Modern APIs typically prefer %20. This tool uses %20.
Yes. This tool fully supports Unicode text — Chinese, Japanese, Arabic, Cyrillic, emoji, and any other characters. They are converted to UTF-8 bytes and then percent-encoded.
Double encoding happens when you encode an already-encoded string. For example, %20 becomes %2520. This breaks URLs because the server decodes only once and gets %20 literally.
The tool auto-converts as you type. Ctrl+Shift+C copies the output. Ctrl+Enter toggles between encode and decode mode.
Developer Toolkit by Git AutoReview
Free tools for developers. AI code review for teams.