Use q=blue%20shoes&plus=a%2Bb&symbol=%E2%89%A1 with the component profile. Percent-20 becomes a space, percent-2B becomes a literal plus and the three UTF-8 bytes E2 89 A1 decode to the single symbol ≡. No plus-as-space substitution is needed. Write down the selected profile and compare the source, decoded rows and canonical query together. That evidence makes a later mismatch reproducible without pretending that this parser defines how every server, framework or signature system will interpret the same bytes.

Verify three decoded values

The ordered rows read q → blue shoes, plus → a+b and symbol → ≡. Names are ordinary ASCII here, but QueryLens applies the same strict decoding to names and values. Three pairs and three unique names are reported, with zero repeated names. Keep duplicate names as separate ordered rows until the receiving application states its own policy. Converting early to a plain object can discard values, change their order or hide whether a parameter appeared without an equals sign in the original query.

Canonical output uses uppercase escapes

Canonical component output is ?q=blue%20shoes&plus=a%2Bb&symbol=%E2%89%A1. It preserves pair order, writes spaces as percent-20 and emits uppercase hexadecimal escapes. Canonicalization is deterministic representation, not proof that the original producer used the same spelling. A successful decode only establishes the text produced by these explicit rules. It does not validate a destination URL, authorize a redirect, verify a signature, detect an attack or prove that another implementation applies identical limits and error handling.

Change one byte to see strict failure

Replacing the symbol value with percent-E2-percent-28-percent-A1 creates invalid UTF-8 even though every percent escape has two hex digits. The parser reports an encoding error and emits no partial rows, canonical query or JSON. This differs from a malformed escape such as percent-GG. QueryLens performs the transformation locally and sends no query content to a product backend. Still review copied output before reuse: encoded data can contain identifiers, search terms or other sensitive text, and the destination remains responsible for validation and access control.