SEO · Free tool
URL Encoder / Decoder
Encode or decode URLs with the right method — and Base64 too. Five modes covering every common case.
Output
https://www.example.com/search?q=biryani%20in%20%E0%A4%B9%E0%A5%88%E0%A4%A6%E0%A4%B0%E0%A4%BE%E0%A4%AC%E0%A4%BE%E0%A4%A6&page=2
Pick the right encode mode
encodeURI preserves the URL structure (slashes, query separators, fragments). Use it on a whole URL. encodeURIComponent encodes everything including the separators — use it on individual query parameter values you're about to inject into a URL.
Common cases
Encoding Indic / Hindi text for a search query parameter? Use encodeURIComponent. Encoding a whole URL pasted from somewhere with spaces? Use encodeURI. Decoding a tracking link to read its payload? Use decode. Need URL-safe Base64 for an obfuscated token? Use the Base64 modes. Companion tools: the permalink cleaner strips tracking junk, and the UTM builder tags URLs cleanly.
Privacy
- All encoding runs locally in your browser — nothing is sent anywhere.
- Base64 is encoding, not encryption — never use it to store secrets.
- For URL-safe Base64 (no
+//), use server-side libraries.
FAQ
What is the difference between encodeURI and encodeURIComponent?
encodeURI preserves URL structure (/, ?, # stay un-encoded) - use for whole URLs. encodeURIComponent encodes everything including those characters - use for individual query parameter values.
When do I need to encode a URL?
Whenever a URL contains spaces, non-ASCII characters, or reserved characters (?, &, #, +) inside a path or parameter value. Browsers tolerate some unencoded inputs but servers, redirects and analytics tools often do not.
Is Base64-encoded data safe in URLs?
Standard Base64 uses + and / which conflict with URL syntax. Use Base64URL variant (substitutes - and _) for URL-safe encoding. Never put secrets in Base64 - it is encoding, not encryption.