URL Encoder / Decoder

Percent-encoding done right, both directions.

Encode component (safe for query values)

The two modes, and when to use each

Component mode (encodeURIComponent semantics) escapes every special character including ?, & and = — this is what you want for a value you're placing inside a query string, like a redirect URL or a search term. Full-URL mode (encodeURI semantics) preserves the URL structure characters so the link stays navigable while spaces and non-ASCII characters get encoded.

Decoding reverses the process and reveals what an encoded parameter actually says — the fastest way to inspect a tracking link or a long redirect URL. A common bug this tool exposes: double encoding, where %2520 shows up because a % was itself encoded a second time.

FAQ

Why do spaces become %20 instead of +?

Both represent a space in query strings; + is legacy form-encoding, %20 is the URL standard. Modern APIs accept %20 universally — prefer it.

Which characters are never encoded?

Unreserved ones: A-Z, a-z, 0-9, hyphen, underscore, period and tilde. Everything else depends on the mode.