URL Encoder
Encode text and URLs using percent-encoding. Choose from encodeURIComponent, encodeURI or full percent-encoding. Live character encoding map shows what changed.
✅ Free ⚡ Live 🗺️ Encoding Map 🔒 Private
🌐
URL Encoder ⚡ Live⚡
Live Encoding
Output and encoding map update in real time as you type.
🎛️
3 Encoding Modes
encodeURIComponent (recommended), encodeURI (preserve URL structure), or full percent-encode.
🗺️
Character Map
See exactly which characters were encoded and their percent-encoded equivalents.
🔒
100% Private
All encoding runs in your browser using native JavaScript APIs.
⭐ User Reviews
A
Alex T.
Yesterday
⭐⭐⭐⭐⭐
Saved me hours. The live conversion and character counter are exactly what I needed for debugging API payloads.
Encoder ToolsS
Sofia K.
2 days ago
⭐⭐⭐⭐⭐
Super clean interface. The stats panel showing input vs output size ratio is incredibly useful for understanding encoding overhead.
Encoder ToolsD
Dan M.
3 days ago
⭐⭐⭐⭐⭐
I use this daily for development work. Fast, private, no ads. The sample button lets me test edge cases instantly.
Encoder ToolsL
Laura B.
1 week ago
⭐⭐⭐⭐⭐
Handles Unicode and special characters perfectly. The error messages are clear and tell me exactly what went wrong.
Encoder Tools📖 How to Use
1
Paste your text or URL
Enter the text or URL component you want to encode.
2
Choose encoding mode
Select encodeURIComponent for query params or encodeURI for full URLs.
3
Review the map
Check the character encoding map to see what was changed.
4
Copy the output
Click Copy Encoded to get the percent-encoded result.
🎯 Related Tools
❓ FAQ
What is the difference between encodeURIComponent and encodeURI?+
encodeURIComponent encodes everything except A–Z, a–z, 0–9, -, _, ., ~, !, *, ', (, ). Use it for individual query parameters. encodeURI preserves :, /, ?, #, &, = and other URL structural characters — use it for full URLs.
When should I URL-encode text?+
URL-encode text when including it in: query string parameters (spaces → %20), form submissions, API request parameters, redirect URLs, and any text that might contain special characters like &, =, +, or non-ASCII characters.
Why does space become %20 or + ?+
%20 is the proper percent-encoding for space in URLs. + is used in application/x-www-form-urlencoded (HTML form data). encodeURIComponent always uses %20; HTML forms use +. When decoding, you may need to handle both.
What characters are safe in URLs?+
RFC 3986 defines these unreserved characters as URL-safe: A–Z, a–z, 0–9, hyphen (-), underscore (_), period (.), tilde (~). All other characters should be percent-encoded when used in query parameters.
Do I need to encode the entire URL?+
No. Only encode the individual components that need it — typically query parameter names and values. Encoding the full URL (including :// and /) will break it. Use encodeURI mode if you need to encode a complete URL.