URL Encoder and Decoder

Component uses encodeURIComponent and escapes reserved characters like / ? : & = so a single value is safe inside a query string. Full URL uses encodeURI and leaves those structural characters intact so a whole link still works. In the examples above the ampersand becomes %26 in Component but stays a plain & in Full URL.

Use Component for one piece of data going into a URL, such as a query parameter value, a single path segment or a form field, where every reserved character must be escaped so it cannot be mistaken for URL syntax.

Use Full URL when you already have a complete address and only want to fix unsafe characters like spaces or accented letters. It preserves the grammar characters / ? : @ & = + $ , # so the link keeps working.

This tool always produces %20 for spaces, which is correct for paths and is also accepted in query strings. The plus sign is only used by the older application/x-www-form-urlencoded form encoding, which this tool does not emit.

No. Decode uses decodeURIComponent, which leaves a literal + unchanged because + is not percent-encoding. If your source used form encoding where + means space, replace + with a space yourself before decoding.

Non-ASCII characters are encoded as their UTF-8 bytes, one %XX pair per byte. The letter é becomes %C3%A9 and many emoji expand to four bytes, so a single glyph can turn into eight hex characters. Decode reverses this back to the original character.

Component leaves the unreserved set alone: A to Z, a to z, 0 to 9, and the marks - _ . ! ~ * ' ( ). Full URL keeps that set plus the URL grammar characters, so it changes far fewer characters than Component.

Decoding throws when the input has a malformed percent escape, for example a stray % or an incomplete byte sequence like %E0%A4%A. Fix or remove the broken escape and the result will appear.

Yes. All encoding and decoding happens locally in your browser using the built-in JavaScript functions, and nothing is uploaded to a server.