About the URL Percent-Encoder & Decoder (URI Component)
Uniform Resource Identifiers (URIs) only permit a restricted subset of ASCII characters (alphanumerics and unreserved symbols like '-', '_', '.', '~'). When URLs include special characters, spaces, non-Latin UTF-8 scripts, or reserved query symbols (like '&', '?', '='), they must be converted into percent-encoded format (such as '%20' for spaces). The URL Percent-Encoder & Decoder converts query strings, path segments, and complete URLs between human-readable text and RFC 3986 compliant percent-encoded strings in real time. Switch between 'encodeURI' and 'encodeURIComponent' modes, batch-process multi-line lists of URLs, decode complex nested query parameters, and export clean strings instantly.
In-Depth Technical Guide
How URL Percent-Encoder & Decoder (URI Component)Works & What the Results Mean
Mechanics of RFC 3986 Percent-Encoding
Percent-encoding represents non-ASCII and reserved characters using hexadecimal byte values preceded by %:
`encodeURIComponent` (Component Mode): Encodes all reserved punctuation characters (/, ?, :, &, =, +, #) into percent codes. This mode is essential when encoding user inputs intended for query string parameter values (e.g. ?search=hello%26world).
`encodeURI` (Full URL Mode): Preserves structural URL protocol and path characters (http://, /, ?, &) while encoding only illegal characters like spaces (%20), quotes, and non-ASCII Unicode characters.
Standard Percent-Encoding Mappings:
Space $\rightarrow$ %20 (or + in form data)
& $\rightarrow$ %26
= $\rightarrow$ %3D
? $\rightarrow$ %3F
/ $\rightarrow$ %2F
# $\rightarrow$ %23
Full UTF-8 Multi-Byte Encoding: Non-ASCII characters (such as emojis or accented foreign text) are converted to multiple percent-encoded byte sequences (e.g. é $\rightarrow$ %C3%A9, 🚀 $\rightarrow$ %F0%9F%9A%80).
Primary Everyday Applications
API Endpoint Construction: Safely passing email addresses, filters, and search queries into REST API query strings.
Tracking & UTM Link Building: Encoding campaign parameters into marketing landing page URLs.
Debugging Web Server Logs: Decoding raw server access logs containing percent-encoded search queries.
Step-by-Step Guide
How to Use URL Percent-Encoder & Decoder (URI Component)
1Paste your raw text, batch URLs (one per line), or percent-encoded URL string into the input editor.
2Select your Operation Mode: 'Encode URL' (Text to %Hex) or 'Decode URL' (%Hex to Plain Text).
3Choose your Encoding Scope: 'Component (encodeURIComponent)' (encodes all reserved symbols) or 'Full URL (encodeURI)' (preserves protocol and query delimiters).
4Inspect the live output and real-time character statistics (Original, Output, Diff, Line Count).
5Click 'Swap Input/Output' to invert inputs or click Copy to copy the result to your clipboard.
Capabilities
Key Features & Highlights
Supports standard RFC 3986 percent-encoding and full UTF-8 multi-byte character sequences (emojis, non-Latin scripts).
Dual scope selection: 'Component (encodeURIComponent)' for parameter values and 'Full URL (encodeURI)' for complete links.
Batch multi-line processing allowing you to encode or decode hundreds of URLs at once while preserving line breaks.
Live real-time character statistics (Original Chars, Output Chars, Character Difference, Line Count).
Instant 'Swap Input/Output' button to flip between encoded and decoded states.
Clear error alert reporting for malformed percent-encoded sequences without erasing user input.
100% in-browser conversion with zero server latency or data tracking.
Practical Scenarios
Examples & Real-World Use Cases
Encoding a Search Query with Special Characters
Scenario: Passing a query parameter containing spaces, ampersands, and quotes to a REST API.
'encodeURI' is designed for complete URLs and does not encode protocol/delimiter characters (such as ':', '/', '?', '#', '&'). 'encodeURIComponent' is designed for individual parameter values and encodes all reserved punctuation to prevent query string corruption.
