URL Encode / Decode

Free online URL encoder and decoder. Percent-encode text for safe use in URLs and decode %-encoded strings back to readable text — instantly and privately in your browser.

✓ Free ⚡ Instant 🔒 100% private
Encode mode:
Plain text / URL0 characters
Encoded result

🔒 All encoding and decoding happens in your browser — your text is never uploaded.

Advertisement

Free URL Encoder / Decoder

This free online URL encoder and decoder converts text and links into safe, percent-encoded form — and turns encoded strings back into readable text. It handles spaces, special characters, query parameters and non-English letters correctly, with a one-click toggle between encoding and decoding. It’s free, instant and runs entirely in your browser, so your data never leaves your device.

How to use the URL encoder / decoder

  1. Pick a mode: Encode to make text URL-safe, or Decode to read an encoded string.
  2. Type or paste your text or URL into the box on the left (or click Load sample).
  3. When encoding, choose Component to encode every special character, or Full URL to keep structural characters like : / ? & =.
  4. The result appears instantly on the right — click Copy to grab it.
  5. Use Swap to send the result back to the input and reverse the operation.

What is URL encoding / percent-encoding?

A URL can only safely contain a limited set of characters. Anything outside that set — a space, an accented letter, an emoji, or a symbol with special meaning — must be percent-encoded: replaced by a % followed by the two-digit hexadecimal code of each byte. For example a space becomes %20, an ampersand becomes %26, and a slash becomes %2F. This is also called URL encoding or URI encoding, and it is what keeps links from breaking when they travel through browsers and servers.

Characters fall into two groups. Unreserved characters — letters, digits and a few symbols like - _ . ~ — are always safe and are never changed. Reserved characters such as : / ? # & = have a structural meaning in a URL, so whether you encode them depends on the job. Use Component encoding for a single value such as a search term or a query-string parameter, because there you want every reserved character escaped. Use Full URL encoding when you have a complete address and want to keep its structure intact while still escaping spaces and unsafe characters.

Frequently asked questions

Is this URL encoder free and private?
Yes. It is completely free with no sign-up, and all encoding and decoding happens in your browser with JavaScript. Your text and links are never uploaded to a server.
What is the difference between Component and Full URL encoding?
Component encoding escapes every reserved character, so it is right for a single value like a search term or a query parameter. Full URL encoding leaves structural characters such as the colon, slash, question mark, ampersand and equals intact, so it is right for encoding a whole address while still escaping spaces and unsafe characters.
Why does a space become %20?
A space is not allowed directly in a URL, so it is percent-encoded. The byte value of a space is 32, which is 20 in hexadecimal, so it is written as %20. In some contexts a space is shown as a plus sign instead, but %20 is the standard percent-encoded form.
What happens if I try to decode invalid text?
If the encoded text is malformed, for example a stray percent sign that is not followed by a valid two-digit code, the tool shows a friendly message instead of crashing. Fix or remove the bad percent sequence and the decode will work.
Does it handle non-English characters and emojis?
Yes. The encoder uses UTF-8, so accented letters, non-Latin scripts and emojis are converted into the correct percent-encoded byte sequences and can be decoded back to the original characters.
Advertisement