Webflow currently maintains a hard limit of 1 level of nested collection lists, and as of now, there is no public roadmap or official confirmation that this restriction will be lifted in the near future.
1. Current Nesting Limitation
- You can only nest one Collection List within another on a CMS page—for example, showing job categories with nested job posts.
- This limitation is often problematic for projects like job boards, real estate directories, or e-commerce catalogs where multi-level relationships are necessary.
- Attempting to nest beyond one level will result in a validation error within the Webflow Designer, preventing additional nested structure.
2. Workarounds for Nested Structures
- Use Multi-reference fields creatively by flattening structure; for example, show child collections with linked filters instead of real-time nested lists.
- Reference dynamic data using custom code (e.g., fetching additional CMS items client-side with JavaScript and Webflow CMS API).
- Some users rely on third-party integrations like Jetboost, Wized, or Outseta to provide dynamic rendering beyond Webflow’s native nesting.
- Convert pages to static + API-fed pages—this allows near-unlimited flexibility, but reduces CMS manageability inside Webflow.
3. Community & Feature Requests
- This nesting limitation is one of the most upvoted feature requests on the Webflow wishlist (wishlist.webflow.com).
- You can follow and upvote relevant requests to get notified if there’s progress.
- Webflow staff occasionally addresses high-demand features in quarterly updates or livestreams, though no ETA has been mentioned regarding increased nesting flexibility as of early 2024.
Summary
Webflow still enforces a 1-level nesting limit for Collection Lists with no announced plans for expansion. For now, use workarounds like multi-references, third-party tools, or client-side scripts to simulate deeper nesting in CMS-driven designs like job boards.