I admit that this feature is a major weakness of Webflow. You can always use an auxiliary collection and employ a multi-reference field, which somewhat addresses the issue. I think this stems from the limit of fields per collection or from the limit of elements in the CMS.

This is basic CMS feature, it is unbelievable that Webflow does not have that in 2023.

OOf! This would be REAL nice feature!

Looking into the viability of Webflow for my agency and this is a major blocker. I don't think I've ever created a site without leveraging repeater fields. Surprised this one doesn't have more votes.

This feature request has been open since 2017! It's nigh impossible to build a flexible content management experience without repeater fields. I find myself constantly needing workarounds to bend Webflow CMS to my client's needs. Multi-reference fields only get you so far, and then there is the infamous "One nested CMS collection per page" limitation to contend with. Man do I miss WordPress and ACF sometimes.

Was just looking for this feature and surprised it wasn't already part of the webflow functionality.

Agreed, crazy that this hasn't caught on yet but they're already thinking about making their CMS multilingual while they haven't even addressed the basic needs of a good functioning CMS...

Repeater Fields are not a nice to have, it's a must-have, almost a necessity. Everybody would gain from Repeater Fields and it would speed up the workflow dramastically of almost all Webflow Users working on a CMS Website, while not everyone would gain from the multilingual CMS necessarily.

Some food for thought.

That this isn't addressed yet is a joke. Claiming to be one of the most user friendly & powerful CMS's that doesn't even have repeater fields for clients to use. This is very much required for almost every project. Especially for managing images on a lot of projects...

This is needed so badly!

Really need this as well. Also pretty shocked this isn't something even being reviewed as it's pretty common for a CMS.

I'm building out a sports website and I need to be able to show event scores. So I need a way for the content editor to reference a player and their score and keep adding that combo (player/score) for as many players were in that event. The player coming from a reference field within another collection, and a score being a number field. Not really sure there is a way currently to do this since each event could have different players, different scores, and a different amount of players.

Cmmon how come this is not part of it. I was excited using Webflow for exacly 15 minutes until I realized that.

PLEASE can we have this. For dynamic sites it's absolutely essential. The multi image field is the closest thing we have and it's just like having your hands tied.

Yes - that comment from July highlights the real frustration here...

I think that this is basic. Instead of having to predict the number of whatever something that a user will want to include on their page, or duplicate that field with 1, 2, 3, ... up to the limit of fields allowed, the user can simply click to add an additional whatever something.

This needs way more votes! Advanced Custom Fields is such a great example of how to set up dynamic and intuitiv collections for editors without over expanding an collection item.

Praying Webflow reviews this.. Really struggling with some pretty straightforward client CMS requests.

We NEED dynamic page zones like this to create custom page layouts in the CMS. This is CRUCIAL to Webflow.

This should get a high priority - every site I have built with WP uses ACF repeating fields. Am currently evaluating Webflow and have purchased a subscription to create a proof of concept. This, along with inability to create hierarchal categories may be show stoppers.

(I posted this over on the forums, but thought it worth saying here, too)

We started testing Webflow at our agency for use with smaller client sites and it's pretty cool, but I agree with folks who are coming from CMSs like Craft CMS, Statamic, WP with/ACF, or even ExpressionEngine - if you've never used a "repeater" ("matrix") field, you don't know what you're missing.

So far the Webflow CMS seems pretty good, at least for more basic type sites than we typically build with these other systems. I think the lack of a repeating fieldtype is a pretty big drawback and hampers what you can set the CMS up for. If you have to rely on RTF's for content, it should be a more advanced RTF than I'm seeing in Webflow currently.

We're currently reviewing Webflows limitations to see if our agency should incorporate it in into out stack. I have to say this one surprised me. So for a client to manage simple product details with repeater fields is not possible?!

I second (and third and fourth, etc) the want/need for this feature.

What's more, I am wondering why this request hasn't even been reviewed (at least there is no "reviewed" tag on this suggestion). There are requests with literally only 1 vote that are marked with the review tag. Indeed, there are requests with only 1 vote that have a tag of "planning" and some with as little as 11 votes that are "in development".

And yet, this is a 4 year old request with over two hundreds votes that would greatly improve the power and flexibility of the webflow cms.

As such, I would like to please request that you take (another?) look at this request as well as write an update on what are webflows plans vis-a-vis this request.

Thanks :).

P.S. I should add that there are projects that I would start today on webflow if only they had this feature. It seems that I'm not the only one.