๐Ÿ”— Developer Tool

URL Encoder / Decoder

Percent-encode URLs and query strings or decode encoded URLs back to readable text โ€” instantly, in your browser.

URL Input
Encoded Output
๐Ÿ”„

Encode & Decode

Switch between encoding and decoding in one click. Instantly swap input and output.

โš™๏ธ

Two Modes

encodeURIComponent for query values, encodeURI for full URLs โ€” pick what fits your use case.

โšก

Real-time

Text is encoded/decoded as you type with zero delay.

๐Ÿ”’

100% Private

All processing happens locally. Your URLs never leave your browser.

Frequently Asked Questions

What is URL encoding?โ–ผ
URL encoding (percent-encoding) converts special characters into a format that can be transmitted safely over the internet. Spaces become %20, & becomes %26, and so on.
Difference between encodeURI and encodeURIComponent?โ–ผ
encodeURI encodes a full URL, preserving characters like :, /, ?, &, =, #. encodeURIComponent encodes a single URL component (like a query parameter value) and encodes those special characters too.
Why do URLs have %20 instead of spaces?โ–ผ
URLs can only contain certain ASCII characters. Spaces and other special characters must be percent-encoded. A space becomes %20 because the ASCII code for space is 32 (0x20 in hex).
When should I use URL encoding?โ–ผ
Use URL encoding when building query parameters with special characters, passing values in GET requests, embedding links in HTML attributes, or handling user input in URLs.
Is + the same as %20 in URLs?โ–ผ
In query strings (form data encoding), + is often treated as a space. In path segments, use %20. Technically %20 is the correct percent-encoding; + is only equivalent in the query string context.