URL Encoder
Percent-encode text as a URI component.
About this tool
The page encodes the text you paste so it can sit in a query value or a path segment. It does not assemble a URL around it.
Decode is the reverse for a component that was encoded this way.
How to use it
- Paste the text.
- Encode.
- Copy the component. It is not wrapped in a full URL.
Limitations
- The operation is encodeURIComponent. Characters that are allowed in a component stay readable. The rest are percent-encoded UTF-8.
- The result is a component, not a complete URL with a scheme and host.
A URI component, not a secret
What encodeURIComponent keeps readable
The encoder runs the browser’s encodeURIComponent on the whole box. Bytes that are unreserved, plus hyphen, underscore, period, exclamation mark, tilde, asterisk, apostrophe, and parentheses, stay as characters. Everything else becomes a percent escape of the UTF-8 bytes, and a space is %20 rather than a plus. A question mark, hash, slash, ampersand, or equals sign is escaped too, so a full address pasted here collapses into one component. The function does not wrap a scheme or a host around that component, and it does not assemble name/value pairs the way a form body would.
Percent text is a spelling of the same bytes. There is no key, and a reader who understands the escapes recovers the original without guessing. Confidentiality needs a cipher. Matching an old checksum needs a hash or a CRC. This box only changes representation so the value can sit inside a query or a path segment.
When the call fails, and when a second pass changes the text
A lone surrogate makes encodeURIComponent throw, and the panel reports that exception instead of a half-written escape. Ordinary letters, digits, and the marks listed above never throw. Encoding a string that is already percent-encoded is a quiet loss: each percent sign becomes %25, so a later single decode peels only one layer and leaves the escapes visible. Do that only when a downstream parser will decode twice.
Characters the function is allowed to leave literal are not forced into escapes. “cafe” stays four letters. An accented letter grows a multi-byte escape because the underlying bytes are UTF-8, not a Latin-1 code unit. The same input always yields the same component. Nothing is stored, and the operation is not a signature over the text.
What a later decode will and will not restore
Encoding and then decoding with the component rules returns the original characters, including spaces and non-ASCII letters. The escape string itself is not a stable fingerprint of a hand-written encoding. Hex from this function is uppercase. A hand-written lowercase escape, or an escape of a character this function would have left literal, will not match the encoder’s output even when both decode to the same text. Compare decoded characters when the meaning matters. Compare the escape bytes only when the next hop expects this function’s exact spelling.
The decoder, not this box, is what rejects a stray percent sign. This box’s job is to emit well-formed escapes. It will not warn you that you encoded a whole URL by mistake; the result simply stops being a URL.
Privacy
Your input is processed in your browser and is not uploaded to UtilChain. File names, text, and results are not sent to analytics.

