🛠️ Developer · Updated September 24, 2026 · 3 min read

How to URL Encode and Decode Online (Free)

Text / URL Encoded / decoded 🔗

URLs can only contain a limited set of characters. When you need to put a space, an ampersand, a question mark or non-English text into a URL, it must be percent-encoded — turned into codes like %20 for a space. This guide explains what URL encoding is, which characters need it, and how to encode and decode URLs for free.

🔗 Try the URL Encoder / Decoder now — freeOpen →
💡 Why use URL Encoder / Decoder?

Get URL encoding wrong and links break, query parameters get cut off, and form data arrives corrupted. Encoding ensures special characters travel safely inside a URL; decoding turns an encoded URL back into readable text. It's an everyday need when building links, APIs and forms.

What percent-encoding is

URLs reserve certain characters for structure: ? starts a query, & separates parameters, / separates paths, # marks a fragment. To use these characters as data — or to include spaces and non-ASCII text — they're replaced with a percent sign and a code. A space becomes %20, an ampersand becomes %26, and so on.

This keeps the URL unambiguous: the browser and server know that %26 is literal data, not a parameter separator. Decoding reverses the process to show the original text.

Which characters need encoding

Step-by-step

1234
1Open the URL Encoder / Decoder.
2Paste text to encode it for safe use in a URL, or paste an encoded URL to decode it.
3The result appears instantly.
4Copy it into your link, API call or form.

Common mistakes to avoid

⚠️Leaving spaces or & in a query value, which breaks the URL.
⚠️Double-encoding — encoding an already-encoded string turns %20 into %2520.
⚠️Encoding the whole URL including the :// and separators, breaking its structure.
⚠️Forgetting non-English characters need encoding too.

Pro tips

✓Encode only the data parts (query values), not the URL's structure.
✓Watch out for double-encoding when handling already-encoded URLs.
✓Spaces become %20 in paths and often + in query strings.
✓Letters, digits and - _ . ~ are always safe and need no encoding.
✓Everything runs in your browser, so your data stays private.

Frequently asked questions

What is URL encoding?

Replacing characters that aren't allowed in a URL with percent-codes (like %20 for a space) so they travel safely.

Which characters need encoding?

Spaces, reserved characters (? & = # /) used as data, and any non-ASCII text. Letters, digits and - _ . ~ are safe.

Why did my URL break?

Often an unencoded space or & in a value, or double-encoding. Encode only the data parts, once.

Is it free and private?

Yes — free with no sign-up, and it runs in your browser, so nothing is uploaded.

What's the difference between %20 and +?

Both represent a space; %20 is used in paths, while + is common in query strings.

📌 Bottom line

URL encoding keeps special characters and text safe inside links, APIs and forms — and decoding makes encoded URLs readable again. Encode the data parts once, avoid double-encoding, and your links won't break. Free and private in your browser.

Open the URL Encoder / Decoder →

Related guides