About URL Encoder & Decoder
RFC 3986 compliant URL encoder and decoder handling percent-encoding for query parameters, path components, form payloads, and non-ASCII characters.
Key features
- Dual encoding engines: encodeURIComponent (for query values) and encodeURI (for full URL strings).
- Complete UTF-8 byte sequence percent-encoding for multi-byte Unicode characters and emojis.
- Live decoding of malformed or obfuscated URI strings with clear error detection.
- Space encoding toggle between standard percent '%20' and application/x-www-form-urlencoded '+'.
How to use
- Select Encode or Decode Mode: Choose whether to percent-encode plain text or decode percent-escaped URLs.
- Paste URL or Query String: Input your parameter string, endpoint URL, or JSON payload into the editor.
- Copy Safe URL String: Review the encoded or decoded output and copy it for use in HTTP requests or API clients.
FAQ
What is the difference between encodeURI and encodeURIComponent?
encodeURI preserves URL structure characters like / ? : @ &, whereas encodeURIComponent escapes them, making it safe for query parameters.
What is percent-encoding in RFC 3986?
A mechanism where reserved or unsafe characters are replaced by a '%' followed by their two-digit hexadecimal ASCII/UTF-8 byte value.
Should spaces be encoded as %20 or +?
'%20' is the strict RFC 3986 standard for URL paths and queries, while '+' is used in legacy application/x-www-form-urlencoded forms.
Are my query strings or secret API keys safe?
Yes, all encoding and decoding runs 100% locally in your browser memory without network logging.