URL Encoder/Decoder
Encode special characters for safe URL transmission. Essential for query strings, API parameters, and web development.
100% Free — Instant and accurate.
URL Encoder/Decoder
Common Use Cases
Search Queries
Encode user search terms for safe inclusion in URLs and API calls.
API Parameters
Safely pass data in REST API query strings and POST bodies.
Share Links
Create shareable URLs with encoded titles, descriptions, or user data.
mailto: Links
Encode email subjects and bodies for mailto: URL parameters.
URL Encoding Reference
URL encoding (percent encoding) converts characters that are not allowed in URLs into a format that can be safely transmitted.
Common Encodings
→ %20 / +→ %21→ %23→ %24→ %26→ %3D→ %3F→ %40Frequently Asked Questions
When should I encode URLs?
Always encode user input, search queries, or any data used in query strings, paths, or parameters. This prevents breaking URLs and security issues.
What is the difference between %20 and +?
Both represent spaces. %20 is the RFC 3986 standard (universal), while + only works in query strings. Use %20 for paths.
encodeURI vs encodeURIComponent?
encodeURI() preserves URL structure characters (:, /, ?, #). encodeURIComponent() encodes everything except alphanumerics. Use the latter for parameter values.
Do I need to encode the entire URL?
No. Only encode the dynamic parts (query values, path segments). The URL structure (protocol, host, slashes) should remain unencoded.