About the URL Encoder / Decoder
Spaces, ampersands, question marks and non-ASCII characters can silently break a URL. This free URL encoder converts them into safe percent-encoded form (%20, %26, %3F and so on) and decodes encoded strings back into readable text. Two modes cover the two real-world situations: component mode encodes every reserved character, ideal for query-string values, while full-URL mode leaves structural characters like colons, slashes and question marks intact so a complete address keeps working.
Picking the wrong mode is the classic cause of double-encoded links and broken redirects, so the tool spells out when to use which. Encode individual parameter values — search terms, callback URLs, email addresses — with component mode before joining them into a query string; use full-URL mode only to clean up a whole address someone typed with spaces or accents. Everything runs locally in your browser, and the converted output is ready to copy instantly.
Features
- Encode and decode in both directions instantly
- Component mode for query-string parameters and values
- Full-URL mode preserves slashes, colons and question marks
- Handles UTF-8 characters, emoji and accented letters
- One-click copy of the converted output
- Processed locally — URLs are never sent to a server
How to URL encode or decode online
- Choose whether you're encoding or decoding.
- Pick component mode for parameter values, full-URL mode for whole addresses.
- Paste your text or URL into the input.
- Read the converted result immediately.
- Copy the output into your code, link or browser.
Frequently asked questions
What is percent-encoding?
Percent-encoding, also called URL encoding, replaces characters that aren't allowed in URLs with a percent sign followed by their byte value in hexadecimal — a space becomes %20, an ampersand %26. It ensures browsers and servers interpret every character as data rather than as URL structure, keeping links intact.
When should I use component mode versus full-URL mode?
Use component mode when encoding a single value that will be inserted into a URL, such as a search term or a redirect address inside a query string — it encodes reserved characters like slashes and ampersands too. Use full-URL mode to tidy an entire address while keeping its structure functional.
Why does my URL end up encoded twice?
Double encoding happens when an already-encoded string gets encoded again, turning %20 into %2520. It usually means two layers of your code both encode, or you ran a finished URL through component mode after building it. Encode each value exactly once, before assembling the final address.
What does the + sign mean in a URL?
In query strings, some systems historically encode spaces as + (form encoding) instead of %20. Both usually decode to a space after the question mark, but only %20 is safe in the path portion of a URL. If a decoded result shows unexpected plus signs, they most likely started life as spaces.
Is anything I paste uploaded?
No. Encoding and decoding are performed with your browser's built-in JavaScript functions right on your device. URLs often contain tokens, session IDs and email addresses, so keeping the processing local means those values never appear in any server log — ours included.