When should I encode a component instead of a full URL?

Encode a component for a query value or path segment. Full URI encoding preserves URL separators such as colon, slash and question mark.

Why are spaces sometimes plus signs?

HTML form URL encoding represents spaces as plus signs, while standard percent encoding uses percent twenty.

Plain Text 0 chars

Encoded URL

0 chars

Component

Use for one query value, key or path segment. Reserved separators are encoded.

Full URI

Use for a complete URL. Structural characters such as :/?&= remain meaningful.

Form value

Use for HTML form-style values where spaces are represented by plus signs.

Can I encode multiple values at once?

Yes. Enable “Process each line separately” to preserve line breaks while transforming each line independently.

Why does decoding sometimes fail?

A percent sign must be followed by two hexadecimal digits, and encoded byte sequences must form valid UTF-8.

Is input sent to a server?

No. Encoding, decoding, copying and downloading happen locally in your browser.

Character	Encoded	Note
space	%20	Also + in form data
&	%26	Parameter separator
=	%3D	Key=value separator
?	%3F	Query string start
#	%23	Fragment identifier
/	%2F	Path separator (Component only)