Multi-Reference Fields

What is a multi-reference field?

A multi-reference field creates a many-to-many relationship between two collections. Each item can reference multiple items in the other collection, and each referenced item can be referenced by multiple source items.

Examples

• A Blog Post can have multiple Tags (and each tag can appear on multiple posts).
• A Project can involve multiple Services (and each service can appear on multiple projects).
• A Provider can practice at multiple Locations (and each location can have multiple providers).

Single reference vs. multi-reference

Single Reference	Multi-Reference
Cardinality	One-to-one or many-to-one	Many-to-many
Items linked	Exactly one	Zero to many
Example	Blog → Author	Blog → Tags
CMS editor	Dropdown	Multi-select from collection

When to use multi-reference

Use multi-reference when:

• An item can relate to multiple items in the other collection.
• The relationship goes both ways — both collections benefit from the link.
• The related items are real entities with their own fields and pages.

When NOT to use multi-reference

• Simple labels — if tags are just text labels without their own pages or descriptions, use a multi-select field instead. It is simpler and does not require a separate collection.
• Large data sets — multi-reference fields have item count limits in Webflow (depending on your plan). For very large relationships, consider alternative approaches.
• One-way relationships — if only one side of the relationship matters, a single reference might be enough.

Multi-reference vs. multi-select

This is a common decision point:

Use multi-select when:

• The values are simple labels (no additional data).
• You do not need pages for each value.
• The list of options is relatively static.

Use multi-reference when:

• Each value has its own fields (name, description, image).
• Values need their own pages.
• You want to show all related items on each value's page (reverse lookup).

Platform limits

Webflow

• Maximum of 5 multi-reference fields per collection.
• Each multi-reference field can link up to 25 items per CMS item (varies by plan).
• Multi-reference fields cannot be used in conditional visibility for individual items.

Airtable

• Linked record fields support many-to-many relationships with no hard limit.
• Performance may degrade with very large link counts.

Tips

1. Use multi-reference sparingly — it is tempting to link everything, but each multi-reference adds complexity to your data model and potential performance issues.
2. Check your platform limits first — Webflow's 5-field and 25-item limits are real constraints. Plan around them.
3. Consider the editor experience — selecting from a list of 500 items in a multi-reference dropdown is painful. Keep referenced collections manageable.
4. Reverse lookups are powerful — on a Tag page, show all blog posts with that tag. This is the main reason to use multi-reference over multi-select.

Working around the 5-field limit

Webflow's limit of 5 multi-reference fields per collection is one of the most impactful constraints in CMS architecture. Here are strategies for working within it:

1. Convert to single reference where possible

If the relationship is actually one-to-many (each blog post has one primary category), use a single reference instead of multi-reference. Single references do not count against the 5-field limit.

2. Use select/multi-select for simple taxonomies

If your categories or tags do not need their own pages, descriptions, or images, use a multi-select field instead of multi-reference. Multi-select gives you filtering and display without consuming a multi-reference slot.

3. Combine related collections

Instead of separate Tags and Categories collections, combine them into a single Taxonomy collection with a "Type" field. One multi-reference field can then point to both tags and categories, filtered by type in the frontend.

4. Reverse the relationship direction

Instead of adding a multi-reference from Products to Features, add a single reference from Features to Products. Then use a nested collection list on the Product template to display related features. This uses zero multi-reference slots on the Product collection.

Airtable linked records vs. Webflow multi-reference

Behavior	Airtable	Webflow
Item limit per field	No hard limit	25 items (plan-dependent)
Fields per collection	No limit on linked records	Maximum 5 multi-reference
Bidirectional	Automatic	Manual (create field in both)
Filter by linked record	Native (view filters)	Requires Finsweet Attributes
Sort by linked record	Native (rollup + sort)	Not natively supported

When Trellis syncs multi-reference fields from Airtable to Webflow, it resolves the linked record IDs from the source to the corresponding Webflow item IDs in the destination. This requires that all referenced items are synced first, which Trellis handles automatically through dependency ordering.

Common multi-reference patterns

Blog taxonomies

Blog Posts → Tags (multi-reference) and Blog Posts → Categories (single reference). This uses only 1 of your 5 multi-reference slots. Show related posts on tag pages using a reverse nested collection list.

Project portfolios

Projects → Services (multi-reference), Projects → Client (single reference), Projects → Team Members (multi-reference). Uses 2 of 5 slots. On a Service page, show all projects that used that service.

Event management

Events → Speakers (multi-reference), Events → Topics (multi-reference), Events → Venue (single reference). Uses 2 of 5 slots. Speaker and topic pages show upcoming and past events automatically.

E-commerce

Products → Categories (multi-reference for cross-listing), Products → Related Products (multi-reference). Uses 2 of 5 slots. Be cautious — adding colors, sizes, and materials as multi-reference can quickly exhaust your limit.