Suggest a Feature

hey Figma fam, so, we’ve been going on about this for ages, but seriously, when are we getting the “lock guides” feature? it’s 2024, and we’re still nudging guides by mistake 🙄 we all know the drill - you’re in the zone, designing away, and then oops, there goes your guide. it’s like playing a game of ‘spot the difference’ trying to get it back in place. super annoying. i mean, how many times do we need to ask, right? it’s a no-brainer feature that would make our lives so much easier. locked guides = no more accidental shifts. simple. let’s give it another shot. maybe if we all shout about it (again), Figma will finally listen and add it to their to-do list. who’s with me? catch ya later! flo

Simplified use caseImagine there’s one component that is the same on iOS and Android but different on Web I create a Platform property with values of iOS, Android and Web In order to allow all selections, I need to have three variants, one for each Platform property value, even though there are only really two variants.This introduces a risk of someone editing the iOS variant and forgetting to make the same change to the android variant since there’s no way to merge these variants together. This is a really simplified use case to illustrate the point, but I am working with components with 9+ properties, each with multiple values. This creates many duplicate variants and makes it really hard to keep track of the duplicates and keep them all in sync.  Please add this! It would really save me time, headache and reduce the number of variants of components.

It is driving me crazy when I follow someone, if I need to zoom to desired level, I loose the follow and I have to follow again. I just want to be able to continue following the user on the desired level of zoom I choose.

Is it possible concatenate variables within another?

Would love to be able to save and apply object styles such as a fill color and stroke color and properties; just like in CSS.

When using the eyedroppper/color picker via the shortcut ‘I’, you can select a color and the RGB value is copied to the clipboard, letting you paste this value to copy the color. (Very nice feature!)See below:  However, when pasting the value from your clipboard, the format is like: RGB 151 71 255. Figma does not recognise this a color when trying to use this value. Please see below, when pasting the RGB value in to a field that expects a colour, the RGB text at the start prevents Figma from recognising the 151 71 255 following it: Existing Process: Pasting the result of the Pick Color tool, automatically includes the text ‘RGB’Result is #BBBBBB or RGB 187 187 187You have to remove the ‘RGB’ yourselfOnce RGB is removed, then Figma will interpret the colorSuggested Process:Pasting the result of the Pick Color tool Figma recognised the 151 71 255 then changed the color to the RGB value provided.

What if you we could easily control the thickness of lines, arrows, and other elements on the board? 😍

Hi all,it would be really REALLY useful to be able to share a link to a screen in a specific state, for example with an overlay opened. We’re writing user stories, and both client and devs need to visualize the exact screen, in a specific state.In that case, with the modal overlay opened.Currently, i can only get a link either to the screen in the design mode (right link to the frame, copy as link to selection) so without any component state or opened overlay, or the link to the global prototype starting point.

Hello, currently using the Export widget is very cumbersome. You have to click on a project layer, expand the Export widget, select a file size (1x, 2x, …), select a file format, expand the preview and save. This has to be repeated with EVERY attempt to save! When will you change this so that the widget expansion, selected format, file size and preview display is remembered!

At times I can get a buildup of available library updates. Often it’s a mixed bag of complex components and “easy” updates with just some type and colors adjustments. Nothing breaking.In those cases, I can either accept ALL updates available which might break stuff all over a page or document, or accept individual changes one by one (which takes time).Since updates are grouped like commits, why isn’t there a functionality to let me accept, let’s say, a commit with 40 icon updates, along with a color update of some 20 colors… without accepting a few complex component updates? All in all, what’s everyones thoughts on adding another update option?Accept ALL updates Accept a “commit” Accept individual update (part of commit)Would make life much easier. Quick design experiment: 

Recently a new member of our team (who was granted edit privileges) deleted our component library file, which led to a series of issues until I, the admin, realized what had happened and restored the file from trash. However, there was a chance that I never would have realized what happened, or that the user could have gone into the trash and permanently deleted that file, both of which are horrifying outcomes when it means re-creating the design system and all documentation from scratch and then replacing component instances across dozens of files with the new one. It would be FANTASTIC if I, as the admin, could prevent editors from deleting certain files, whether that’s on a per-file basis or with an across-the-board rule like “you can only delete files that belong to you” or “you can’t delete files in this project.” Such an option on all the paid plans and up would definitely help me sleep better at night!

I have been documenting our design system best practice in Confluence. I would like to embed the Component Playground into the doc. This would allow people to preview the ui within the doc.

The way the web works is that elements nested within a parent element will inherit the font-family defined in the parent unless explicitly set on the nested element.It would be a really useful feature in Figma to allows something similar where you can define a font family for a frame so that all the text elements inside inherit that font-family, so if the font-family needs to be updated you don’t need to change the font-family for every text element within the frame. However, the nested text elements with a font-family explicitly set would remain unaffected.You could also do something similar with text styles where a text style can inherit from a parent text style so you can make more broad font-updates to your text styled without having to change each one individually.

Event listeners could improve prototypes efficiency and limit the number of workaround to replicate common interactions on websites. OnScrollUp OnScrollDown (left or right as well for Horizontal scroll with an offset value) E.G : Menu expanding on scrolling up. Right now this is almost impossible to simulate, while being a pretty common thing. (i mean yes, with increasing a number variable or decreasing it and check the previous result, which asks for a lot of onMouseEnter and possibly deactivating other interactions). It would be great to listen when user is going up or down the page. OnView (with offset trigger and possibly onLeave) For example we have a page with sticky elements, like filters, that need to disappear when the footer enters the visible area of our prototype. As of now, we need onMouseEnter interaction to change visible state with booleans. This is a problem, because people won’t be able to see these interactions when on mobile. So triggering a bloc when it is onVi

The developers and I are currently refining our handover process. I discovered, that for the VSCode Figma plugin the Feature “Focus mode” is available and was wondering why I wasn’t able to access it. I found out that it’s only available on the organization plan and above.Since I know that the huge canvas is overwhelming (even if it’s structured in sections) this feature would make the handover process way easier and is a huge benefit for developers, regardless the team size. It also saves time for designers, as they don’t have to invest as much time in neatlessly structuring the file and explaining the structure in detail to devs.We are just a small team of three and won’t be growing soon, therefore upgrading to another plan does not make sense for us.Is there any chance this will be available for the professional plan as well?

I am making a prototype game UI for a studio. This sometimes forces me to create scenarios that are not common to classic web or mobile app usage.In this particular scenario I am making a Diablo-like type of mouseover. In short, when mouse is over an item, its description tooltip appears and when mouse leaves the tooltip disappears. Pretty standard. There’s an extra bit that the moused over object needs to be clickable. I am unable to achieve that with current Figma tools so I am dropping this simple idea for overlays to improve tooltip making. First, let me describe the solutions I already tried and their downsides:I am making a button component that has three variants: normal, hovered and pressed. The hovered variant is displayed while hovering. Within that variant I create a frame which acts as a tooltip and appears right beside the variant as its integral part. Downsides: When the component is placed on any canvas, the tooltip within hovered variant is subject to z-depth, meaning i

Hi I want to keep ("Preferences" > "Snap to pixel grid") enabled, while being able to:Center a shape with perfect precision. Freely move a shape while snapping to pixel grid when possible. Disabling ("Preferences" > "Snap to pixel grid") can be useful when trying to perfectly center a shape inside another. Examples:https://forum.figma.com/ask-the-community-7/why-it-doesn-t-align-in-the-center-properly-9206 https://forum.figma.com/ask-the-community-7/perfectly-centering-22683 Having ("Preferences" > "Snap to pixel grid") enabled by default can cause issues for beginners. Having it enable can be useful too. So, in order to have “Center a shape with perfect precision.” and “Freely move a shape.” we shouldn’t lose the ("Preferences" > "Snap to pixel grid") feature. I think the best solution would be to implement this feature, so all of these needs and issues can be resolved. Let’s say a new option is added for this, as a result:(“Position” > “Align horizontal centers”) butto

Love the new Typography Variable release, but it falls short for our use case. Our goal is to use variable modes to switch styles between our 3 brands. 2 of those brands use all caps for headings, the other brand uses sentence case. We need to be able to bind a variable to the case of a character style (As typed, Uppercase, Lowercase, Title case, Small caps). Without this capability, when switching modes from brand 1 to brand 2 for example, we are getting the default case for the character style (sentence case coming from brand 1). We would then have to go through our designs and manually type in all caps for all instances of headings in brands 2 and 3. Certainly not ideal and will lead to inconsistencies / places where manually typing in all caps are missed if we went this route. Until binding a variable to the case of a character style is an option, using typography variables isn’t feasible for our use case.

Hello,I worked on renaming the variables of our Design System. This was done on a branch, and despite the change in the naming convention, I was careful to rename and not delete the variables in order to not lose the relation.Since some of these variables were previously implemented by the Dev Team it is important for us to track which variables have been changed and what was the original name.I thought you could see the previous name while merging, but no, it only show the change of color value.Where can I see the matching between the old and the new name ?  

In the prototyping part of Figma we can use expressions when using the “Conditional” prototype action. I’d like this functionality to be extended to be used when applying a boolean variable to show/hide a layer or toggle between component variants. The exact same logic/functionality used in the if statement could be used to create a true or false result.Some examples of desired expressions would be:activeIndex (number) == 4 isEnabled (boolean) != true option1 (boolean) == true and option2 (boolean) == true Example situation and ideal scenarioWhen creating a button component with a default and active state, you can toggle between the two states with a boolean. When having 5 buttons and only wanting 1 to be active at the time (like in a tab bar), you’d need every button interaction to set its own boolean to true, while setting all the other booleans to false. Add more buttons and you’d need to add new booleans, edit every button and add additional actions.In the ideal scenario, you’d be

Hey there, I’m currently using Figma slides for some presentation work but there is only Right, Left, and middle text alignment and there is no “Justify” available. I know it sounds like a silly feature request but it is actually very handy and unique when the text is justified. Thanks in advance!

After an AI Summary is generated, I’d really like the ability to edit text in it such as the Title, add/remove bullets, remove the datestamp, etc. Because it’s not always the perfect summary, and at the moment we can regenerate a new summary but we can’t simply edit the summary.  I’d also like the ability to create an AI summary from a block of text in Figjam.

Request the addition of setting relative size options (e.g., percentages, vw, vh, em, rem) in the Auto-Layout feature. This would allow for more efficient responsive design, eliminating the need to create multiple instances for different screen sizes. 

It would be amazing if Figma’s Slack integration offered live previews of individual Frames that you could post in channels. I find myself sharing a PNG copied from Figma to communicate design updates, but when changes happen, I have to rinse and repeat that process if people aren’t jumping into the files themselves. It’s often easier to just send static images and get immediate discussions going in Slack versus using Figma’s commenting system. How cool would it be to have live previews of a selected frame from a Figma file embedded straight into a Slack post? Slack shortcut workflow would be something like: “Embed frame from Figma file” Paste URL to Figma file Select from dropdown the Frame you want to embed Click Share, and you have a preview that updates at an interval. It wouldn’t even need to be realtime, but maybe having a refresh action/button on those embeds would tell Figma to fetch the latest preview. Clicking the embedded image would display a full-size preview in Slack, j

Can you add a feature to the plugin API to allow debugging a plugin in the browser using localhost? Currently the only way to test the plugin in the browser is by publishing it.