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 level of nesting, and as of now, there are no officially announced plans to increase this limit in the immediate roadmap.

1. Current Nesting Limit

• Webflow allows only 1 nested collection list within a parent collection list.
• This limitation applies across all plans and affects the ability to show deeply related CMS data (e.g., job → category → industry).

2. Why the Limit Exists

• Performance and render optimization are key reasons—multiple levels of nesting can heavily increase page load times, especially with large CMS databases.
• The Designer currently lacks dynamic query logic beyond hierarchical display.

3. Common Workarounds

To handle complex data relationships like those in a job board, consider these approaches:

• Use multi-reference fields directly—show related data (tags, categories, etc.) in a text block using a single reference field instead of nested lists.
• Leverage filters in collection lists—set filters based on page context to simulate deeper relationships.
• Use custom embeds with JavaScript and Webflow CMS API or third-party tools (e.g., Jetboost) to fetch and render deeper nested content outside the limitations of the Designer.
• Flatten relationships using logic (e.g., combine all relevant CMS items into a single reference list) where dynamic nesting isn’t needed.

4. What Webflow Has Said

• Webflow’s team has acknowledged this limitation in forum and wishlist discussions.
• It ranks high on the Webflow Wishlist—with hundreds of votes—but no ETA or official timeline has been confirmed.

Summary

Webflow's current limit of 1 nested collection list remains in place with no confirmed plans to expand it in the near term. For complex CMS structures like job boards, workarounds like multi-reference fields, filtered lists, or JavaScript integrations offer the most flexibility until deeper nesting is supported.