Cron Calendar
Explain cron expressions and preview the next run times in any timezone.
OpenEscape spaces, ampersands and non-ASCII characters so a value survives inside a URL.
Add strings with spaces, unicode, or reserved chars.
Encode full URI or component-only as needed.
Unsafe bytes become %XX escape sequences.
Paste into query params or fetch URLs safely.
A campaign link carries a redirect target like https://shop.example/sale?ref=email&id=7 inside another URL's query string. Pasted as is, the inner & splits the outer parameter in two and visitors land on the wrong page. Encoding the inner value first keeps it in one piece.
Pick one of two modes. encodeURIComponent is the strict default: it escapes everything except letters, digits and - _ . ! ~ * ' ( ), which makes it right for a single query value, path segment or form field. encodeURI keeps the characters that give a URL its structure, such as : / ? # & and =, and escapes only spaces and characters that are never valid, which suits a complete link containing non-ASCII text. Both encode text as UTF-8, so é becomes %C3%A9.
Double encoding is the classic bug: run an encoded string through again and %20 turns into %2520. Encode each value once, when you build the URL, and leave it alone afterwards. Spaces become %20 here, not +, which matters if the receiving side expects HTML form encoding. To check the result, paste it into the URL decoder, and to assemble a link from separate parts, the URL builder encodes parameters for you.
Encoding uses the browser's built-in functions on the text in this tab. Tracking links, tokens and email addresses in your input are not sent anywhere.
Pair with: URL Decoder · URL Parser
Keyboard shortcut
Escape search text and filters before appending to a URL.
Encode destination URLs used as parameter values.
Percent-encode non-ASCII path segments safely.
Answers for this tool. For site-wide help, open the FAQ hub.
encodeURIComponent. The whole redirect URL is a single value inside another URL, so its own : / ? and & must be escaped. encodeURI would leave them alone and the outer URL would be parsed incorrectly.
Both JavaScript functions follow URI rules, where a space is %20. The + form comes from HTML form encoding (application/x-www-form-urlencoded). Most servers accept %20 in query strings, but a few form parsers only treat + as a space.
The text contains a lone surrogate, usually half of an emoji that was cut off while copying. JavaScript cannot encode that as UTF-8. Copy the original text again or delete the broken character.