URL Encoder
Percent-encode a value so it survives being placed in a URL path or query parameter.
Input
Text- characters
- 0
- lines
- 0
- size
- 0 B
Options
Only correct inside form-encoded bodies, not general URLs.
About this tool
URLs allow a limited character set. Anything else — spaces, ampersands, non-ASCII text — must be percent-encoded as its UTF-8 bytes in hexadecimal. Skipping this is how query parameters get truncated at the first ampersand.
The important choice is which mode to use. Component mode escapes reserved characters such as & = ? / because the value is a single parameter. Full-URL mode leaves the structural characters intact because you are encoding an entire address.
How to use this tool
Paste the text or URL you want to encode.
Choose component mode for a single parameter value, or full-URL mode for a whole address.
Press Encode.
Copy the encoded result into your URL.
Key features
- Component mode escaping all reserved characters
- Full-URL mode preserving :, /, ?, & and #
- UTF-8 encoding for non-ASCII text including Hangul and emoji
- Optional encoding of spaces as + for form-encoded bodies
- Line-by-line encoding for bulk values
- Character and byte counts before and after
Example
Input — Text
blue chair & deskOutput — Encoded text
blue%20chair%20%26%20deskGood to know
- Full-URL mode assumes the input is already a structurally valid URL; it will not repair a malformed one.
- Percent-encoding does not sanitise input. It prevents structural breakage, not injection into other contexts.
- Very long URLs may exceed server or proxy limits regardless of correct encoding.
Frequently asked questions
Component or full-URL mode?
Component mode when you are encoding a single value that goes into a parameter. Full-URL mode when you have a complete address and want to keep its slashes and separators meaningful.
Space as %20 or +?
Use %20 anywhere in a URL. The + form is only correct inside application/x-www-form-urlencoded bodies and query strings that follow that convention.
How is non-ASCII text encoded?
Each character is converted to its UTF-8 bytes and each byte becomes a %XX sequence, which is why one Hangul character produces three escapes.
Should I encode a value twice?
Almost never. Double encoding turns %20 into %2520 and is a common source of bugs where a parameter arrives with literal percent sequences in it.
Your data stays on your device
Your data is processed locally in your browser and is not uploaded to our server. This page keeps working after you go offline, because there is nothing to send.
Related tools
- URL DecodeDeveloper ToolsDecode percent-encoded URLs and parameters back to readable text.Encoded textText
- JSON to Query StringConvertersBuild a URL-encoded query string from a JSON object, including nested values.JSONQuery string
- Base64 EncodeDeveloper ToolsEncode text or files to Base64, with URL-safe and line-wrap options.TextBase64
- HTML EncodeDeveloper ToolsEscape HTML special characters so markup and code display as text.TextHTML entities