About URL encoding
When you put text into a URL — a search term, a redirect target, an API parameter — characters such as spaces, ampersands and non-English letters must be percent-encoded so the link stays valid. This tool does that in both directions, with two scopes: component for a single query value or path segment, and full URL to encode an entire address without breaking its structure. It handles UTF-8 and never uploads your text.
Frequently asked questions
- What is URL encoding?
- Replacing unsafe URL characters with a % and hex digits so the link stays valid.
- Component vs full-URL encoding?
- Component escapes reserved characters for one value; full-URL keeps them so a whole URL stays intact.
- Is my text sent anywhere?
- No — it runs locally in your browser and works offline.
Why URLs cannot hold every character
URL encoding is governed by the RFC 3986 standard, which dictates how data is represented within a Uniform Resource Identifier. The core mechanism involves replacing non-alphanumeric characters with a percent sign followed by the two-digit hexadecimal representation of the character's ASCII or UTF-8 value. While basic letters and numbers remain unchanged, characters like spaces, symbols, and non-Latin scripts are transformed into this encoded format to prevent them from being misinterpreted by web servers or browsers as structural delimiters.
The process relies on the underlying byte sequence of a character. For standard ASCII characters, the mapping is direct and predictable. For multi-byte characters, such as emojis or non-English alphabets, the system encodes each individual byte of the UTF-8 sequence using the percent-hexadecimal format. This ensures that the original binary data remains intact during transmission, allowing the receiving server to reconstruct the exact string by reversing the process once the bytes are received and interpreted.
The most common mistake users make is applying the wrong encoding scope to their data. Attempting to encode an entire URL string using component-level rules often results in the destruction of essential syntax, such as forward slashes, question marks, and hash symbols that define the URL structure. Conversely, failing to encode a single query parameter can lead to broken links if the input contains reserved characters like ampersands or equals signs. Always distinguish between encoding a single piece of data and preserving the integrity of an existing URL path.