How to use
- Paste text, open a file, or try the sample.
- Choose the format. The result updates as you type.
- Copy the result or download the converted data.
Understanding URL encoding
Percent-encode text for a URL component, an entire URI, or a form value. The default is a component, such as a query parameter value.
The three modes preserve different punctuation. Encode a single value rather than concatenating raw user input into a URL.
Encode one component
Component mode uses encodeURIComponent semantics. It escapes separators such as /, ?, & and = while keeping letters, digits and the punctuation allowed by that operation.
hello world + café/?hello%20world%20%2B%20caf%C3%A9%2F%3FThe default settings convert this input in one pass.
Full URI and form values
Full URI mode follows encodeURI and retains URI delimiters. Form value mode follows application/x-www-form-urlencoded: spaces become +, literal plus signs become %2B, and only letters, digits, *, -, . and _ stay unescaped.
Avoid accidental double encoding
Already encoded % signs become %25. Convert the original value once. This tool encodes text; it does not validate a URL, resolve a hostname, parse a query string, or make network requests.
Up to 5 MiB of input, 20 MiB of output, and 10 seconds per run. Text files must use UTF-8. Base64 encoding also accepts binary files. Documents stay on your device.
Frequently asked questions
Which mode should I use for a query parameter?
Use Component for one parameter value. Use Form value when your receiving system expects + for spaces.
Should I encode an entire URL with Component?
No. It also escapes the separators. Full URI preserves URI structure.
Why did % become %25?
A literal percent sign is encoded too. Start with the original value to avoid double encoding.
Are emoji supported?
Yes. Percent sequences represent the UTF-8 bytes of the text.
Does this check whether a URL is safe?
No. Encoding does not validate a destination or make untrusted URLs safe.