FREE WEB TOOL

URL encoder / decoder

Percent-encode or decode URL text.

Use tool

Your input is processed in your browser and is not sent to our server.

How to use it

Percent-encode text that needs to travel safely as part of a URL, or decode percent sequences back to readable characters. It is mainly for URL components such as search text or parameter values, not for encoding an entire URL.

  1. Enter the text to encode or the percent-encoded text to decode.
  2. Select Encode or Decode.
  3. Copy the result into the appropriate URL component.
Space
Becomes %20
Examples: & = ? #
Encoded when treated as component text
+
Encodes as %2B; decode does not treat plain + as a space
Best for
URL component text

a b becomes a%20b

a b becomes a%20b. A value such as a&b can also be encoded so the ampersand is not mistaken for a query separator.

Do not paste a complete URL such as https://example.com/a?x=1 and expect to keep it usable as a normal URL: characters such as :, /, ? and = will also be encoded. Encode only the component that needs escaping.

Component values are the main use case

Search terms, filenames and query parameter values are common examples where reserved characters need to be represented safely inside a larger URL.

Spaces use %20

This is URL-component encoding rather than form-style plus-for-space encoding. That distinction matters when comparing the output with form submissions.

A plain plus sign stays a plus sign when decoding

The decoder does not reinterpret + as a space. If the source uses application/x-www-form-urlencoded rules, a query parser may be a better fit.

Malformed percent sequences cannot be decoded

A percent sign must be followed by a valid hexadecimal byte sequence. Broken or truncated encoded text will produce an error instead of a guessed result.

Unicode text can be encoded too

Japanese, emoji and other Unicode characters can be converted into percent-encoded URL text when needed.

Related references: HTTP status codes · MIME types · Regex cheat sheet