URL Encoder / Decoder

Encode or decode URLs and URL components instantly. Supports both encodeURI (for full URLs) and encodeURIComponent (for query string values).

Mode: encodeURIComponent encodeURI (full URL)

Input Encoded Output

Common URL Encoded Characters

Character	Encoded	Description
	%20	Space
!	%21	Exclamation mark
"	%22	Double quote
#	%23	Hash / fragment
$	%24	Dollar sign
%	%25	Percent sign
&	%26	Ampersand (query separator)
'	%27	Single quote
(	%28	Open parenthesis
)	%29	Close parenthesis
+	%2B	Plus sign
,	%2C	Comma
/	%2F	Forward slash
:	%3A	Colon
;	%3B	Semicolon
=	%3D	Equals (key=value separator)
?	%3F	Question mark (query start)
@	%40	At sign
[	%5B	Open bracket
]	%5D	Close bracket

Frequently Asked Questions

What is URL encoding?

URL encoding (also called percent-encoding) converts characters that are not allowed in URLs into a percent sign followed by two hex digits. For example, a space becomes %20. This ensures URLs are valid and can be safely transmitted over the internet.

When should I use encodeURIComponent vs encodeURI?

Use encodeURIComponent when encoding individual query string parameters or URL fragments — it encodes all special characters including & = ? / : etc. Use encodeURI for a full URL — it preserves characters like / : ? & = # that have structural meaning in a URL.

Why does space encode to %20 sometimes and + other times?

In standard URL percent-encoding (RFC 3986), space encodes to %20. However, HTML form data uses application/x-www-form-urlencoded format where space encodes to +. If you're building query strings from form data, + may appear; in all other cases expect %20.

Is this encoding the same as Base64?

No. URL encoding (percent-encoding) converts specific characters to %XX hex sequences and is designed for use within URLs. Base64 converts binary data to a text string using 64 ASCII characters and is used for encoding binary data in text contexts like email attachments or data URIs.