ToolNest logoToolNest.

Free Online URL Encoder / Decoder

Last updated: 2026-10-06

Quick answer: Working with messy query strings? Our free URL encoder/decoder converts special characters to percent-encoding (%20, %2F) and decodes them back — with separate modes for full URLs and query-string components, so encodeURI vs encodeURIComponent confusion ends here.

🔒 100% Private: Data never leaves your device.

✓ Free forever  ·  ✓ No signup  ·  ✓ Tool inputs stay in your browser — never sent to our servers.

Try next: Base64 Encoder / Decoder · HTML Encoder / Decoder · JWT Decoder

How to Use the URL Encoder / Decoder

  1. Paste your URL or percent-encoded string into the input box.
  2. Pick Full URL mode (keeps : / ? # intact) or Query component mode (encodes everything).
  3. Click Encode or Decode — the result appears instantly.
  4. Copy the result with one click.

Why Use Our URL Encoder / Decoder?

Common Use Cases

URL Encoder / Decoder vs Alternatives

For one-off manual encoding and decoding with the encodeURI-vs-encodeURIComponent question answered for you, this page is the fastest path — free, no signup, and your URLs never leave the browser. Inside actual code, use your language's standard library.

Frequently Asked Questions

What is URL encoding?
Replacing unsafe characters in a URL with % followed by hex codes (e.g., space becomes %20) so the URL transmits safely.
When do I use query-component mode?
When encoding a value that goes inside a query parameter — it encodes / ? & = too, so they can't break the URL structure.
Why do I see + instead of %20 sometimes?
The + form comes from HTML form encoding (application/x-www-form-urlencoded). In real URLs, %20 is the correct encoding for spaces.
Can it decode double-encoded URLs?
Yes — run Decode twice and each pass unwraps one encoding layer.
Is my URL uploaded anywhere?
No. Encoding and decoding run entirely in your browser.
Which characters must be percent-encoded in a URL?
Spaces, < > " # % { } | \ ^ `, and all non-ASCII characters must always be encoded. Reserved characters (: / ? # [ ] @ ! $ & ' ( ) * + , ; =) are legal as URL delimiters, but must be encoded when they appear as data — which is exactly what query-component mode does.
How do I encode a URL that contains spaces?
Spaces become %20 in paths. In query strings, + is also accepted (form encoding), but %20 is the safe universal choice. Paste the URL in full-URL mode and the spaces are handled correctly without mangling the structure.
What do %40, %3A, and %2F mean?
%40 is @ (common in email addresses inside query parameters), %3A is :, and %2F is /. Paste any encoded string here and Decode shows you the readable version instantly.
Why does my URL show %2520?
Double encoding: the string was encoded twice, so % itself got encoded to %25 — turning %20 into %2520. Run Decode twice, then encode once, cleanly.
Should I encode the whole URL or just the values?
Encode the values, not the whole URL. Encoding everything mangles the :// and ? delimiters that hold the URL together. Best practice: build the URL structure yourself, then encode each parameter value in query-component mode.
How do I URL-decode in code?
JavaScript: decodeURIComponent(s). Python: urllib.parse.unquote(s). PHP: urldecode(s). All three handle UTF-8 sequences like this tool does.