URL Encoder
Percent-encode text for safe use in URLs and query strings, as a URL component, full URL or form data, with full UTF-8 support.
Runs in your browserText → URL-encoded text
Loading tool…
Example
name=Ada Lovelace & co
name%3DAda%20Lovelace%20%26%20co
How to use the URL Encoder
- Paste or type your Text into the input area, or open a file from your device.
- Adjust the options above the editor if the tool offers any.
- Review the URL-encoded text result, then copy it or download it as a file.
Privacy and limitations
- Your data is processed on your device and is not uploaded to any server.
Frequently asked questions
What is the difference between URL component and full URL encoding?
Component mode encodes every reserved character (/, ?, &, = …) so a value can be placed inside a query parameter. Full URL mode leaves those characters alone so an entire address stays usable.
Why are spaces sometimes encoded as +?
HTML forms (application/x-www-form-urlencoded) use + for spaces. Choose "Form data" to produce that style; otherwise spaces become %20.
Related converters
URL ParserSplit a URL into protocol, host, port, path, query parameters and fragment, with percent-encoding decoded.JSON to Query StringConvert a JSON object into a URL-encoded query string. Arrays become repeated keys.HTML Entity EncoderConvert special and non-ASCII characters to HTML entities in named (é), decimal (é) or hexadecimal form.URL DecoderDecode percent-encoded URLs and query strings back to readable UTF-8 text, optionally treating + as a space.HTML Entity DecoderDecode named (&, ©, €), decimal and hexadecimal HTML entities back to plain Unicode characters.Base32 EncoderEncode text or hex bytes to RFC 4648 Base32 (A–Z, 2–7), as used by TOTP secrets and other case-insensitive systems.Base32 DecoderDecode RFC 4648 Base32 to text or hex bytes. Padding is optional and lowercase input is accepted.Base58 EncoderEncode text or hex bytes with the Bitcoin Base58 alphabet, which avoids look-alike characters such as 0, O, I and l.