> ## Documentation Index
> Fetch the complete documentation index at: https://docs.alumio.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Parse from form URL encoded

> Converts a Form URL encoded string into a JSON object.

export const FormField = ({property, label, required = false, diType, uiPatterns, children}) => {
  const patterns = Array.isArray(uiPatterns) ? uiPatterns : uiPatterns ? [uiPatterns] : [];
  return <div style={{
    margin: '1.5rem 0'
  }}>
      <div style={{
    display: 'flex',
    alignItems: 'baseline',
    flexWrap: 'wrap',
    gap: '0.5rem',
    marginBottom: '0.25rem'
  }}>
        <strong>{label}</strong>
        <span style={{
    fontSize: '0.7rem',
    fontWeight: 600,
    textTransform: 'uppercase',
    letterSpacing: '0.04em',
    color: required ? '#6241f5' : '#6b7280'
  }}>
          {required ? 'Required' : 'Optional'}
        </span>
      </div>

      <div>{children}</div>

      {diType || patterns.length > 0 ? <p style={{
    fontSize: '0.85rem',
    color: '#6b7280',
    marginBottom: 0
  }}>
          {diType ? <>
              See the <a href={`/references/${diType}`}>{diType}</a> reference.{' '}
            </> : null}
          {patterns.length > 0 ? <>
              Accepts a <a href={`/documentation/placeholders-and-patterns/patterns#${patterns[0]}`}>pattern</a>.
            </> : null}
        </p> : null}
    </div>;
};

Converts a form URL encoded string into structured data. This is the format a web form or a query string uses, where fields are joined with `&` and each field is written as `name=value`, for example `sku=A1&name=Wool+scarf`. Use this when a value in your flow holds such a string, for example the body of a posted form or a captured query string, and you want to work with the individual fields as data you can map and transform.

This documentation describes: [Schema](/schemas/deserializer/form-urlencoded)

## Fields

<FormField property="compatibilityMode" label="Compatibility">
  Chooses how nested and repeated fields are read. "PHP compatible" (the default) understands bracket notation such as `tags[0]=winter&tags[1]=sale` and turns it into a nested list. "Javascript compatible" keeps every field flat, treating the bracketed name as a plain field name. Choose the one that matches the system that produced the string.
</FormField>

<FormField property="encodeInput" label="Input data is not UTF-8 encoded">
  An on/off toggle, off by default, which assumes the incoming text is already UTF-8. Turn it on only when the source text uses a different character set so that accented and other special characters come through correctly. When on, two extra options appear so you can describe the original character set.
</FormField>

<FormField property="encodingFrom" label="Convert from" required>
  Shown only when "Input data is not UTF-8 encoded" is on, and required there. The character set the incoming text is actually saved in, so it can be converted to UTF-8 before parsing. Choose from UTF-16, ISO-8859-1, or Windows-1252.
</FormField>

<FormField property="modifier" label="On unconvertible characters">
  Shown only when conversion is on. Controls what happens to a character that has no UTF-8 equivalent: NONE stops with an error, IGNORE drops the character, and TRANSLIT replaces it with the closest similar character.
</FormField>

## Sample data

| Field         | Value          |
| ------------- | -------------- |
| Compatibility | PHP compatible |

Input:

```
sku=A1&name=Wool+scarf&price=19.95&tags[0]=winter&tags[1]=sale
```

Output:

```json theme={null}
{
    "sku": "A1",
    "name": "Wool scarf",
    "price": 19.95,
    "tags": ["winter", "sale"]
}
```

```json Configuration theme={null}
{
  "prototype": "form-urlencoded",
  "parameters": {
    "compatibilityMode": "MODE_PHP"
  }
}
```