URL Encoder
URL Encoder
Encode text for URLs using URI or URI component modes with line options.
InputsManual input47 charsAuto run
File input
Choose a file
Click, drop, or paste from clipboard.
Options
3
More actions
Manual
ManualEncoded output
0
No output yet.
Live
Manual
Ready
47
Input
0
Output
0
ms
Flow
- Choose encode mode based on whether input is a full URL or a URL component.
- Encode each line separately when handling batches.
- Optional plus conversion outputs + instead of %20 for spaces in form-style payloads.
Example
Worked example: encode query text
- 1 Input text = chemistry tools and stats
- 2 encodeURIComponent converts spaces and reserved symbols.
- 3 Output becomes chemistry%20tools%20and%20stats.
The encoded output is safe to place in URL query parameters.
How
- Enter plain text or URL content in the input area.
- Select encodeURI or encodeURIComponent and any line options.
- Copy encoded output or swap values for quick round-trip testing.
Cases
- Prepare query values before appending to API request URLs.
- Generate encoded redirect URLs for email campaigns.
- Encode multiline payloads for script-based automation.
Avoid
- Using encodeURIComponent on an already encoded value which causes double encoding.
- Choosing encodeURI for raw query values that should use encodeURIComponent.
- Ignoring plus-space behavior when integrating with form-urlencoded endpoints.
Table
| Conversion | Result |
|---|---|
| space | %20 or + |
| / | %2F |
| ? | %3F |
| & | %26 |
| = | %3D |
FAQ
When should I use encodeURIComponent instead of encodeURI?
Use encodeURIComponent for individual parts like parameter values and encodeURI for full URL strings.
Can this tool convert spaces to plus signs?
Yes, enable the spaces-as-plus option for form-style encoding output.
Does this work line by line?
Yes, enable per-line processing for batched text inputs.
Switch
Switch12
No match.