Suggest a Feature

Hi, this is my first project — I built it to make it easier to compare Figma designs with live websites. Hope you find it useful!    Over.fig — a free Chrome extension that overlays your Figma design on the live webpage, inspects Figma CSS, converts them into Tailwind utility classes, and lets you easily view spacing between elements.🚀All features are available absolutely for free. 🔧 How It Works:1. Paste your Figma link2. Pick a frame to overlay3. Compare instantly — your design floats right over your web page ✅ Key Features: - Pixel-perfect accuracy - Effortless CSS inspection  — auto-convert styles to Tailwind utility classes - Precise measurements — see spacing, font sizes, and alignment in real time - Custom font support - Download optimized assets directly from Figma - Save hours every week on QA and revisions Would love your feedback!

I was thinking of what if @figma adds CYMK Color, which can be used for printing purpose. Recently was designing a poster & wanted to print it but, after printing colors were changed. So i thought what if @figma can add CYMK Color in the software. Let me know what you guys think

I would like to be able to selected multiple child components which are all associated with the same parent component and edit their shared nested instance properties across all selected child components.

I know If I use the option key and hover, I get the distance between objects but I would like a feature that shows the distance exactly the way the option key does but without start making a copy of the element. If I start moving it I just want to see the distance to the element above for example. If I do this now it’s going to get to a point where it starts measuring from the copy I’m holding.

I’m considering hiring offshore developers for an upcoming project, but I’m unsure about the best approach. There are so many agencies and platforms claiming to provide top talent, yet I keep hearing mixed feedback from people who’ve tried it before. Some say it’s a great way to save money and access specialized skills, while others mention challenges with communication, time zones, and maintaining quality. I’d like to hear from people who have real experience in this area — how did it work out for you, and what would you do differently if you had to hire offshore developers again?

SummaryEnable Figma Make users to preconfigure the default code output framework (e.g., Angular, Vue, React) and set organizational coding guidelines that are automatically applied when generating code.ProblemCurrently, Figma Make defaults to generating React code. While prompts can be used to switch frameworks or enforce custom rules, this adds repetitive manual steps for every session. Our teams have established rules and standards (framework choice, naming conventions, linting rules, accessibility standards, etc.) that we want consistently applied from the start.Impact Designers and developers must repeatedly remind the system of our preferred framework and rules. Inconsistencies can arise if someone forgets or phrases the prompt differently. Slows down adoption because teams want their code to be generated within their established ecosystem by default. Proposed Solution Allow users to define a default project configuration for Figma Make (framework, package manager, language ve

SummaryAllow Figma Make to read an .npmrc file so teams can install and use internal or private scoped packages (e.g., @company/components) within their projects.ProblemOur organization maintains internal web component libraries that align to our design system in Figma. These components are published as scoped npm packages (e.g., @ourorg/design-system). Currently, Figma Make does not support .npmrc configuration or scoped package resolution, which prevents us from using our own code directly in Figma Make. It would also reduce the amount of code Figma make generates if it doesn’t have to generate common component code.ImpactWithout this support, designers cannot easily work with the same components developers use in production. This creates a disconnect between design and code, increases manual work, and raises the risk of inconsistencies.Proposed Solution Enable Figma Make to read .npmrc configuration files for authentication and registry settings. Support installation of scoped pac

Hey there, I’ve created a branch and added a component to our library. So far so good. Then I accidently moved an instance of a component a bit, so that in the “Branch Review”, it says “Node Reordered, Position, Rotation, or Scale changed”. And yes, that’s true. Even though, nothing has changed. I missed to it CMD + Z to revert it, so now when I want to merge, I have to merge it even if I don’t want, and then push a library update of this modified pattern. My suggestion would be the same as we can do it in VS Code for example. Before commiting something, you have the ability to “Discard changes” meaning that all the changes you made in this commit will be removed and the component will be in it’s main branch position/state. That would be helpful for not having to merge something you don’t want/did only for testing purposes.

The title just about summarizes my issue. Developers until recently had access to ruler measurements and annotations with their Dev Mode seats. Recently, these tools were stripped from them. I don’t understand why only designers can measure distances or leave annotations, so long as they are not editing files, why should Devs be unable to annotate or inspect files using the tools Figma designed for Devs to inspect files?Good design practice in Figma often requires us to build things differently than they would be built with actual HTML/CSS. with Autolayout in mind, it’s better to determine the space between objects rather than apply padding to the top of Divs as many devs would do. However, when a dev wants to measure the total space between elements, they should be able to use rulers to make the measurement THEY need and not the one Figma decided they should have. Why were these tools stripped from Developers? We’re already on an Organization plan, paying quite a lot of money. They we

Hi there,I’d like to propose a feature that allows individual sections to exist within a parent section, with the ability to collapse and expand them via an accordion-like function. The default state would be closed—similar to an index—so that child sections are only visible when expanded.Currently, it’s challenging to guide developers to the correct layers because the default open view doesn’t always reveal all sub-sections, which can make navigation and referencing less intuitive. This feature would help improve clarity and streamline collaboration.

Hi Figma team,I’m working with a central design system library that uses variables for colors, typography, spacing, etc. The challenge I’m running into is how to customize those variables per project/client without editing the library file.Here’s the workflow I’d love to have: In the library file, components are built using semantic variables (e.g., Brand / Primary, Text / Default). In a project file, I create local variables with the same semantic structure but mapped to project-specific brand values. I want to be able to relink or remap library variables to my local variables, so that when I update the local variable values, all linked components automatically update. Right now, even if I duplicate the variable structure locally, components still reference the library’s variable IDs, and there’s no way to swap or remap them to my local set. The only options are: Manually rebind variables one by one (tedious), or Carry all brands inside the library as modes (not scalable when wo

Please kindly add native support for custom-assignable keyboard shortcuts within the Desktop App. I currently cannot add any custom keys and our workflows would be greatly improved with this essential feature. Thank you! 🙏🏼🌊Computer: Mac Studio M1 | OS 15.3.1

When selecting semantic tokens/variables for colors, you can’t search by section name—this is a HUGE MISS. For example, if I need a color for inputs and type “inputs,” in the color selector, the system doesn’t surface the variables you’ve grouped under that section. That feels like an obvious expectation. On top of that, actually locating these colors is incredibly frustrating when selecting a color. Whenever I’m building something new in a complex design system, this becomes one of the biggest pain points. It’s like there wasn’t any UX done for this. 

In a Design file I can create structure and hierarchy for my font styles by using a naming convention that leverages a “/”. However, even if it’s the same naming convention, this doesn’t result in the same outcome in Slides (in Design. Mode or Slides Mode). In a Slide file in Slide mode, I see the whole name in a list with no hierarchy applied. In a Slide file in Design Mode, I just see a list with no hierarchy in the dropdown + the prefix before the “/” is cut off. But then when I select it… it shows up in the panel… It’d be great to haver a similar behavior in Slides as in a native Design file…  

Currently, when working in Libraries, Figma picks up changes and in the modal to Publish, you are basically forced to Publish any changes that Figma picks up. There’s no way to “reject” those changes. This adds a layer of complexity because Figma doesn’t say how things got changed, it just says that something changed. So often times, we’re not sure why Figma is saying it got changed when visually things look the same. We also keep our editor list rather small but it happens often where I log in the morning, see there are changes, ask the team did anyone make changes, and they all say no they didn’t do anything. From that point on, there’s nothing to do but publish those changes which has negative downstream effects to our entire design org who uses our libraries. They see that they need to update their libraries but for no good reason. We do add comments when we publish so we have to say stuff like nothing actually changed, Figma is just picking up changes when there are none. Does any

The comments feature is very handy amongst the colleagues. It would be nice if the comments bubbles would stick to the object instead of sticking to the position within the frame. Since we are moving stuff around ( adding or subtracting elements ) the comments made should stick to the proper parts of the design. Otherwise, when we move things around, the comments don’t make sense anymore because they do not relate to the object’s new position.

Just putting this suggestion here for the ability to indicate what symbol / value to add to the end of truncated text instead of just the ellipsis (...)Technically there is support for this in code via the text-overflow CSS property, so it might be good to also bring that functionality within Figma Design.Additionally, hoping it could also be possible to change the way text is truncated, where we wouldn't be limited to just text lines, and have the ability to switch to set the truncation via number of characters in the text layer.

 안녕하세요. 초보자가 “MAKE”에서 웹을 개발하다 보면 너무나 많은 버전 히스토리로 인해 웹페이지 로딩이 느려지고 있습니다. 이미 FIGMA 팀의 도움을 한번 받은적이 있는데,앞으로 자주 사용하다 보면 매번 FIGMA 팀에 도움을 요청하기가 부담스러울것 같기도 하고,시간적인 소요도 제법 있는것 같습니다. 사용자가 스스로 버전 히스토리를 삭제 할수 있는 기능을 구현하는건 어떨까요?

Is it possible to add comments in Figma, I shared the prototype to few folks wondering if there is a comment feature.

Hello,We currently are creating annotations utilizing the native Figma annotations tool, but we also need to recreate the annotations to create a format that we can export to pdf for client review and approval. If we could make it possible to turn on Annotations and have them visible along with the frame elements, so they could be proofed by others not within Figma that could be exported as a hard copy, that would be an amazing feature. Currently we need to move them every time the layout shifts. It isn’t very user friendly.

Is there any plan to be able to create the gradient itself as a variable? For example, if I wanted some themes to have a solid background variable but others to have a gradient?

Lately, I’ve been trying out asking Make’s model for design feedback and collaborate on ideas, BEFORE I want to make actual (code) changes. This is a good workflow people use with more experience with prompting.Unfortunately, I’ve noticed that when I ask it to “not make any changes” because I’m asking for ideas first, it just gets stuck on “Reasoning...” 😅 💡 Proposed solutionHaving a Chat Mode that can be toggled, similar to Lovable, would probably be a nice user-friendly way to provide this type of functionality, without having to prompt for it.

Kind of what this says really. Figma Make is a brilliant tool even in Beta.I have a workflow of taking screenshots from Make and putting them into FigJam and sketching over them with my iPad, so it would be great to have the copy to PNG function that exists across the other products (even if it was an interface button). It’s also useful when needing to paste a screen back into the chat to provide feedback.In terms of working with Cursor it has great conversion of images. Ideally there needs to be a way to export all screens (or a selection) to an image folder. At the moment it’s painful having to take screenshots and then deal with the external organisation of these. Exports should have some form of naming logic too (date, time, screen, etc...)

I’ve been playing around with converting figjam notes into slides. Would be great if Figjam could talk to the custom templates. For example, a sticky labeled insight #1 should use the Insight slide format from this Custom Template

If you open a lot of projects the tab strip gets crowded. Chromium browsers solved this by allowing to group tabs, maybe Figma could do the same ?