100% local processing — your files and data never leave this browser. No uploads, no server storage.
Free · Browser-only · No upload
Safe query strings and path segments
Encode reserved characters for URLs and query parameters, or decode percent-sequences back to readable text. Helpful when debugging redirects, webhooks, and form submissions.
Choose component encoding (encodeURIComponent) or full URI rules depending on what you are building. Processing is local only.
Encoding scope
URLs allow only a limited set of characters unescaped. Spaces, ampersands, unicode letters, and binary bytes must become percent-encoded %XX sequences.
Without encoding, query parsers break on ampersands in values and servers misread spaces as delimiters.
Decoding reveals what a server actually received after a client or framework transformed the string.
encodeURI leaves reserved characters that structure the URL (/, ?, #) intact while encoding unsafe text—useful for whole links.
encodeURIComponent encodes nearly everything, which is what you want for a single query value or form field.
Decoding with the wrong function can leave stray % sequences or over-decode path slashes.
Copy encoded query strings from browser devtools or server logs, decode here, and compare to the intended parameter map.
Double encoding happens when an already-encoded value is encoded again—watch for %25 (percent) appearing in output.
Plus signs in query strings historically meant space; some frameworks still translate + to space on decode.
UTF-8 bytes appear as percent-encoded UTF-8, not as raw Unicode code points in the URL.
IDN hostnames use punycode in the wire format; this tool focuses on path and query text, not DNS conversion.
Encoded phishing links hide readable domains until decoded—inspect suspicious URLs in a sandbox before visiting.
Never paste live session tokens into shared screens; decoding exposes secrets in plain text.
HTML entity encoder handles < in markup; URL encoder handles %20 in addresses.
Base64 is a different transport layer—some APIs nest both encodings on the same field.
Encode only the value (encodeURIComponent), then assemble key=value& manually. Encoding the entire URL with component rules can break slashes.
Spaces become %20 in modern APIs; avoid raw spaces in production URLs.
If you see %2520, decode once and check whether your framework encodes on output again.
Align server and client: either pass decoded values internally and encode once at the edge, or document the contract.
Common questions
Usually encode individual parameter values with encodeURIComponent. Use encodeURI when you must preserve URL structure characters.
application/x-www-form-urlencoded uses + for space in bodies; query strings in URLs prefer %20.
Legacy %u sequences are non-standard. Modern UTF-8 percent encoding is the expected format.
Yes, but path rules differ slightly from query rules; encode each segment separately in REST APIs.
No server upload occurs; decoding happens entirely in your browser.
Yes. Everything runs in your browser. Your input is not uploaded, logged, or stored on our servers.
No account or sign-up is required. Open the page and start using the tool immediately.