ConverterURL Encode
Choose the destination context before encoding. A URI component and an HTML form value use different space and plus-sign rules.
Encode One Value For Its Context
Enter input to begin.
Context Changes The Output
| Input | Component mode | Form mode |
|---|---|---|
| Hello World | Hello%20World | Hello+World |
| a+b | a%2Bb | a%2Bb |
| a&b=c | a%26b%3Dc | a%26b%3Dc |
One Value, Not A Complete URL Validator
Component mode applies UTF-8 percent encoding suitable for one component value; form mode follows URLSearchParams form serialization for one value.
Encoding does not validate a scheme, hostname, redirect destination, path structure, or trust. Assemble complete URLs with an API that understands their component boundaries.
Avoid Double Encoding
- Encode raw data once at the boundary where its destination is known.
- Do not encode an already encoded percent sign unless a second layer is intentional.
- Keep literal + behavior separate from form-space behavior.
Questions About This Tool
Component mode uses %20. Form mode uses +. The correct choice depends on the consuming context.
No. It encodes one value and does not validate URL structure, schemes, or destinations.
No. It represents bytes for a URL context; validation, allowlists, and output handling remain separate.