Webflow now supports up to two nested collection lists per page, each of which can show up to 10 items within each parent item.
Simply place one collection list inside of another to create this arrangement.
Why limits matter.
There is frequent frustration in the forums retarding Webflow's nested list limits.
Webflow's CMS is dynamic, it's not a static site generator.
That dynamic capability is what allows you to add items by API, publish/draft CMS items individually, and set date-based conditional filters.
That dynamic server-side generation (SSG) step is expensive because it means large queries and page assembly on every request. If devs were to increase those limits, sites could easily thrash the servers hard, increase hosting costs, and performance would suffer badly.
It's a tradeoff decision.
People wanted to be able to make small CMS changes like edit a blog post, update a price, and to have dynamically updated "upcoming events" pages, without republishing the whole site every 5 mins, and Webflow delivered.
But this also means being mindful of things like;
- Max collections lists per page ( 20 )
- Max items per collection list page ( 100 )
- Max nested lists per page ( 2 )
- Max items per nested list ( 10 )
If you do some basic math you can quickly see the problem.
20 * 100 = max 2,000 un-nested items.
100 * 2 * 10 = another max 2,000 max nested items.
That's 4,000 items that need to queried and integrated into the server side rendering on every page request.
Feels like a solid balance. In my builds, the need for > 2 nested lists is pretty rare and always handled well using an FS nest approach.
