Why you should avoid using List fields in your form

The List field in Gravity Forms is a handy way to let users add multiple rows of related information without having to create dozens of separate fields. It’s quick to set up, keeps your form compact, and works well for collecting simple, repeating data, like adding multiple names and email addresses, listing ingredients for a recipe, or capturing step‑by‑step instructions. So why is it not ideal?

Why not use List fields?

The reason? List fields store data in an inflexible way in the database called "serialization". While this works fine for simple uses, it creates challenges when you want to:

• Control how that data is displayed in GravityView
• Search for specific field values
• Sort by values
• Reorder items

Exporting List fields also isn't great…

Another limitation is in exporting. When you export entries with List field data, the output is a long, hard‑to‑read string rather than a nicely formatted table. This can make reporting, sharing, or importing that data into other systems a frustrating process.

We recommend Nested Forms instead.

The List field is essentially a type of repeater field (it allows multiple rows of related information) but it’s not the most powerful or flexible option available.

If you need more control, a better alternative is Nested Forms from Gravity Wiz. Nested Forms let you embed a form within another form, giving you a cleaner database structure, better display options in GravityView, and far more flexibility for exporting and integrating with other tools.

What are other options?

For a full breakdown of repeater field options and best practices, Gravity Wiz has published an excellent resource: Gravity Forms Repeaters: The Ultimate Guide. It covers the pros and cons of each approach, along with practical examples to help you choose the right solution for your needs.