Suggest a Feature

For instances where a user is creating a flow chart and the text formatting bar isn’t needed, can there be a way to either hide it entirely (similar to hiding UI) or being able to pin it to a location (like its attached to the Tool bar)? Having it open all the time when you’re clicked on an object can be frustrating when trying to see if you have a connecting line or to read an object right above it.  

It would be a great idea to add the ability to move annotations (сhanging the place). Right now, they’re fixed in place and can overlap other elements. And you cannot change it.What I mean is the ability to reposition an annotation freely while keeping the link to the target object intact.Annotations are a really useful feature—thank you! Previously, I had to create similar functionality using my own objects. Please do not move this offer to another discussion. 🙏Can we move the Figma Annotations (in dev mode) from one Figma project to another?These are different questions.

I was super pumped to start using grids for my layouts until I learned of one fatal flaw that killed my excitement :(  The inability to set a row height to hug is simply a deal-breaker for me. Also no variables support for gaps? really?

I see we can double click the edge of a section to match contents, which is truly so lovely. I would like that to be taken a step further: a one-click option that causes a section to resize itself according to contents without further intervention, functionally in the same vein as the Figma auto-layout feature.When in Figjam, I want to focus on thinking and planning. Repeatedly zhuzhing layout is such a relentless distraction. It would be nice to be able to check a box on a section that says “Manage yourself, please!” So I can keep scooting. That’s all! Thank you for your time, and such a nice app! 

We need a way in the REST API to get a list of Team IDs. A previous post (Suggestion: API endpoint for :team_id) was moved to ‘share an idea’ and then marked as solved, so I’m reposting sans solution, in hopes that we can get some votes. With the new library analytics API, this feels more relevant than ever. I want my users to pick the team their library is in from a list, and then pick the library file from a list of files. Trying to get end users to figure out how to get the library file ID is needlessly complicated to start taking advantage of the new API, when I could set up a system to let them pick it from a list. Almost all of the endpoints require a Team ID… (or require a file ID, the list of which requires a project ID, which requires a Team ID… etc.) So adding a Team API would unlock improved usability for almost every other REST API endpoint.

Is it possible to change default font in Figma? (from Inter to Mardoto)

I know that I can export as SVG from draw.io and then drag and drop in FigJam but this does not allow me to edit. I would like to import a flowchart from draw.io in an editable format. Thanks.

Hi everyone 👋One thing that has always bothered me about Figma’s native PDF export is that it converts all text into outlines. TrueText PDF fixes that.Select one or more frames, hit export, and get a PDF where every word is selectable, searchable, and copy-paste ready — just like a Word doc.https://www.figma.com/community/plugin/1608786203490497687/truetext-pdfFeatures:• Selectable & searchable text in exported PDFs• Pixel-perfect positioning — text overlays match your design exactly• Bold and mixed-style text fully supported• Multi-page export — select multiple frames and export as a single PDF• Drag to reorder pages before exporting• Sort pages by name

So this boggles me. Why can’t I change (override) the opacity of a referenced color-variable, without having to detach it? To me a color and an opacity value are two different things. So if I want an opacity on my referenced color e.g. “Blue-950” I have to detach it and change the value to my liking, now it is not referenced to the variable collection anymore. A workaround is to add that “Blue-950” with the desired opacity in the variable collection and then reference that new “Blue-950-50-percent”. It is so annoying that you can’t change opacity on the fly without loosing reference!!!

I’m using Figma Make to leverage my company’s internal design system. I’ve made some progress, but I’m still running into issues with it properly consuming our system. Right now, Figma Make creates its own set of design tokens or references tailwind tokens to create lookalikes of our designs. I have spent a lot of time adding code context to our variables in our design system library, but these seem to be ignored by the figma Make llm when it generates the designs.I have our system’s components loaded into the private NPM registry. I have the styles and token packages in there as well. There is no reason it shouldn’t try using them first, and I’ve even told Make how to consume them (in several different ways). It seems to prefer tailwind/radix regardless, which is no longer acceptable, and is causing additional churn cycles for our teams.Instead of trying to force tailwind/radix to look like our design system (and repeating this process for every new Make we mak

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’ve got our company’s internal design system packages published into our private NPM registry. But in doing so, I found (after I published) I needed to modify the packages for consumption by figma make. Figma’s NPM private registry would not allow me to unpublish or overwrite the package versions once I published them.This is causing a problem in Figma Make because users are able to select old, incorrect versions of the packages when installing. I want to prevent this by being able to unpublish or delete packages from the registry, but I’m unable to do it.We are experimenting with the best way to handle this for figma make that is easiest for our figma users--and would like to be able to hit a hard reset at some point as we may completely change strategies. Right now, we have 50 or so unbundled packages in figma make. In the future, we may want to bundle those into a single versioned package for easier consumption.To summarize, here is a list of figma make NPM

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.

It doesn’t look like there’s an obvious way to change the order of exposed nested instances. Right now the order seems to be based on reverse layer order. It’d be great if the order can be manually adjusted.

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 there! I was also wondering if it is somehow possible to include also the layer of variant controls to be exposed or hid! I often have cases where I need to nest base components e.g. an icon wrapper providing me with the ability to select certain sizes, or color overrides and boolean props of an icon. I am now able to expose all of those or none, but I can’t restrict the users to only be able to select just some of those. What do you think about it?

Hey everyone,As a product designer working with a pretty large internal design system, I kept hitting the same limitation in Figma Variables: they’re great for static values, but the moment you want a scalable system (spacing scale, type scale, radii, opacity variants, responsive values…), you end up maintaining a ton of derived variables manually… or in spreadsheets.Variables Plus — a plugin that lets you define relationships between variables using formulas, so derived values stay in sync automatically when the base variable changes.Examples: space_2 = space_1 * 2, space_3 = space_1 * 3 h1 = base_font * 2.25, h2 = base_font * 1.75 col_w = (container_w - (gutter * (cols - 1))) / cols

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

Please make Dev Mode Annotations visible by all roles, not just Full Dev Mode seats. This can become costly for users needing context but not all the other dev-mode features. Here’s the scenario: We have a dashboard, with cards showing a customer’s account status. This status can be mapped from multiple back-end statuses, to show just one front-end status. For example, any of the following could be mapped to a single status known to the customer as “Completed”: canceled, terminated, sold, complete, etc. This is something that the developer needs to reference, but then also the PM needs to reference in writing tickets (who doesn’t need full dev-mode access), the QE needs to reference for testing automations, and various other individuals on our team. Placing it in a comment makes it less clearly attached to the specific piece of the design, and requires us to keep documentation dispersed among different tools (Jira, Confluence, Figma etc). Simply making Dev m

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.

We noticed that starting March 18, Professional plan seats will include 3000 AI credits per month.After testing Figma Make, 3000 credits feels quite limited. In practice, this equals roughly 50 to 70 prompts per month depending on usage. When building and iterating on prototypes, especially during exploration phases, this amount runs out very quickly.For teams that rely heavily on AI to generate, refine, and test ideas, the current default credit allocation makes it difficult to maintain workflow momentum throughout the month.We understand that additional credit packages may be introduced in the future. However, the base 3000 credits per seat feels insufficient for serious prototyping and experimentation within the Professional plan.Would it be possible for Figma to reconsider increasing the default monthly credit allocation to a more practical amount for active users?Looking forward to hearing thoughts from the community and the F

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.

Figma Make is the best prototyping tool I have seen so far (yes, better, or at least more time efficient, than V0 and Claude Code for now). It also has an integration with Github, which is suuuper cool. Now… it would be REALLY gamechanging, if the connection with Github was a two way sync. If edited code could be pulled back into Figma Make, for team collaboration across multiple platforms. I understand that this is really tricky, because Figma Make can't interpret all types of code… but I'm putting it out there… 

When aliasing a color variable to another (img 1), or using it directly on an element (img 2), we should be able to override the opacity without the need to create a variable for each transparency variation: Cant override opacity in the alias: Example 2 Cant override the fill opacity: