Pro URL Encoder & Decoder
Deep percent-encoding with encodeURIComponent and safe reversal with decodeURIComponent—including multi-line URL batches and a quick auto-detect hint.
Input
Paste text or one URL per line. Empty lines are preserved. All processing stays in your browser.
Output
Percent-encoded strings or decoded text (monospace).
Status: Waiting for input
Knowledge base
Why is URL encoding necessary for web development?
URLs are constrained wire formats: spaces, ampersands, hash marks, and non-ASCII text would collide with syntax if sent raw. Percent-encoding lifts arbitrary Unicode into an ASCII-safe representation so servers, CDNs, analytics pixels, and JavaScript fetch calls agree on delimiters. Without encoding, `?q=foo&bar=baz` could misparse when `bar` was meant to be part of the value, or international copy could arrive mangled at upstream proxies.
Modern stacks still lean on encoding when composing deep links, mobile app bridges, Open Graph fallbacks, and webhook callbacks where signatures must stable-serialize query pairs. Treat encoding as hygiene at boundaries: browsers may auto-handle clicks, but programmatic builders must call the same rules your backend validates against to avoid intermittent 400s during traffic spikes.
Common reserved characters in URLs and their encoded values
RFC 3986 reserves characters that structure URIs: `: / ? # [ ] @` separate schemes, authorities, paths, and fragments; `! $ & ' ( ) * + , ; =` carry meaning inside queries. encodeURIComponent escapes most punctuation so those symbols can live inside a parameter value. Space often becomes %20; ampersand becomes %26; hash becomes %23.
Hyphens, underscores, periods, and tildes typically remain unescaped in components, which is why slug generators favor them. When piping values through multiple systems (email → SMS → in-app browser), double-encoding or mixing + versus %20 still causes classic support tickets—always match the consumer’s decoder table.
How URL encoding affects SEO and link sharing
Search engines consume canonical URLs, hreflang alternates, and rendered links. Correct encoding prevents duplicate signals when trackers append parameters: uppercase versus lowercase escapes rarely matter, but broken decoding yields soft 404s and wasted crawl budget on gibberish paths. Social scrapers and chat previews also re-fetch Open Graph URLs—an unescaped ampersand in a campaign link can truncate the URL at share time, erasing UTMs.
For humans, readable paths and short queries still outperform opaque triple-encoded blobs in trust tests, even if both rank identically. Balance marketing clarity with transport safety by encoding only what the protocol demands, centralizing URL builders in code, and snapshotting final strings in QA checklists before launches.
Frequently asked questions
Does percent-encoding preserve UTF-8 and international domain names?
encodeURIComponent operates on UTF-16 code units in JavaScript but emits UTF-8 bytes as percent escapes (for example “é” → %C3%A9). Internationalized domain names additionally use Punycode in the host (xn--...) per IDNA. This tool focuses on component/query encoding—pair it with your DNS or browser APIs when normalizing full IDN hosts.
What are practical limits for query string length in 2026?
There is no universal spec limit, but stacks impose them: older IE-era ~2 KB cautions, many CDNs and reverse proxies accept several KB to tens of KB, while brittle analytics beacons still warn near 8 KB. Prefer POST with JSON for large payloads; use short opaque IDs in URLs; monitor 414 URI Too Long from your WAF when campaigns append giant UTM matrices.
When should I use encodeURI instead of encodeURIComponent?
encodeURI is meant for entire URIs and leaves `;,/?:@&=+$#` reserved characters intact so the structure survives. encodeURIComponent targets query components or fragments where `/`, `?`, `&`, `=` and more must be escaped. Feeding a full URL through encodeURIComponent will escape slashes—useful when the entire string is a nested value, not when preserving path delimiters.
Why do some APIs expect + instead of %20 for spaces?
application/x-www-form-urlencoded historically treats `+` as space while decodeURIComponent expects `%20`. Libraries often normalize one to the other. Mixing modes between client and server causes subtle bugs in OAuth, payment webhooks, and legacy CRM parsers—always match the decoding table documented by your receiving endpoint.
More tools
Encode binary payloads, craft metadata, and keep campaigns composable.