Percent-encode one Unicode URI component with encodeURIComponent semantics, explicit context limits, and malformed UTF-16 rejection.
Choose your path
Percent-encode one exact Unicode URI component with encodeURIComponent semantics, rejecting malformed UTF-16 and separating component encoding from complete URLs, form bodies and unrelated escaping or validation contexts.
Encode one value without preserving structural delimiters or guessing the final URL context.
Split the destination into components, enter one value, inspect the percent-encoded output and save the stated context.
Can insert the encoded value at the intended component boundary without double encoding.
Stop URI component encoding from being represented as HTML, SQL, shell, redirect or destination safety.
Read the context warning, review parsing/allowlisting in the receiving system and retain output only as transform evidence.
No security or destination approval is inferred from percent encoding.
Encode multilingual text and emoji while rejecting lone UTF-16 surrogates explicitly.
Use labeled editor/output/copy/save controls and compare UTF-8 percent triplets for boundary fixtures.
Valid Unicode encodes deterministically and malformed text fails with a readable reason.
Outputs and checklists are planning aids. Review the linked current authorities and the records, terms, instructions, and requirements that apply to your exact situation before a consequential decision.
This tool is part of these guided projects. Each project provides step-by-step instructions with checklists and all the tools you need in one place.
Tools you might need next
Decode one percent-encoded URI or form field component with explicit plus handling, strict malformed-input errors, and inert output.
Encode UTF-8 text with RFC 4648 standard or URL-safe Base64 and an explicit padding policy, with strict errors and no encryption claim.
Encode ampersands, angle brackets and quotes as HTML entities. Preview the converted text, copy it, and compare examples before using it in markup.
The focused route treats the full input as one component value. It does not preserve complete-URL delimiters or guess whether the value belongs in a query, path, fragment, or another protocol field.
Malformed lone UTF-16 surrogates are rejected. Valid Unicode is converted according to encodeURIComponent, producing UTF-8 percent triplets for characters outside its unescaped set.
The output records one percent-encoding operation. Re-encoding it can change literal percent signs, and downstream parsing, allowlisting, escaping, and authorization remain separate.
Updated: August 2026
A developer encodes `café + tea` as one value, then inserts it through the application's structured URL builder rather than concatenating a complete URL.
A reviewer proves that slash, ampersand, equals and hash are encoded as data and documents that URL structure was separated before the transform.
An internationalization tester exercises emoji, combining marks and a lone surrogate, confirming valid UTF-8 triplets and an explicit malformed-input error.
Encode exactly one URI component after separating it from URL structure. This Tool does not encode a complete URL or form body and is not HTML, SQL, shell, redirect, or destination validation.