Repeater Fields

Under collection settings, where you can add fields for each project, it'd be great to be able to add a repeater field. This would function like Advanced Custom Fields in Wordpress, so that in the CMS settings you could add an image repeater field. Then, in the user side of the CMS, you could add an image and have a button for 'add another image'.

ACF Repeater field:

CraftCMS Matrix field: 

I've run into this issue trying to use the CMS for a portfolio and hitting a 31 field limit.

  • Nick Woods
  • Jan 24 2017
  • Manuel Engler commented
    10 Nov 11:47am

    This is needed so badly!

  • Jonathan Wagoner commented
    25 Oct 06:42pm

    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.

  • Ron Biton commented
    7 Sep 03:29pm

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

  • Jon Burdon commented
    6 Sep 01:18pm

    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...

  • Marc Ricketts commented
    18 Aug 07:36pm

    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.

  • Sebastian Frommberger commented
    18 Aug 11:19am

    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.

  • Build Web Studio commented
    13 Jul 06:12am

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

  • Dylan Colby commented
    21 Jun 04:05pm

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

  • Renee Martin commented
    21 Apr 06:02am

    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.

  • Ryan commented
    30 Mar 11:29pm

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

  • Wernich commented
    25 Feb 08:50am

    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?!







  • Moshe Morris commented
    17 Jan 05:47pm

    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.

  • Yuki Tsuji commented
    18 Dec, 2021 06:59am


  • Rick Erickson commented
    2 Dec, 2021 05:03pm

    It'd be in Webflow's best interest to add this functionality while Editor X is still maddeningly buggy (perhaps fatally broken) for sure!

  • Nelson C. commented
    13 Sep, 2021 10:53pm

    This is a must need to build scalable CMS pages

  • Yigit Arslan commented
    19 Jul, 2021 10:34am

    This would be a game changer for all Webflow users. Please make this happen.

  • Rob Nichols commented
    6 Jul, 2021 07:28am

    Still really want this feature.

  • Agustín Moglie commented
    2 Jul, 2021 09:54pm


  • KR RT commented
    23 May, 2021 08:48pm

    Very surprised that this feature has been requested for 4 years - and still no update

  • David Stolarik commented
    2 Mar, 2021 07:27pm

    + 1

  • Load older comments
  • +152