URL Encoder
Percent-encode text for safe URL use. Component or full-URL mode.
EncodeURIClient-sideFree to use
0 / 500,000
Try It Out
How to use
- Paste your string. Any text with special chars.
- Pick mode. Component (strict) or full URL (preserves reserved chars).
Common use cases
- Building safe query string values
- Encoding path segments
- Preparing webhook payloads
Frequently asked questions
- What is the difference between Component and Full URL mode?
- Component mode is strict (encodeURIComponent): it escapes every reserved URL character including / : ? & = #, which is correct when the value will become a single query parameter or path segment. Full URL mode (encodeURI) preserves those reserved characters so a complete URL stays usable.
- Which characters get percent-encoded?
- In Component mode, anything except the unreserved set (A-Z a-z 0-9 - _ . ~) is encoded. In Full URL mode the URL reserved set (; , / ? : @ & = + $ # plus !*\'()) is preserved unchanged.
- How are non-ASCII characters handled?
- Text is first UTF-8 encoded into bytes, then each byte is percent-encoded. Emoji, Chinese, accented Latin, and other non-ASCII characters all round-trip correctly when the decoder uses the same UTF-8 convention (RFC 3986 + WHATWG URL).
- When should I use URL encoding vs Base64?
- Use URL encoding when the result needs to live inside a URL or HTTP header. Use Base64 when binary or arbitrary text needs to travel through a text-only channel that does not specifically expect URL syntax.
- Does this run in the browser?
- Yes. Encoding uses encodeURIComponent / encodeURI locally; the input never leaves your machine.
Related tools
How to use
- Paste your string. Any text with special chars.
- Pick mode. Component (strict) or full URL (preserves reserved chars).
Common use cases
- Building safe query string values
- Encoding path segments
- Preparing webhook payloads
Frequently asked questions
- What is the difference between Component and Full URL mode?
- Component mode is strict (encodeURIComponent): it escapes every reserved URL character including / : ? & = #, which is correct when the value will become a single query parameter or path segment. Full URL mode (encodeURI) preserves those reserved characters so a complete URL stays usable.
- Which characters get percent-encoded?
- In Component mode, anything except the unreserved set (A-Z a-z 0-9 - _ . ~) is encoded. In Full URL mode the URL reserved set (; , / ? : @ & = + $ # plus !*\'()) is preserved unchanged.
- How are non-ASCII characters handled?
- Text is first UTF-8 encoded into bytes, then each byte is percent-encoded. Emoji, Chinese, accented Latin, and other non-ASCII characters all round-trip correctly when the decoder uses the same UTF-8 convention (RFC 3986 + WHATWG URL).
- When should I use URL encoding vs Base64?
- Use URL encoding when the result needs to live inside a URL or HTTP header. Use Base64 when binary or arbitrary text needs to travel through a text-only channel that does not specifically expect URL syntax.
- Does this run in the browser?
- Yes. Encoding uses encodeURIComponent / encodeURI locally; the input never leaves your machine.