URL Encoder / Decoder

Encode special characters for URLs or decode percent-encoded strings. Everything runs in your browser — nothing is uploaded.

Encode
Decode
0 characters
Copy

FAQ

Link Sharing Web Scraping API Debugging Parameter Handling
What's the difference between URL encoding and other encodings?
URL encoding handles URL-reserved characters (&, =, ?, etc.) and non-ASCII characters so links aren't broken. Other encodings like UTF-8 are for text files.
Why do some copied links fail to open?
Special characters like spaces or Chinese may not be encoded. "Hello" should be "%E4%BD%A0%E5%A5%BD"—without encoding, the link breaks.
What's the difference between encodeURI and encodeURIComponent?
encodeURI preserves structural characters (:, /, ?, etc.) and doesn't encode them. encodeURIComponent encodes everything. Use the latter for parameter values, the former for full URLs.
How do I encode Chinese paths in URLs?
Paste the full Chinese path and the tool outputs proper percent-encoding. Browsers auto-encode in the address bar, but programmatic calls need manual encoding.
Can I batch encode/decode multiple URLs?
Yes—paste multiple URLs (one per line) and the tool processes them all at once. Perfect for web scraping workflows.
Try JSON Formatter → · Try Base64 Encoder →

What URL Encoding Actually Does

URL encoding, also called percent encoding, converts characters that are unsafe or ambiguous in a URL into % followed by hexadecimal bytes. A space becomes %20, a question mark in a parameter value becomes %3F, and non-ASCII text is encoded as UTF-8 bytes. This keeps links, query strings, redirect URLs, and API parameters from being misread by browsers or servers.

The important rule is context. Encoding a whole URL is different from encoding one parameter value. A slash in a full URL separates path segments, but a slash inside a parameter value may need to be encoded. That is why JavaScript has both encodeURI and encodeURIComponent.

Common URL Encoding Mistakes

Encoding the wrong part
Use component encoding for query parameter values. If a search term contains &, failing to encode it can accidentally create a second parameter.
Double encoding
Hello%20world encoded again becomes Hello%2520world. If you see %25, a value may have been encoded more than once.
Plus signs vs spaces
Some form encoders use + for spaces in query strings, while percent encoding uses %20. Both appear in real systems, so check what your API expects.

Example: Query Parameter

Raw value:      JSON tools & API debugging
Encoded value:  JSON%20tools%20%26%20API%20debugging
Safe URL:       /search?q=JSON%20tools%20%26%20API%20debugging