Suggest a Feature

 I love the implementation of Figma Draw! Please keep adding more functionality, because I would love to keep using Figma instead of having to pull in elements from Adobe Illustrator! Here’s my feature request:Can you add more detailed point manipulation tools in Figma Draw, such as the ability to scale, rotate, transform individual vector points in concert each other relative to a custom transform origin point?This process is relatively simple in Illustrator currently. I just select my points, select the Scale tool, set my origin point, and then drag/scale. Each point is transformed an equal amount, its perfect. This capability is super helpful for icon and logo design.  In Figma currently (unless I’m missing something) this is a very manual process: I have to select a vector point, and then key in an X (trial and error that value) and then do it for the other point, which is extremely cumbersome compared to most vector editors.   

Admin management for "standard" and "private organization" plugins is currently separated into two completely different interfaces (Admin / Resources / Approved Plugins vs Workspaces / Plugins). It would be great to have these consolidated into a single interface, or at least cross-linked.  Our admins don’t manage our few private plugins as much, and always have to spend 10 minutes+ trying to figure out where the private plugins live.Publicly sourced approved plugins are all listed from the Admin / Resources area. But... Private plugins developed internally are listed under Workspaces (or Teams)Even a cross-link between the two spaces would be helpful. Ideally all the plugins should be listed together.

It would be convenient to be able to search through a long list of approved plugins from the admin interface. Currently you can do this from within a web browser using CMD-F. But in the app, CMD-F isn’t an option, so as an admin you have to scan the long list.Many of the other admin functions have a search, so this seems a natural add.

I’d like to suggest a feature improvement for Figma Make based on a real issue I recently encountered.In one of my long-running projects, I had accumulated thousands of Make prompt interactions (≈4,000+) over time.Eventually, the file began to show severe performance issues: Frequent “Recovery mode” prompts Editor becoming unresponsive Out-of-memory (OOM) crashes Make prompts failing with errors such asPOST /api/make/fetch_ds_code_gen_status 400 After working with Figma Support, we discovered that clearing the Make chat history immediately resolved the problem: Performance returned to normal No more recovery mode or memory crashes Make prompts started working reliably again This suggests that long Make prompt histories can significantly impact memory usage and file stability, especially in large or long-lived projects.Feature suggestionIt would be extremely helpful to have: A built-in option to clear Make prompt history Or basic prompt history management (e.g. clear, archiv

Hi, it would be great if we could hide/remove rows/columns if all the content inside the row/column is hidden/deleted. That is, the grid’s dimensions get adjusted dynamically based on the content instead of being fixed always.For example: In this 3x3 grid, if I delete/hide “C”, then the second row should be deleted/hidden such that the grid looks like a 2x3 grid instead. Like this: Instead, it currently looks like this: The second row does not get automatically hidden/deleted since the Grid dimensions are fixed. Would be nice if we had dynamic dimensions based on the content. I know that this can be achieved by creating a regular vertical auto-layout with nested grid auto-layouts but that feels more like a workaround. (That’s how I created the “how it should be” example above). I am currently working on a complex form using Grids and I am not able to dynamically show/hide fields with a Grid auto-layout. I have to now create a grid of form-fields (even if there’s only 1 element in it) a

The fastest way to suffer in Figma? Try building a design system icon library with stroked icons - resizing alone can turn it into a never-ending headache Example: You draw a line icon at 24×24 with 2px stroke (e.g., hamburger icon).If you resize it to 48×48, the icon gets bigger but the stroke stays 2px. The only way to scale stroke proportionally is using Scale tool(K) manually. That works until you use few icons. But not building a lib.Icon wrapper could be a solution. But wrappers can only resize, they can’t apply Scale(K) for you. So the icon’s weight looks wrong at different sizes.Workarounds don’t scale: Big libraries explode with variants (1000 icons × multiple sizes (at least 6)). Outline/flatten strokes breaks editability - and icons must stay editable because you often need to go back and adjust them. Keeping “editable source” + “flattened output” in sync is not sustainable long term.  WHY NOT?!Add a per-layer/per-component a checkbox: [✓] Scale strokes on resize. Defaul

There’s a lot of plugins, and especially for certain features that there’s a lot of plugins for, like finding Icons/Symbols, there’s certain plugins that i prefer or like, but can only access them through the Recently Used section, but it disappears if I use other ones. There should be an ability to favorite a plugin for reuse.

Does there exist a setting that would allow me to prevent URL links from being clicked while designing? I want them if I’m viewing a prototype. When I’m designing though, I’ll often copy and paste copy from our website which has a number of links in it. Then as I select text to work with it I inevitably click the links. It’s almost as if my mouse is attracted to them. It drives me nuts.

It would be great to be able to seperate the visibility objects beyond just the layer. To be able to associate a boolean variable to the visibility of; Layer Fill Stroke Effects Would make it more effective when putting together a design system. This means that you could effectively determine that all buttons have outlines, or drop shadows or both right across the whole design. See examples below. Thoughts?

Please… PLEASE! For those of us with lots of simultaneous projects and heavy deliverable schedules, tab browsing in Figma needs some LOVE! Now, I’m not one of those psychos that keeps 300 tabs open in their Chrome browser, but I do, at any given time, need access to multiple projects simultaneously. If I could easily group those tabs together in Figma and give them a nice, friendly name, maybe an emoji, or… dare I say… a color, I’d be a really, really happy camper.  

Would love to have more options on the typewriter effect, such as easing.  Also would love to have more/better control over parallax scrolling (direction, speed, distance all as separate parameters).

It would be great to have a feature that allows you to hide or lock a page in a file. There have been moments when stakeholders will keep peeking at the work before it is ready for review. Having a hide & lock feature would be nice to have so that if you do share the figma, they can only access the pages visible to them. 

Здравствуйте подскажите пожалуйста как можно добавить шрифты в фигму если работаю на ipad

I am using variants to enable dark and light modes for example and it works automatically for almost everything except for overlays. I have am user flow with an overlay menu that opens when I click on a button or icon. I want to display how to shwitch between light/dark modes. So when Im in light mode and open the overlay menu (light) and then switch to dark mode and then open this menu again its still in light mode and I dont see a way to change this using the “Change to” nor “Set Variable” options in the “On click” prototyping option. How can I simulate this consistently without having to use two different menus (one for each mode)?

With the emergence of skills for agents becoming very popular, are there plans to create agent skills for the various dev API you offer? For example, skill for plugin & widget development. Skill for dealing with the REST API, etc.

It would be really helpful to have the ability to group opened Figma tabs in the top bar, allowing users to create collapsible and expandable folders, similar to the tab groups in Google Chrome.

It would be so great to have some additional filter options when browsing search results. In a large organization, there can be dozens of files spanning years, all with similar names and content. It’d be great if one could still sort by recommended results, but filter by the modified/created date

The fill is not visible on a vector shape unless its closed. Many applications and the web supports fill on open vector shapes, but not Figma. Please allow something like this. This red area should be fillable by the paint bucket.  

Figma Prototype : In large IT companies and design teams, it’s often a struggle to manage design review tasks because we constantly need to jump between Figma and external management tools (Jira, Asana, Notion, etc.) just to track: what page or element was assigned to us for review who is responsible for feedback what review status each screen is in ✅ Proposed Feature: Review Tab Inside FigmaIntroduce a new “Review” tab, similar to the existing Dev Mode icon, that enables teams to manage review assignments directly in Figma.🔹 Key Features1. Assign Reviewers to Frames / Pages / ElementsJust like adding a Dev icon, designers could add a small Review badge on a page or specific frame. Assign a team member Add due date or notes Track who is responsible 2. Review Status TrackingEach assigned item could have a status such as: To Review In Progress Approved Needs Changes This would give instant visibility without leaving the design file.3. Review Inbox Panel (Like Notifications

When selecting an object inside a component, the bounding box uses the same purple color as components. This makes it difficult to quickly confirm whether you’ve selected the parent container or a nested object.It would be helpful if objects within a frame or component used a different selection color than the container itself. This visual distinction would reduce selection ambiguity and speed up precise edits.A comparable example is InDesign: images live inside frames, where the frame is highlighted in blue, and double-clicking into the image shows an orange bounding box. This clear color separation provides immediate confirmation of what level you’re editing.Introducing a similar distinction in Figma would improve clarity and reduce mis-selection, especially in complex, component-heavy files.

The variables feature is a great addition to Figma. In our workflow, we use them extensively with multiple modes (like light and dark mode) and collections, which involves a lot of variable aliasing (linking variables to other variables).This has created a large and complex network of references. It is becoming difficult and time-consuming to find the original source value (like the final hex code) for a specific variable.It would be a significant workflow improvement if we could trace a variable's origin, much like you can trace CSS variables in devtools.We propose the ability to click (or right-click) on an applied variable to see which variable it is referencing, and then be able to follow that "chain" of aliases all the way back to its original source value. This "Go to Definition" or tracing feature would make debugging complex variable setups much more efficient.If this functionality already exists, please let me know. Otherwise, I hope this is valuable feedback.

Allow us to change the background color of text (not just the text fill color) to give a highlighter effect that stays with the words that the effect is applied to even when the size/shape of the text box is changed. For example: The above shows two examples of the same ipsum (left and right) where specific words are highlighted. When the size of the text box (the left example) is changed to accommodate a responsive layout (the right example), the highlighting stays with the selected words. The way to add highlighting for the above examples could be included in the type settings pop-over: Note: the idea here is that the user can apply this to specific sets of selected characters within a text box or to the entire text box, just like how all of the other type settings already behave.

Situation It often happens that there are a lot of instances that have overrides in a design. Sometimes you are not quite aware what exact overrides have been made to a component, though. For example someone could have manually changed the height of a component and if the height override is actually the same as the main component, you would be blissfully unaware. Problem You will notice that an override has been made maybe, after you make adjustments to your main component and realising that the instances did not change. Annoyingly, if you want to reset a particular override behaviour, you will have to reset the entire component back to the state of the main component and then do the overrides you do want to keep again. Depending on the complexity of the component (Maybe it is even a nested component), this can be quite the hassle. Proposal As such it would be nice if we had some listing of the overrides that have been made (maybe also interesting for the devs) as well as the option to

Hi everyone, 👋I’m new to Figma and learning everything completely from scratch. I really appreciate having access to the free version, as it’s been helpful for getting started. That said, I’m finding the current limitations a bit challenging when trying to fully understand the workflow and explore what Figma can really do. I feel that having access to some Pro features would really help me learn faster and more effectively. I wanted to ask if there are any options for a free trial or a discounted Pro upgrade for beginners even if just for a limited time. I’d love the chance to experience the Pro features before fully committing. Thanks so much, and I really appreciate this community and the product!— Bright

It would be beneficial to have version control in Figma Make, or at least the ability to publish changes to a "QA" instance. Currently, the only way to test app changes across different browsers is to publish them and hope for the best!