Suggest a Feature

We’re attempting to use Figma make with our internal design system and I’m running into several issues regarding context provided to Figma’s coding AI models:Our design system has around 80 components that all need guidline files in the guidelines directory according to the Make documentation. I’ve created these files with AI connected to our internal MCP server. 80 or so files. To get these files into Make, I had to create them manually one-by-one and copy/paste the contents in for each make. Theoretically I could do this with a template Make file that everyone starts with, but this is cumbersome regardless.Here is what I’m requesting:Ability to push guidelines to a figma make project without needing to copy the project. I have like 80 files representing different components that needed context. (generated from our MCP/Cursor) Ability to push our codex packages from our engineering MCPs so they can be consumed a

I often duplicate existing mocks to work on feature updates. Deleting previous annotations one by one is extremely tedious. It would be helpful if the tool could recognize when a frame has been duplicated and then allow bulk clearing of annotations.

With the increasing popularity of iPads among creative professionals and the device's capabilities now rivaling many laptops — especially with Apple Pencil support and desktop-class processors — it’s surprising that a leading design platform like Figma hasn't released a fully functional iPad app. Is this a matter of strategic prioritization, where Figma believes the current user base doesn’t demand it strongly enough to justify development resources? Or is it due to technical limitations, perhaps stemming from the complexities of maintaining feature parity with the desktop/web version on iPadOS? Alternatively, is Figma's vision more aligned with a cloud-first, desktop-class browser experience, where portability across devices takes a backseat to collaborative infrastructure? If so, does this approach overlook the rising trend of mobile-first or tablet-based design workflows? It would be insightful to understand if Figma simply hasn't seen en

Hey folks, first of all I love the new variable function. Within the setup of spacings I want to reference my base value (“8”) and do calculations, e.g. (spacing-base)*2". This works fine and the value is calculated properly within the input to add a new variable. But I expected not that the calculation string changes to the absolute value. With this behaviour I loose the connection/ reference to my base value and the calculation is some how obsolete. Does anybody feel the same? Will there be an update? Thanks

It would be great if, when I insert a component from a Figma library in Figma Make, I could use Figma Code Connect to retrieve the actual design system code linked to that component.

Hi! I upgraded my Figma account from using the free version to the basic plan. Since I did that I can no longer switch to design mode when I could do that with my free account. Please can someone fix this asap. Otherwise I will downgrade my account.

I often need to paste screenshots into Figma from mobile devices of various sizes. We work at the pt/dp scale, so it would be awesome if there was a setting someplace where you could have Figma try to determine the proper pt/dp size of the device/display from which the screenshot came and then automatically resize it to match that.Example: I drop in a screenshot from an iPhone 16 Pro onto the canvas. As of posting this, Figma sizes the screenshot to 603x1311, but based on the original dimensions of the image, it should be able to determine (or do a best guess) of which device it’s from, and then resize it to the proper pt values of 402x874. Half of this info is already stored in Figma’s roster of frame sizes (i.e. when creating a new frame, you get a ton of device choices with the proper pt sizes), so I have to imagine this is possible to pull off. Obviously not with 100% accuracy...but currently my workflow requires me to resize these screenshots 100% of the time! 

I’m wondering - why do we need the instance swap property? Usually our components have variants therefore the nested component property is a better option. In my opinion, the nested properties should appear automatically once I place a nested instance of one component inside another. 

I have a numeric input field as a component, and its value is set as a text property called value. Pretty simple stuff, right?For prototyping reasons, I want to bind this field's value to a number variable, so I can add/subtract to this value when I press a button somewhere else on the screen. Also pretty simple stuff, right? Well, apparently not. Turns out I just found out that we can't bind number variables to text properties for whatever reason — they don't even show on search results. And since there's no component property of type number, this simple prototyping scenario I'm trying to achieve appears to be impossible. Meanwhile, if I simply remove the value property from my component, then select the plain text layer with the value and try to bind it to my

Can a remark function be added to personnel management to write remarks for each member's name?

1. Describe the problem your experiencing and how your idea helps solve this If I add an image to figma and then resize that image I would like to export it at the original resolution. Maybe if there was even a button to resize the image to the full size. 2. Add as much context as possible (screenshots, Figma files, mockups, etc.)

Vertical text is pretty common for east Asian text like Japanese and Chinese. Can you make this a feature?

Hello I miss a capabilitie to assign a number variable to the rotation field. In the today case, I simply try to rotate a SVG animation depending on the breakpoint. If somebody have a solution (no bolean 🙃) Thank you

Poder crear subcarpetas en los proyectos

Negative delay is a cool idea in prototyping when you need to start next action BEFORE current is ending, so next starts in 100ms before current ends

When exporting variant names, the file name becomes a combination of all the variant properties. There is no way to control the variant export name, which is especially difficult for developer hand-off. In this example, I have a back icon variant group (Named “Back”) containing both an Apple and an Android variant of the back icon. If I then go to expo

Currently exported .PDFs out of Figma are not accessible, because the text is flattened as images. I would like to request an option for exported .PDFs to have editable text. This would be a game changer for our team to move off of Sketch! 😃 (Sketch allows for .PDFs to export with editable text, but Figma does not)

 Summary A way to merge two or more Figma Make files together — similar to how video editing tools let you combine, split, or cut clips on a timeline.The problem When working on complex SaaS prototypes and flows, I often end up with multiple Figma Make files that each contain useful generated content. Right now, there's no way to bring them together without re-prompting from scratch — which means repeating context, losing time, and risking inconsistent output.The idea A merge or "stitch" feature where you can:Select two Figma Make files and combine them into one Preview the contents of each file (like a video timeline view) before merging Choose the order, split points, or which sections to keep — without having to re-generate anythingWhy it matters For product designers working on multi-screen SaaS flows, being able to build up a prototype from modular

I know there’s an option to hide the components from a linked library by prefixing them with a “_” or a “.” but I also have components within my file that I don’t want to see on the search results. Is there a way to achieve this?

In figjam especially people commonly sketch out diagrams with lots of freeform lines used as arrows to point to things, sometimes as they talk about them (both when brainstorming and when annotating). It would be a really nifty feature for advanced users to be able to automatically have a line get converted into an arrow. Could also see this relevant in Figma too.I think everyone can maybe relate to the pain-point of having to either go into the setting to choose the arrow end-style for a line you just drew (a little finnickey and breaks flow if drawing to explain something on a screen-share) or else you manually draw the tip of the arrow each time for each line (doesn’t look good and if you want to move the arrow you have to select both the arrow tip you drew and the line itself)

Would be good if there was some way of exporting comments to a text file without the need of a Plug-in, helps build documentation

Hello,An admin-level dashboard for Figma AI analytics would be invaluable, giving us the visibility needed to:Measure Business Impact: Track adoption rates and usage to satisfy our internal reporting requirements. Drive Strategic Adoption: Identify which AI features are most popular and which teams are leading adoption. Support Our People: Celebrate team members who are regularly engaged with AI and identify users who may need more support to get started.

I have this use-case:All I want to do is ask the Figma AI to “Populate the same colour styling based on the syntax above, to the syntax below”.This is super easy for AI to understand.It should be in Figma already. There are so many example like this where because of the way the Figma interface works in relation to product UIs, some things take a disproportionally long time to do - e.g. “change all these pill components to this new one”.  

There have been many times where I’m trying to compare the color values between two or more objects. However, every time I select another object the color panel disappears so I have to click on the swatch again and try to remember the values from the previous object. Sometimes I’ll just take a screenshot of the color picker values and paste them back into Figma but that’s not fun at all. One possible solution would be to make the color picker remain visible if the user ‘unpins’ it (ie. drags it away from the right panel). Then they could select the next object to see the color values and then close the picker when they’re done.

Figma: If you’re used to working in another design tool, you may find it strange that your text styles in Figma don’t include traits like color or justification. Although it could take some getting used to, hopefully the benefits of this approach will quickly become clear. Well, no it didn’t. And strange indeed. In addition to getting used to, it takes a lot of time to to change the color every single time I create a new text element, because our text color is not black. Having a default color saved with text styles would be SO. MUCH. EASIER. I see no reason why the color can’t be in there and also be changed when using the style, if necessary.