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.

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  

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 :-(

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'm waiting for this feature.