Inspect percent escapes in one component
Paste a percent-encoded component and choose Inspect encoding. The report lists each valid %HH byte with its zero-based UTF-16 offset, hexadecimal spelling and decimal value. It separately reports malformed percent escapes and whether otherwise valid byte escapes fail strict UTF-8 decoding.
Example: accented text and two kinds of spacing
The example caf%C3%A9+tea%20time has three percent-encoded bytes: C3, A9 and 20. Strict component decoding yields café+tea time. The plus remains a plus; this page does not apply form-query plus-to-space rules. The two bytes C3 A9 jointly represent é, while 20 represents one space.
Invalid escapes and decoding failures
A percent sign without two following hexadecimal digits is reported by offset. For example, %G0 is malformed and does not become a byte row. Valid hexadecimal syntax alone does not make a valid UTF-8 sequence: %FF or a truncated multibyte sequence is reported as invalid UTF-8 and no decoded text is provided. The report still exposes syntactically valid byte rows for inspection.
Literal unescaped characters remain in decoded text but do not receive byte rows. A code point may need multiple escaped bytes, so byte rows are not character counts. The table previews 200 rows and malformed offsets; the JSON download contains the complete report.
Scope and limits
Input supports 50,000 UTF-16 code units and at most 5,000 percent tokens, including malformed ones. Unpaired surrogate text is rejected. No URL is visited, and the tool does not decide whether a decoded component is safe to insert into HTML, a shell or a URL path. Use URL Query Difference Viewer for decoded query semantics, or UTF-8 Byte Inspector to inspect all bytes of the decoded text.
Changing any input or option clears the prior result and download. Processing stays in this browser; no source file is changed.





