Unicode URL Encoder & Decoder
Encode Unicode text to percent-encoded URLs, or decode URL-encoded strings back to text. Ensure your web addresses and query parameters are safe.
Unicode URL Encoder/Decoder
Encode text to percent-encoded UTF-8 for URLs and decode back
Examples
How the Unicode URL Encoder Works
Enter text containing Unicode characters to encode for URLs. The encoder converts non-ASCII characters to percent-encoded UTF-8 sequences.
Unicode characters are first encoded as UTF-8 bytes, then each byte is percent-encoded. For example, 'é' becomes '%C3%A9'. The result is safe for URLs.
Decode percent-encoded URLs back to readable Unicode. The decoder detects UTF-8 sequences and converts back to characters. Handles mixed encoded and plain text.
When You'd Actually Use This
Creating international URLs
URLs with non-ASCII characters need encoding. German 'straße' becomes 'stra%C3%9Fe'. Works in all browsers and servers.
Building API endpoints
API parameters with Unicode? Encode them properly. Prevents request failures. Ensures reliable API communication.
Processing query parameters
Search queries with special characters? Encode for URL inclusion. Decode received parameters. Handle international search terms.
Working with file paths
File URLs with Unicode names? Encode for file:// URLs. Cross-platform file access. Proper path handling.
Debugging URL issues
URL not working? Check encoding. Decode to see actual characters. Identify encoding problems.
Creating shareable links
Links with Unicode titles? Encode for sharing. Works in email, chat, social media. Reliable link sharing.
What to Know Before Using
UTF-8 encoding is standard.Unicode chars are encoded as UTF-8, then percent-encoded. This is the web standard. All modern browsers expect UTF-8.
Some characters don't need encoding.A-Z, a-z, 0-9, and -_.~ are safe. Everything else should be encoded. Don't over-encode.
IDN domains are different.International domain names use punycode (xn--). Not percent-encoding. Different system for domains vs paths.
Double encoding causes problems.%C3%A9 encoded again becomes %25C3%25A9. Wrong! Encode once. Check if already encoded.
Pro tip: Use built-in functions when possible. JavaScript: encodeURIComponent(). Python: urllib.parse.quote(). This tool is for testing and debugging.
Common Questions
Why encode Unicode in URLs?
URLs are ASCII-only by specification. Non-ASCII must be encoded. Percent-encoding is the standard method.
What's percent-encoding?
Each byte becomes %XX where XX is hex. 'é' is C3 A9 in UTF-8. Becomes %C3%A9 in URL.
How do I decode URLs?
Use this tool or built-in functions. JavaScript: decodeURIComponent(). Python: urllib.parse.unquote(). Reverses the encoding.
What about spaces?
Spaces become %20 in URLs. In query strings, sometimes + is used. %20 is more universal.
Do browsers auto-encode?
Modern browsers encode automatically in address bar. But not in JavaScript or APIs. You must encode programmatically.
What characters are safe?
Unreserved: A-Z a-z 0-9 - _ . ~. These don't need encoding. Everything else should be encoded for safety.
Is encoding reversible?
Yes, perfectly. Decoding returns the original Unicode. No information lost. Lossless encoding.
Other Free Tools
Unicode Character Lookup
Unicode Character Lookup
Unicode Text Converter
Unicode Text Converter
Unicode Character Counter
Unicode Character Counter
Unicode Whitespace Remover
Unicode Whitespace Remover
ASCII to Hex Converter
ASCII to Hex Converter: Text to Hexadecimal Translator
Barcode Generator
Free Barcode Generator
Binary to Text Converter
Binary to Text Converter
Free Printable Calendar Maker
Create & Print Your Custom Calendar
Pie Chart Maker
Free Pie Chart Maker Online