URL Component Encoder

Encode the component, not the whole address

A URL is made of structured parts: scheme, host, path, query, and sometimes a fragment. Characters such as ampersands, equals signs, slashes, and question marks can separate those parts. A value inserted into a query parameter may contain the same characters as ordinary data; percent-encoding tells a URL parser to treat them as value content.

For example, if a search phrase contains an ampersand, leaving it unescaped inside a query string could make it look like another parameter begins. Component encoding changes the value representation while leaving the surrounding URL syntax to the code that assembles the address. Encoding the complete URL as one component can instead escape separators that must remain structural.

Spaces, Unicode, and destinations

FormatInstant uses the browser’s encodeURIComponent behavior. It converts Unicode text to percent-encoded UTF-8 sequences where needed. Some server or form conventions represent spaces with a plus sign; that convention is not identical in every URL context. Follow the rules of the receiving API or application and test with a harmless example.

Encoding does not establish that a URL is safe, authorized, or trustworthy. It is not HTML escaping, SQL escaping, encryption, or a defense against phishing. Validate destinations and use the correct parameterized APIs in the system that constructs the final request.

Use the paired decoder to verify

1. Enter only the value that belongs in one URL component.
2. Copy the encoded result into the intended component using a URL builder or documented API.
3. Decode a test value and confirm that the original text returns unchanged.

Use the URL Component Decoder to restore an encoded value. Read the formatting guides for other text-conversion patterns.