Hi Guys,

So its 2020 and this issue seems to be pending from 2017. It would be great to get some feedback as to if this is something in the pipeline. A limit of 20 CMS Collection needs to be fixed, especially with Pro users.

This rule is extremely restricitive and makes my client project impossible to implement on webflow. Even the 60 field is too small. I need 120 to make my project work. Such a shame, I love using WF and wish i could stick to it for this client.

30 is quite restrictive. I'm trying to use Webflow to build a basic product comparison tool for a client and I'm having to cut data fields to meet the limit. Seems a bit silly really.

Increasing the limit from 30 to 50 would be so great! Or even 40... or 35 😁

As a freelancer I'm going to do anything to keep my clients from using webflow because of such dummy constraints 🤦‍♂️

I am currently building a Self-Drive Safari Travel site and am unable to create detailed itineraries within the CMS (there are over 60 itineraries in 12 countries!) - I'm having to cut important info so as to fit the Webflow limit.

I think this is an incredibly important feature and will give designers more freedom to develop more information intensive sites.

Graham Jones nailed this one on the head.

I've upgraded to the biggest plan available - still hitting a wall. UPGRADING DOES NOT FIX THE PROBLEM

I'm using CMS for landing pages, and need the fields to customize each landing page per vertical. Each vertical has A Hero Image, Sub image, Title, Description, CTA, and then all its features, which could be up to 10 features. IS there a way i can add more fields? i don't care how much it costs! (within reason)

I've spent a ton of time migrating my service over to Webflow, and am setting up a CMS collection now, and realizing that it won't have enough fields to allow me to do what I need to do, and it screws me totally. 

I'm waiting for this feature.

I found a similar issue. But as a temporary solution, I created another new collection as a storage and use the first collection refer to the second collection for items such as images or other info.

Example:

Main Collection : Client
Sub Collection 1 : Images
Sub Collection 2 : Categories
Sub Collection 3 : Videos
Etc etc etc.

All other sub collections can be used as reference in the main collection.

This method can expand the limitation of fields in a single collection.

I've had two projects stall recently because of this limitation... In order to deliver a complete site, I need to add in all elements.

Not entirely sure how to proceed other than paying for hosting myself until I'm ready to hand over to my client, but then not sure if that's possible to do once I've set up CMS hosting...

I really wish there were guidelines for stuff like this :-(

Complete agree, I have been chasing Webflow to fix this for a while.

Not only from the point of being easier to build collections, my main complaint is that the current system is unfair.

The current allocation is poorly thought out, take the following as an example.

One client might have one collection that requires 35 fields, but that is the only collection on the site, that means they would need to upgrade to the business hosting just to list the extra 5 items(fields).

Another business could have a collection that only has 30 fields, but have 2000 items listed, and would still only require basic CMS hosting.

So in summary

Business 1: 35 fields, total items 35 – requires business CMS $36pm

Business 2: 30 fields, 2000 items – requires basic CMS $16pm

So the business that is only listing 35 items is having to pay more than double the CMS prices compared to the business that has 2000 items.

Customers find this very hard to stomach!

Thanks Graham  

If possible from a technical point of view up to 100 fields per collection would be great. I'm currently working on a page and 60 fields aren't enough for me.