About URL encoding
URLs can only safely contain a small set of characters, so everything else — spaces, Nepali text, emoji, symbols like & and ? — gets written as percent-codes: a space becomes %20, न becomes %E0%A4%A8. That's why shared links sometimes look like alphabet soup. This tool encodes text for safe use in URLs and decodes percent-encoded strings back to something readable, with correct UTF-8 handling for every language.
How to use it
- Paste your text or URL on the left.
- Pick a mode: Component encodes everything including ?, & and = (right for query values); Full URL keeps the structural characters intact (right for whole addresses).
- Press Encode or Decode and copy the result.
Where you'll need it
- Building links with parameters — a search link for "नेपाल" needs the query encoded or it breaks in many contexts.
- Reading tracking links — decode that monstrous marketing URL to see where it actually goes and what it carries.
- WhatsApp/social sharing links — pre-filled message links (wa.me) require the message text to be component-encoded.
- Debugging web forms and APIs — when a value with an ampersand mysteriously truncates, encoding is almost always the culprit.
Frequently asked questions
When do I use Component vs Full URL mode?
Component mode encodes everything including ?, & and = — use it for a value going inside a URL, like a search query. Full URL mode keeps those structural characters — use it to encode a complete address without breaking it.
Why do spaces sometimes appear as + instead of %20?
Web forms historically encoded spaces as + in query strings, while %20 is the standard elsewhere. The decoder here understands both, so either style decodes correctly.
Does it handle Nepali text and emoji?
Yes — text is encoded as UTF-8, the web standard, so नेपाल becomes %E0%A4%A8%E0%A5%87%E0%A4%AA%E0%A4%BE%E0%A4%B2 and decodes back perfectly.