Tables for Figma

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.

Now with the Figma Agent, a semantic table tool is still sorely needed. How can the Agent understand that your group of shapes and layers is actually a table? If Figma had native table support, maybe it could help the Agent better semantically understand table structures, and thus become more helpful. Right now, it destroys tables because I think it just doesn’t understand what they ‘are’, if that makes sense.