Skip to content

URL Encoder / Decoder

Type in either box — the other updates instantly. Choose Component for a single query or path value (RFC 3986, spaces as %20), or Form for application/x-www-form-urlencoded data like an HTML form submission (spaces as +).

Mode

Processed locally. Your text never leaves your browser.

Common questions

Does "Component" mode encode a full URL, or just one value?

Just one value — a single query parameter or path segment. It deliberately doesn't encode a full URL, since that would also escape characters that must stay literal, like : / and ?. To build a query string with multiple key=value pairs, encode each value separately and join them yourself.

What happens if I decode something that isn't validly encoded?

It depends on the mode. Component mode shows a clear error for a malformed %-sequence, like a stray % or an incomplete %XX. Form mode never errors — it passes anything it can't interpret through unchanged, matching how real form-urlencoded decoding behaves in a browser.

Can I decode a value that contains a literal & or =, like "a&b=c"?

Yes — those characters are treated as part of the value's own content here, since this handles a single value rather than a full "key=value&key=value" query string, not as delimiters that would otherwise truncate the rest of the input.