Skip to main content
Question

Grid: Automatic rows not working / resetting itself

  • June 2, 2026
  • 8 replies
  • 97 views
Julia57

Figma recently launched the feature for a grid to automatically add/remove rows depending on the content that’s actually in there.  Unfortunately it’s not working for me, and I haven’t seen anyone else talking about it.

 

Let’s say I have a component with a grid, and it has about 4 rows worth of cards inside. When I use the instance of this component and hide 1 row’s worth of cards, the grid initially shrinks in height to hug the remaining 3 rows visible. But a few minutes later the instance will pop back to the height of 4 rows, leaving an empty row. If I toggle hide/show on the cards it will force Figma to recalculate the height and hug again, but then the same thing will happen again 2 minutes later. 

 

The inverse is also true; if I include hidden extra cards in my component, and turn them on in the instance, the grid will initially grow in height to accomodate the extra cards, but later shrink again to the original number of rows, causing the extra cards to overflow the frame.

    8 replies

    Tom Reem
    Figmate
    • Tom Reem
    • Figmate
    • June 2, 2026

    Hey ​@Julia57 and ​@didip13 — thanks for flagging this! I gave it a go in one of my testing files but wasn't able to fully replicate the grid resetting its row height unprompted.

    Could either of you share a bit more detail on what's happening? Specifically:

    1. Expected behavior. Does what you're expecting match what's shown in this GIF: Use the grid auto layout flow → Toggle automatic positioning?
    2. Card size. Can you confirm whether any of the cards span more than one row?
    3. Screen recording. A brief recording that includes both side panels would go a long way in helping us recreate the exact scenario.

    If a recording isn't possible, we'd be happy to take a look at the file directly. Just let me know and I'll follow up with instructions on sharing access securely.

    I'll keep an eye out for your reply.

      Julia57
      • Julia57
      • Author
      • Active Member
      • June 3, 2026

      ​@Tom Reem  Hey thanks for the response!


      I’ve attached a video demonstrating both cases (hiding and showing cards).

      I couldn’t catch the actual bug in action because it happens so randomly. But I tried to demonstrate how the bug looks.

      The expected behavior works fine in the master component. It’s the instances that are bugging out.

      None of the cards span more than one column or row.

        Tom Reem
        Figmate
        • Tom Reem
        • Figmate
        • June 4, 2026

        Hey ​@Julia57 — thanks for following up and for the screen recording. I haven't been able to replicate this in my own file yet, so I've gone ahead and opened a ticket with our Product Support team to take a closer look. Your case number is: 1942851. Please keep an eye on the inbox associated with your Figma account for a message from me with next steps on sharing file access securely.

        Julia57
        • Julia57
        • Author
        • Active Member
        • June 5, 2026

        ​@Tom Reem thanks, I’ll continue from there :)

          Axl Jaro
          • Axl Jaro
          • New Member
          • June 17, 2026

          Experiencing the exact same issue as of today. Wondering if this has been fixed or if any workaround exist?

            Julia57
            • Julia57
            • Author
            • Active Member
            • June 17, 2026

            ​@Axl Jaro They filed a ticket with Figma dev to fix it, but its not clear when it will be resolved. In the meantime, we built our Design System components with grid, but we cannot use them.

            So temporarily, in some designs we are using the old hacky method: Flex-wrap on the container,  min-width on the children, and throw a few zero-height frames in there to “hold open” the empty spaces when needed. And also naming the frame “❖component” so that we know its actually supposed to be the DS component.

            In some places we are using the component with the grid, but our spec sheets and flows keep bugging out and breaking multiple times a day randomly, and we keep getting comments from confused devs, “is it supposed to look like that?”

              AntoinePuig
              • AntoinePuig
              • New Participant
              • June 18, 2026

              Same issue here.

              Tom Reem
              Figmate
              • Tom Reem
              • Figmate
              • June 21, 2026

              Hey ​@AntoinePuig and ​@Axl Jaro, thanks for adding your reports here.

              I checked in with our Technical Quality team, and this issue is indeed logged with engineering for a fix. I don't have a timeline to share yet, but it's actively tracked.

              ​@Julia57 — appreciate you sharing the flex-wrap solution your team has been using in the meantime:

              In the meantime, we built our Design System components with grid, but we cannot use them.

              So temporarily, in some designs we are using the old hacky method: Flex-wrap on the container,  min-width on the children, and throw a few zero-height frames in there to “hold open” the empty spaces when needed. And also naming the frame “❖component” so that we know its actually supposed to be the DS component.

              Hopefully it helps everyone move forward for the time being.

              We'll continue monitoring this thread and will update here as soon as there's progress. Thanks to everyone for your patience — I understand how disruptive this is to your workflows.

               

                Terms & ConditionsAccessibility statement