Developer utility

URL encoder

Кодирование и декодирование URL (percent-encoding) прямо в браузере

Source text

Result

The result will appear here

About URL encoding

Parameter value

  • • Encodes separators too (& = ? /)
  • • For single values in a query string
  • • encodeURIComponent

Full URL

  • • Preserves the address structure
  • • For encoding a whole link
  • • encodeURI

URL encoding in practice

Where it comes in handy

Building links with UTM tags and parameters, passing search queries and Cyrillic values in the query string, debugging redirects and API requests, inserting addresses into attributes and code.

The tool supports two modes: encoding a parameter value (component) and encoding a full URL, so as not to break the address separators.

Pairing with other tools

To build tagged links use the UTM tag generator, and to get readable slugs from Cyrillic use the transliteration tool.

If a link goes through a chain of redirects, check it with the redirect checker to make sure there is a single 301 without extra hops.

Frequently asked questions

Why encode a URL?+

Addresses allow only a limited set of characters. Spaces, Cyrillic, “&”, “?”, “#” and other special characters must be percent-encoded (for example, a space → %20), otherwise the link breaks or parameters are read incorrectly.

How is encodeURIComponent different from encodeURI?+

encodeURI encodes the whole address and does not touch separator characters (: / ? & =), so it suits a full URL. encodeURIComponent encodes them too — it is used for individual parameter values so that “&” and “=” inside a value do not break the query string.

Is the data sent to a server?+

No, encoding and decoding are done in the browser with built-in JavaScript functions. The entered text is not transmitted anywhere.

Why does Cyrillic in a URL turn into %D0%BA...?+

This is correct UTF-8 percent-encoding: each byte of the character is written as %XX. The link works but looks bulky — that is why transliteration is often used for readable URLs.