Are there plans to increase the nest limit for nested collection lists in Webflow anytime soon? The current limit heavily restricts the functionality on listing type pages and affects the suitability of Webflow CMS for projects like jobs boards.

Webflow currently limits nested collection lists to 1 per page, and as of now, there is no announced plan to increase or lift this restriction. This limitation does affect use cases like job boards, real estate listings, and marketplaces, where showing related dynamic content is essential.

1. Why the Limit Exists

• Performance concerns are the primary reason Webflow enforces the 1 nested collection limit.
• Every nested collection pulls additional CMS queries, which can slow page rendering and increase data load on the frontend.

2. Current Workarounds

To work within the system, here are some common solutions:

• Use Reference or Multi-Reference Fields: Set up relationships using reference fields and display related data via one nested collection.
• Use CMS Filters + Static Sections: Instead of dynamically pulling all related data, create static sections that filter one relationship only.
• Use Custom Code and Webflow CMS API: Embed a script that fetches related items from the CMS using JavaScript + Webflow’s CMS API and renders them manually on the page.
• Break Up Across Pages: If you need multiple nested lists, consider splitting content across multiple CMS template pages or sections.

3. Follow Webflow Updates

• Check the Webflow Wishlist platform (wishlist.webflow.com) for official responses and status updates.
• Follow Webflow’s Product Updates blog and Webflow Forum for any roadmap announcements.

Summary

Webflow limits the number of nested collection lists to one per page, and there’s no official confirmation of plans to lift this cap. For complex relationships, use CMS reference fields, custom code, or break content into multiple sections/pages as workarounds.