A design tool like Figma should have a way to make Tables which are a very basic feature for layout design. Currently I’m forced to use something else. I’ve looked at the alternate ways to make tables in Figma and its not pretty or convenient. Looking at the history of other similar requests here, it doesn’t look like this will get a response, let alone a response from the product team.

Hi @Usmtr - at the moment, there’s table tool or feature available natively within Figma.

At the moment, it’s not on our roadmap, so I can’t speak on if/when this would become something available.

I know you mentioned that the alternatives you’ve looked into aren’t ideal for your situation, but my best recommendation at this time is to give our community plugins a chance to see if something ends up working for you.

In the meantime, I’ve edited your topic title for extra clarity - hopefully others who are looking for a similar solution will add their +1 votes to this ☺️

The best table-building feature I’ve ever used is in Omnigraffle, that old diagramming software for Mac. In fact, if I have to wireframe a table, I’ll fire it up and export the artwork as an image for Figma.

I think Figma should benchmark the Omnigraffle functionality!

would be great if it could use something like css grid / flex so handover is factored in.

obvs ability to add various lines, fit and hide content, text alignment, independent row / column sizes (fix widths, flex others).

definitely needed.

Native Table support in Figma is essential for rapid mockup and prototype production. Far too much time wasted on building and adjusting.

It’s now 2024 and a Table element is sorely lacking for Figma (aside from increasing the number of modes for the non-enterprise plans). I’ve used all the methods for constructing tables column based, row based, and even autolayout wrap and none of them work even remotely the way we need for design.

It would be a huge improvement if Figma shared the FigJam native table component. Maybe these two teams can collaborate and deliver a value win!

Big up for this feature. Can’t believe it’s still missing in Figma 🫤

It’s fascinating that Figma has so many great features that are such time savers (especially coming from Adobe XD), and yet this wasn’t even on the roadmap 2 years ago…

I certainly hope it will be there soon and with high priority, because it’s sort of scandalous to have this gaping hole in the otherwise great set of tools. You would think that with Figma’s prioritazion of big corporations, this would be higher on a list.

I make a lot of screens for B2B apps and I work with tables all the time - it’s infuriating how much time gets wasted to get basic stuff done.

I just popped over here to see if there was any progress, because I’m procrastinating working on my task since once again tables are involved and it gives me psychic pain.

I’ve built a very advanced cell/row/table component system and it’s still clunky AF and horrible to use (column-based, because my team keeps wanting to add or remove columns more often than they require a certain number of rows).

I keep scratching my head about the priorities of the Figma product team, but I suspect all resources are being thrown at shiny marketing features that include the letters “A” and “I”, likely in that order. 

Tables and an XD-style Repeat Grid are hugely missing features here, as is a proper CSS Flexbox implementation.

The Figma Team could just port the table feature from FigJam to Figma (at least).

Tables are essential! I’ve designed so many tables I lost count at this point. This needs to be in Figma ASAP!

It’s now 2025 and just after Config, where a whole bunch of new products were announced. And still no table component (or any other type of functional component used in every application in the world like radio buttons, checkboxes, input fields, etc.). So disappointing.

It’s now two years later-2025 and just after Config, where a whole bunch of new products were announced. And still no table component (or any other type of functional component used in every application in the world like radio buttons, checkboxes, input fields, etc.). So disappointing.

You’re totally right — Figma’s lack of native table support makes designing data-heavy interfaces way more tedious than it should be. A proper table component with resizing, sorting, and interaction options would save huge amounts of time and unlock real productivity for enterprise UI design.

I get you — building tables in Figma feels like a constant workaround. Native table support with proper rows, columns, and sorting would make workflows so much smoother and cut down on all the manual tweaking.

​@Matt_Meeks  I’m not sure about default “functional components like radio buttons, checkboxes etc”. That doesn’t seem right. That’s the job of the designer to create the look-and-feel and behaviour of those components. You can 100% make completely functional radio buttons, checkboxes and other input fields (including drop-down menus) that all “work” in Figma Design - you just have to really understand how to build components and variants and if you’re fancy, use the prototype mode to define automatic behaviours like rollover etc.

We are definitely on the same page regarding implementing Tables - which is a layout type not a component like a checkbox or radio button.

​@Tom_Auger1 Nope. Every other prototyping tool I’ve ever used: Axure RP, UXPin, Just in Mind, etc. all have functional components that not only work like real browser-based components, but are usually fully customizable. And no, you cannot make fully functional radio buttons and checkboxes, and especially input fields that you can type into and use logic. In my opinon, Figma is not really a UX or prototyping tool-it’s more of a UI design tool with minimal interaction capability. It may be suited for most designers, especially young designers who primarily work on mobile apps, e-commerce, or websites, but it’s severely lacking prototyping capabilities for the enterprise applications I work on.

Figma is also missing crucial interaction capabilities like using double-click, specific key commands, and other triggers that have been in other prototyping tools for more than a decade. Creating complex interactions is needlessly complex. It may be because we have several designers creating components and interactions, but we frequently have interactions break.

It’s interesting to hear about your use case ​@Matt_Meeks - especially when it comes to prototyping. I think you’ll really like Figma:Make in that case. My guess though with regards to components is that perhaps you haven’t fully explored the depth to which you can create complex components with multiple states and properties when done correctly - most people don’t bother. As a UX designer of 30 years myself, I find that Figma is more than capable a tool… up to as you mention the prototyping stage, where it becomes very cumbersome indeed. I’ve had great success however with Figma Make to create unbelievably high fidelity prototypes (I even have one prototype of an AI chatbot fully working and using the OpenAI API right in Figma). And that’s only going to get better in the coming months. Take a look if you haven’t already.

But we’ll have to agree to disagree on the UI component piece. In every design system I’ve built or managed in Figma, we’ve built out the full suite of form/input controls and this has given us full control over the behaviour, look-and-feel, and customizable of those components - and they translate well to code afterward.