Percent encode a URL component so special characters stay part of its value. Prepare query values without confusing them with URL separators.
How to use
Enter only the component you need to encode. Copy the output into the appropriate part of your URL rather than encoding the full address.
Example
red & blue becomes red%20%26%20blue. The ampersand is encoded so it cannot split the value into separate query parameters.
FAQ
Should I encode a full URL?
No. This component encoder also escapes structural characters such as : and /. Encode individual values before assembling the address.
Related tools
A practical task
Encode a query value before combining it with parameter names and separators. A search phrase with spaces, ampersands, or non Latin letters needs component encoding so those characters stay inside the value instead of changing address structure.
Another useful question
Can I encode a value that is already encoded?
That encodes its percent signs again. Start from the original decoded value unless the receiving format explicitly requires another encoding layer.
Details for interpreting the result
| Detail | Explanation |
|---|---|
| URL components | A URL contains structure such as scheme, host, path, query, and fragment. Characters that separate those parts differ from characters inside a value. Encode the right component rather than transforming the full address blindly. |
| Percent encoding | A percent escape represents a byte with two hexadecimal digits. It does not describe a visible character directly. Several escapes can belong to one Unicode character encoded with multiple UTF8 bytes. |
| Query values | Query separators connect parameter names and values. An ampersand inside a value must not be confused with the separator between parameters. Build the URL with correct component encoding before sharing it. |
| URL fragments | A fragment points to a location within a resource and is normally not sent as part of the server request. It differs from a query parameter. Changing it does not necessarily create a different document for canonical selection. |
| UTF8 bytes | UTF8 encodes characters as bytes. Basic Latin letters use one byte each, while many accented letters and other scripts use more. A byte count therefore differs from a visible character count. |
| Encoding and encryption | Encoding changes how data is represented so another system can read it. It does not require a secret key. Encryption protects information with a key, while hashing produces a digest for a different purpose. |
| HTML character references | Character references such as & describe a character inside HTML. A reference can be escaped again when nested in another source. Decoding one layer is different from decoding every layer of a value. |