SummaryLog

URL Encoder / Decoder

Encode and decode URL strings using encodeURIComponent or encodeURI.

Component (encodeURIComponent / decodeURIComponent)

Full URI (encodeURI / decodeURI)

This tool encodes and decodes URL strings using the same logic browsers and JavaScript use: encodeURIComponent for individual pieces like query values, and encodeURI for whole URLs. Paste text or an already-encoded string, pick a mode, and the result appears instantly.

It solves the everyday problem of unsafe characters in URLs. Spaces, ampersands, slashes, and non-ASCII text break links and query parameters unless they are percent-encoded (%20, %26, and so on). Use it when building API request URLs, debugging a query string, or reading what an encoded link actually contains.

How to use

  1. Paste or type your text in the Input box. This can be plain text to encode or an encoded string to decode.
  2. To encode or decode a single URL part (such as one query parameter value), click Encode Component or Decode Component, which use encodeURIComponent / decodeURIComponent.
  3. To process a complete URL while keeping its structure (://, /, ?, &), click Encode URI or Decode URI, which use encodeURI / decodeURI.
  4. Read the converted text in the Output box, then click Copy to put it on your clipboard.

FAQ

What is the difference between Encode Component and Encode URI?
Encode Component (encodeURIComponent) escapes nearly every reserved character, including / ? : @ & = + and #, so it is right for a single value you drop into a URL. Encode URI (encodeURI) leaves those structural characters intact, so it is meant for encoding a full URL without breaking it.
Why did decoding show an error?
decodeURIComponent and decodeURI throw a URIError on malformed input, for example a lone % sign or an incomplete sequence like %E0 without its following bytes. Check that every % is followed by two valid hexadecimal digits.
Is my input sent to a server?
No. All encoding and decoding runs locally in your browser using built-in JavaScript functions. Nothing is uploaded, so it is safe to paste URLs that contain tokens or private parameters.
Does it handle non-English characters and emoji?
Yes. Characters such as Korean, Japanese, or emoji are encoded as their UTF-8 byte sequences (for example a space becomes %20 and non-ASCII text becomes multiple %XX bytes), and decoding reconstructs the original text.