Developer Tools
URL Encoder & Decoder
Encode text and URLs into URL-safe form, or decode percent-encoded strings back to readable text. Choose whole-URL or single-component encoding, with clear errors for malformed input.
Runs in your browser
Features
What you get
All four standard modes
Encode URL, encode component, decode URL and decode component — the same functions browsers and JavaScript use.
Unicode and emoji
Characters are encoded as UTF-8, so café becomes caf%C3%A9 and 🍰 becomes %F0%9F%8D%B0.
Precise errors
Malformed sequences like %2G or a truncated %C3 are pinpointed instead of failing silently.
No accidental double-encoding
You're warned when input already looks encoded, and when decoded output still contains % sequences.
Query parameter editor
Read a URL's parameters as decoded key–value rows — repeated keys included — edit them, and get a correctly encoded URL back.
Plus sign control
Choose whether + means a literal plus or a space, as in HTML form data.
Copy or download
Copy the result in one click or save it as a .txt file.
How to use
How to use the URL Encoder & Decoder
Text is first converted to UTF-8 bytes, and each unsafe byte becomes %XX — so é becomes %C3%A9 and a space becomes %20. Encode URL (encodeURI) leaves characters that structure a URL, like : / ? # & =, untouched so the address still works. Encode component (encodeURIComponent) encodes those too, which is what you want for a single query value. Decoding reverses the process and reports the exact position of any malformed % sequence.
- 01
Choose a mode
Encode URL for a whole address, Encode component for one parameter value, or one of the decode modes.
- 02
Paste your text
The output updates as you type.
- 03
Copy the result
Copy or download it. Any warnings explain what changed and why.
Examples
Worked examples
A query value
Encode component on "rock & roll / 100%" gives rock%20%26%20roll%20%2F%20100%25 — safe to put after ?q=.
A whole URL
Encode URL on https://a.com/p?q=a b&x=1#top gives https://a.com/p?q=a%20b&x=1#top — the ?, & and # still work.
Decoding
caf%C3%A9%20%26%20%F0%9F%8D%B0 decodes to “café & 🍰”.
Technical specifications
- Modes
- encodeURI, encodeURIComponent, decodeURI, decodeURIComponent
- Character encoding
- UTF-8
- encodeURI keeps
- A–Z a–z 0–9 ; , / ? : @ & = + $ - _ . ! ~ * ' ( ) #
- encodeURIComponent keeps
- A–Z a–z 0–9 - _ . ! ~ * ' ( )
- Form data option
- + decoded as space
- Processing
- In your browser
Privacy
Text and URLs are encoded and decoded in your browser. Nothing — including tokens in query strings — is sent or stored.
Read the full privacy policy.
FAQ
URL Encoder & Decoder questions
URL encoding (percent-encoding) replaces characters that aren't allowed or have special meaning in a URL — such as spaces, &, ? and non-English letters — with a % followed by hexadecimal byte values. ZSpace Tools' URL Encoder & Decoder uses the four standard JavaScript functions: encodeURI, encodeURIComponent, decodeURI and decodeURIComponent.
Text is first converted to UTF-8 bytes, and each unsafe byte becomes %XX — so é becomes %C3%A9 and a space becomes %20. Encode URL (encodeURI) leaves characters that structure a URL, like : / ? # & =, untouched so the address still works. Encode component (encodeURIComponent) encodes those too, which is what you want for a single query value. Decoding reverses the process and reports the exact position of any malformed % sequence.
URL encoding, or percent-encoding, replaces characters that can't appear in a URL with % followed by their byte values in hexadecimal. A space becomes %20 and é becomes %C3%A9.
encodeURI encodes a complete URL but keeps characters with structural meaning — / ? # & = : — so the URL still works. encodeURIComponent encodes those too, so use it for an individual value, such as a search term placed inside a query string.
%20 is the standard percent-encoding for a space. HTML forms use an older format (application/x-www-form-urlencoded) where a space is written as +. Turn on “+ means space” when decoding form data.
A % must be followed by two hexadecimal digits that form valid UTF-8. Errors usually mean a literal % that wasn't encoded (write it as %25) or a sequence that was cut off. The tool shows where the problem is.
If you see %2520 instead of %20, the text was encoded twice. Decode it once to get %20, then again to get the original text.
No. Anyone can decode it. It only makes text safe to transport in a URL.
Related tools
Base64 Encoder & Decoder
Encode text or files to Base64 and decode it back, with full Unicode support.
URL Slug Generator
Turn titles into clean, readable URL slugs — one at a time or in bulk, with CSV export.
JSON Formatter & Validator
Beautify, minify and validate JSON, with exact line and column for every error.