URL Encoder/Decoder

Encode special characters for URLs or decode percent-encoded strings. All processing happens in your browser.

Encoding Mode:

encodeURIComponent

encodeURI

Spaces as + (form data)

📝 Decoded (Plain Text)

Hello World! How are you?

Characters: 24 Bytes: 24

⇄

🔗 Encoded (URL Safe)

Characters: 0 Bytes: 0

Quick Test:

Common URL Encoding Examples

Space character:

Hello World → Hello%20World or Hello+World

Query string:

search?q=coffee & tea → search?q=coffee%20%26%20tea

Special characters:

!@#$%^&*() → !%40%23%24%25%5E%26*()

Unicode characters:

café naïve → caf%C3%A9%20na%C3%AFve

About URL Encoding

URL encoding, also known as percent-encoding, is a method to encode characters in a URL that may have special meaning or are not allowed in URLs. This ensures safe transmission of data in web requests.

When to Use URL Encoding

Query Parameters: When passing data in URL query strings
Form Data: When submitting form data via GET or POST
API Requests: When including special characters in API endpoints
Path Segments: When file or folder names contain spaces or special characters

Encoding Modes

encodeURIComponent: Encodes most special characters. Best for query parameter values.
encodeURI: Preserves URL structure characters (:, /, ?, #, etc.). Best for full URLs.

Frequently Asked Questions

What characters need to be URL encoded? +

Characters like spaces, &, =, ?, #, +, %, and non-ASCII characters need encoding. Reserved characters that have special meaning in URLs must be encoded when used as data.

What's the difference between %20 and + for spaces? +

Both represent spaces. %20 is the standard URL encoding, while + is used specifically in application/x-www-form-urlencoded content (HTML form submissions).

Is my data secure? +

Yes! All encoding and decoding happens entirely in your browser. No data is sent to any server.