Encode special characters for safe URLs and decode percent-encoded strings back to readable text. Free online URL encoder and decoder tools for developers.

Paste a link containing a space, an ampersand, or a character from another alphabet into the wrong place and it breaks. URLs were designed around a limited set of safe characters, and everything else needs to be translated into a format the web understands. That translation is called percent-encoding, where a space becomes %20 and a non-ASCII letter becomes a sequence like %C3%A9. The URL Encoder handles the translation for you, and its companion URL Decoder reverses it.

<

h2>Why encoding exists at all

A URL is really a set of instructions: the address, the path, and then parameters after the question mark. Characters like &, ?, and = already have jobs inside those instructions, so if your actual data contains them, the browser cannot tell data from structure. Encoding marks each special character with a percent sign and two hexadecimal digits, removing the ambiguity. Without it, search boxes, share links, and API calls would constantly misfire.

Encoding a URL in four steps

1. Open the URL encoder and paste the text or link you need to make safe.
2. Run the encoding to convert spaces and special characters into percent sequences.
3. Copy the encoded output.
4. Use it in your link, redirect, or API parameter and test that it resolves correctly.

When you need the decoder instead

Sooner or later you will meet a URL that looks like alphabet soup: long strings of %20 and %2F where readable words should be. That usually means you are debugging a redirect, inspecting an analytics report, or reading a link someone else generated. Paste the encoded string into the URL decoder and it restores the human-readable version, which makes the actual destination and parameters obvious. If you regularly untangle encoded payloads, a Base64 to Text converter covers the other common encoding you will meet.

Encoding mistakes that break links

• Encoding the whole URL: encode the parameter values, not the structure. Turning https:// into https%3A%2F%2F destroys the link.
• Double encoding: encoding an already-encoded string turns %20 into %2520. Encode once, at the end.
• Forgetting non-ASCII text: names and words in other scripts must be encoded too, or servers may reject or misread them.
• Encoding what is already safe: letters, digits, and characters like - _ . ~ never need encoding.

Frequently asked questions

What is the difference between encodeURI and encodeURIComponent?

encodeURI leaves structural characters like : / ? and # alone, while encodeURIComponent encodes everything except basic unreserved characters. For parameter values, the stricter one is usually what you want.

Why do spaces sometimes become + instead of %20?

In form submissions, the older application/x-www-form-urlencoded convention uses + for spaces. In paths and most modern uses, %20 is correct.

Can encoding hide malicious links?

It can obscure them from a quick glance, which is exactly why decoding a suspicious link before clicking is a good habit. Encoding is not encryption and offers no real secrecy.

Do I need to decode URLs before saving them?

Store the canonical readable version when you can, and encode at the moment of use. That keeps your data clean and avoids double-encoding bugs later.

Final thought

Percent-encoding is one of those invisible details that either works silently or breaks loudly. Encode parameter values once, decode when debugging, and never encode the structure itself. With the encoder and decoder bookmarked, garbled links become a thirty-second fix instead of a mystery.