Why do URLs contain %20?

URLs may only contain a limited character set, so other characters are written as % followed by their UTF-8 bytes in hex. A space becomes %20 (or + in query strings under the older form-encoding convention).

When should I use component vs full-URL mode?

Component mode (encodeURIComponent) escapes &, =, ?, / and is correct for individual query-string values. Full-URL mode (encodeURI) keeps URL structure characters intact — use it only to clean up a complete URL.

URL Encoder / Decoder

Encode text for safe inclusion in URLs (percent-encoding) or decode an encoded URL back into readable form. Choose component mode (encodes every reserved character — right for query-string values) or full-URL mode (preserves :, /, ?, & so a complete address stays valid). Handles all Unicode via UTF-8.

Developer Tools

EncodeDecode

Component (values)Full URL

Text to encode

Encoded result

name%3DJohn%20Doe%26city%3DS%C3%A3o%20Paulo

Component mode escapes every reserved character (right for query-string values). Full-URL mode keeps :, /, ?, & intact so a complete address stays valid.

Private by default

This tool runs entirely in your browser. Your data is never uploaded to a server.

How to use

3 clear steps.

Choose Encode or Decode.
Pick component mode for parameter values, or full-URL mode for whole addresses.
Paste your text and copy the converted result.

Good to know

Frequently asked questions

Why do URLs contain %20?: URLs may only contain a limited character set, so other characters are written as % followed by their UTF-8 bytes in hex. A space becomes %20 (or + in query strings under the older form-encoding convention).
When should I use component vs full-URL mode?: Component mode (encodeURIComponent) escapes &, =, ?, / and is correct for individual query-string values. Full-URL mode (encodeURI) keeps URL structure characters intact — use it only to clean up a complete URL.