URL encode, both ways.

Percent-encode query values, Unicode, and emoji — and decode them back. Choose component (value) or full URL.

Scope

Input

Output

Output appears here.

Component vs full URL — pick the right scope

Component uses encodeURIComponent and escapes reserved characters like / ? # & = — use it for a single query value or path segment. Full URL uses encodeURI and leaves scheme delimiters intact — use it when encoding a whole address. Choosing the wrong one is the most common URL-encoding bug.

The “+ means space” gotcha

In application/x-www-form-urlencoded data a space is written as +, but in a real URL + is a literal plus. When decoding, toggle “Treat + as space” to match where the string came from.

Unicode round-trips cleanly

Korean, Japanese, and emoji encode to UTF-8 percent sequences and decode back exactly. Broken sequences (like a truncated %) are reported instead of producing garbage.

FAQ

Why is my slash being encoded?

You are in Component mode, which escapes /. Switch to Full URL to keep path separators readable.

Is it safe for secrets in query strings?

Encoding happens locally and nothing is sent anywhere, but remember that anything in a URL can end up in server logs and browser history regardless of encoding.