Use this text operation when its stated character encoding, token boundaries, normalization, case handling, and output format match the surrounding workflow.

Form-encoded text

Required string.

The cited overview of Percent-encoding supplies background for the terminology and domain context used by this tool.^[1]

Decode ordered UTF-8 application/x-www-form-urlencoded pairs, preserving duplicate names and treating plus signs as spaces. Inputs are interpreted exactly in the displayed units and the calculation returns the following fields without presentation rounding.

Field names

Returned list.

Field values

Returned list.

• Unicode normalization, locale, grapheme clusters, malformed input, ambiguous syntax, and implementation-specific conventions can change text-processing results.
• Use finite inputs in the displayed units, preserve source measurements and assumptions, and independently verify consequential decisions.

Preserve the original text, test representative non-ASCII and malformed cases, and use a standards-aware parser or serializer when interoperability matters.

• Form URL-Encoded Encoder

  Serialize ordered UTF-8 name/value string pairs in application/x-www-form-urlencoded form, using plus signs for spaces.

• Referrer Policy Parser

  Select the last recognized token from a comma-separated Referrer-Policy header while preserving an empty result if none is recognized.

• Vary Parser

  Parse a Vary response header as a case-insensitive set of field names or the single wildcard value.