URL Encoder / Decoder

URLs can only contain a limited set of safe characters. The moment a link includes a space, an ampersand, a question mark inside a value, or text from most of the world’s languages, it must be percent-encoded or the link breaks. Our free URL encoder and decoder handles both directions: encode a full URL or a single parameter value so it survives transport intact, or decode a messy percent-encoded link from an email, log or redirect chain back into readable text so you can see where it actually goes.

Quick Answer: Paste a URL or text value and click Encode to percent-encode special characters, or Decode to turn %XX sequences back into readable characters. Component mode is safest for single parameter values.

Free Online Tool

URL Encoder / Decoder

Percent-encode URLs and values, or decode them back to readable text.





How to Use the URL Encoder / Decoder

  1. Paste your URL or parameter value into the box.
  2. Choose Encode for sharing or embedding a value safely, or Decode to inspect an encoded link.
  3. If you are encoding just one query value rather than a whole URL, leave the ‘encode as component’ option on; it also encodes characters like / and ? that carry meaning inside values.
  4. Review the result and copy it into your link, redirect or API call.
  5. If decoding shows leftover % signs, the original may have been encoded twice; decode once more to fully unwrap it.

Key Features

  • Both full-URL and component encoding modes, matching how developers actually use encodeURI and encodeURIComponent.
  • Instant decoding of percent-encoded text from redirects, trackers and email links.
  • Clear errors for malformed percent sequences instead of silent corruption.
  • Handles international text correctly using UTF-8 percent-encoding.
  • Local processing only: long tracking URLs and private parameters stay on your machine.

Best Practices and Tips

  • Encode each parameter value separately, then assemble the URL; never percent-encode an entire finished URL or you will encode its structural characters too.
  • A space can be %20 or ‘+’ in query strings; %20 works everywhere, while ‘+’ is only valid inside query values.
  • When a link breaks after sharing, decode it here to check whether an ampersand inside a value is being read as a parameter separator.
  • Double-encoded values (%2520 instead of %20) are a common bug after passing a link through two systems; decode twice to confirm.

Common Mistakes to Avoid

  • Encoding the whole URL including ‘https://’, which turns the slashes into %2F and destroys the link.
  • Posting unencoded non-English text into an address bar link you share; recipients’ apps may handle it inconsistently.
  • Assuming decoding reveals a link is safe; decoding shows the destination, but you still need to judge whether that destination is trustworthy.

Frequently Asked Questions

What is percent-encoding?

Percent-encoding replaces an unsafe character with a percent sign followed by its two-digit hexadecimal byte value. A space becomes %20, an ampersand becomes %26, and characters from scripts like Arabic or Chinese become several percent-encoded UTF-8 bytes.

What is the difference between the two encode modes?

Full-URL mode preserves the structural characters of a URL ( : / ? & = ) and only encodes what would break it. Component mode encodes those too, which is correct when the text is a single value living inside a URL, such as a search term in a query string.

Why do links from emails look like gibberish?

Email systems and trackers wrap links and encode parameters for safety and measurement. Decoding the link here reveals the real destination and parameters so you can inspect it before clicking or reusing it.

Can I encode an entire sentence for a URL?

Yes. Encode it as a component and it can travel as a query value, share text parameter or path segment. Just remember every special character will expand, so very long text makes very long URLs.

Does encoding change my page’s SEO?

Properly encoded URLs are equivalent to their decoded form for search engines. Problems arise from inconsistent encoding across links, which can split signals between URL variants; keep one canonical encoded form.

Related Tools