When to Use Reference vs Option vs Multi-Reference

Three ways to relate content

Webflow gives you three field types for connecting or categorizing CMS items. Choosing the wrong one leads to rebuild work later, so it is worth understanding the trade-offs before you create your first field.

Field type	Stores	Example
Option (Select)	One choice from a fixed list	Blog post → Category ("Engineering", "Design", "Product")
Reference	A link to one item in another collection	Blog post → Author (one author per post)
Multi-Reference	Links to many items in another collection	Blog post → Tags (many tags per post)

Option (Select) fields

An Option field stores a single value from a predefined list — like a dropdown. The list is defined in the field settings, not in a separate collection.

Use when:

• The list is short and rarely changes (under ~20 values).
• Items do not need their own pages, images, or additional metadata.
• You want simple filtering in Collection Lists.

Examples:

• Blog category: Engineering, Design, Product, Announcements.
• Property type: House, Apartment, Condo, Townhouse.
• Status: Draft, Published, Archived.
• Difficulty level: Beginner, Intermediate, Advanced.

Limitations:

• You cannot attach metadata to an option (no image, no description, no URL).
• Renaming an option does not update existing items — you must re-select.
• No dedicated pages per option without custom workarounds.

Reference fields

A Reference field links one item to exactly one item in another collection. It creates a one-to-one or many-to-one relationship.

Use when:

• The related item needs its own page or has its own fields (photo, bio, description).
• Multiple items point to the same related item (many blog posts → one author).
• You need to pull related data into your layout (show the author's photo on the blog post page).

Examples:

• Blog post → Author (each post has one author, but an author can have many posts).
• Product → Brand (each product belongs to one brand).
• Event → Venue (each event happens at one venue).
• Case study → Client (each case study features one client).

How it works in Webflow:

On a Collection Page, you can access the referenced item's fields directly. If a blog post references an Author, you can display the author's name, photo, and bio without duplicating that data.

Multi-Reference fields

A Multi-Reference field links one item to many items in another collection. It creates a many-to-many relationship.

Use when:

• An item can belong to multiple categories, tags, or groups.
• You need to show related items on both sides of the relationship.
• The related items are managed as their own collection (with pages, images, etc.).

Examples:

• Blog post → Tags (a post can have many tags, a tag can appear on many posts).
• Recipe → Ingredients (a recipe uses many ingredients, an ingredient appears in many recipes).
• Course → Instructors (a course can have multiple instructors).
• Property → Amenities (a property can have many amenities).

The 100-item limit:

Webflow caps Multi-Reference fields at 100 linked items per field per item. This is rarely a problem for tags or categories, but it matters for high-volume relationships. If you need more than 100 links, you must restructure — often by flipping the reference direction or using a companion collection.

Performance considerations:

Multi-Reference fields add database joins when Webflow renders the page. On pages with multiple Collection Lists each using Multi-Reference filters, load times can increase. Keep Multi-Reference usage targeted — do not use it for simple categorization that an Option field can handle.

Decision flowchart

Ask these questions in order:

1. Is the list fixed and simple?

Does the list have fewer than 20 entries, rarely change, and not need its own pages or metadata?

Yes → Use an Option field.

Examples: status, difficulty, content type, department.

2. Can each item only belong to one?

Does each item relate to exactly one entry in the other collection?

Yes → Use a Reference field.

Examples: one author per post, one brand per product, one venue per event.

3. Can each item belong to many?

Can an item be linked to multiple entries, and vice versa?

Yes → Use a Multi-Reference field.

Examples: tags, amenities, instructors, ingredients.

4. Will you exceed 100 links?

If yes, restructure. Flip the reference direction so the "many" side holds a single Reference back to the parent. Or use a companion collection for the overflow.

Common mistakes

• Using Multi-Reference for simple categories. If a blog post can only have one category, use a Reference (if categories need pages) or an Option (if they do not). Multi-Reference adds unnecessary complexity.
• Using Option when you need metadata. If your "categories" need images, descriptions, or SEO fields, they belong in their own collection with a Reference or Multi-Reference link.
• Ignoring the 100-item limit. Designing a "Followers" multi-reference on a User collection will break as soon as someone gets popular. Use an external data source for high-cardinality relationships.
• Duplicating data instead of referencing. If you find yourself typing the same author name on every blog post, you need a Reference field to an Authors collection — not a plain text field.

Next steps

• Read Reference Fields for in-depth reference field patterns.
• Read Multi-Reference Fields for advanced multi-reference techniques.
• Read Companion Collections Explained for when you outgrow multi-reference limits.