Option / Select Fields

What is an option field?

An option field (called "select" in some platforms) lets editors choose one value from a fixed list of choices. The list is defined when you create the field — editors pick from your predefined options, they cannot type in new values.

When to use an option field

Option fields are ideal when:

• The list of choices is short (under 10-15 items).
• The list rarely changes — you are not adding new options every week.
• Each option is a simple label — it does not need its own image, description, or page.
• You want to filter or sort by the value.

Common uses

• Status: Draft, In Review, Published, Archived
• Category: Blog, Tutorial, Case Study, News (when you have fewer than 10)
• Priority: Low, Medium, High, Urgent
• Type: Full-time, Part-time, Contract, Freelance
• Difficulty: Beginner, Intermediate, Advanced

Option vs. reference

This is one of the most important architectural decisions in CMS design. Both option fields and reference fields let you categorize content, but they work very differently.

Consideration	Option Field	Reference Field
Data stored	A label (string)	A pointer to another collection item
Additional data	None — just the label	Any fields you want (image, description, URL, etc.)
Own page	Cannot have its own page	Can have its own page (/categories/design)
Maintenance	Edit the field definition to add/remove options	Add/remove items in the referenced collection
Shared across collections	No — each field has its own list	Yes — multiple collections can reference the same collection
Filtering	Supported in Webflow collection lists	Supported in Webflow collection lists

When to upgrade from option to reference

Start with an option field and upgrade to a reference when any of these become true:

1. You need more data per option — a category needs an icon, color, or description.
2. Options are shared — both Blog Posts and Case Studies use the same set of categories.
3. Options need their own pages — you want a /categories/design page that lists all design content.
4. The list grows — once you pass 15-20 options, a reference collection is easier to manage.
5. Non-technical editors manage the list — adding items to a collection is easier than editing field definitions.

Webflow-specific behavior

Editor experience

In the Webflow CMS editor, option fields render as a dropdown select. Editors click the dropdown and choose from the predefined list. It is fast and familiar.

Collection list filtering

Unlike switch fields, option fields do support filtering in Webflow collection lists. You can set a collection list to "only show items where Category is Tutorial" directly in the designer. This makes option fields excellent for creating filtered views of content.

Conditional visibility

You can also use conditional visibility with option fields: show an element only when Status equals "Featured", for example.

Setting up options

Keep options consistent

Define your options with consistent formatting:

• Use title case: "In Progress" not "in progress"
• Avoid abbreviations: "Information Technology" not "IT" (unless the abbreviation is universally understood)
• Keep labels short: "Blog" not "Blog Post Article"

Plan for the future

Think about whether your list might grow. If you start with 5 categories and expect to add more every month, consider using a reference field from the start.

Default values

Set a default value when most items will share the same option. For a Status field, "Draft" is a sensible default. This saves editors a click on every new item.

Sync considerations

When syncing between Airtable and Webflow:

• Airtable single select maps to Webflow option fields.
• Option values must match exactly — "In Progress" and "In progress" are treated as different values.
• Trellis validates option values during the mapping step and warns you about mismatches.
• New options in Airtable that do not exist in Webflow will cause sync errors unless you add them to the Webflow field definition first.

Tips

1. Start with options, upgrade to references — it is easier to start simple. You can always migrate to a reference field later when the list grows or needs richer data.
2. Use for filtering — option fields are one of the best ways to create filtered collection lists in Webflow. "Show all events where Type is Workshop" is a common and powerful pattern.
3. Limit to 10-15 options — if your list is longer, it probably deserves its own collection with a reference field.
4. Document your options — keep a list of valid options and their meanings. "Active" vs "Live" vs "Published" can confuse editors if not clearly defined.
5. Avoid using options for data that belongs elsewhere — if you find yourself putting "John Smith" as an option value, you need a reference to a People collection, not an option field.