Suggest a Feature

The hand tool is not efficient; please allow a “1” click button to be able to scroll vertically to the next frame. It was so easy and did not waste any time. It was a fabulous feature in Jamboard!!!

I’ve noticed a few requests for this, but it really surprises me that more people are not upvoting it. I cannot express enough how annoying it is for me to click on Figma links from a Jira task and then get shifted out of the current design I’m working on, only to not be able to find my way back to it. As a UX manager, I am working on 100 different design files each day, conducting design reviews, answering questions, and triaging Jira design stories. Therefore, trying to remember each file/page location is total insanity. PLEASE add a back button. Thank you.

Allow to change the appearance of a frame on hover, as well as open overlay, so basically allow to add more than one interaction on the same interaction trigger

In my day-to-day I have to approve a lot of branches. While doing that I always find myself scrolling through a list of branches (we have like 50?) and look for branches that have “In Review”. What you think of a way to filter the branches list. I create a demo video but are not able to upload it here so please have a look at my post on twitter: https://twitter.com/i/status/1775507243586245080

I would like to know the exact resolution of my images in Figma. The software should indicate the global , we need to know when the image is too big for example. Like in Indesign, we need to know these two parameters : Actual PPI / Effective PPI The actual PPI is where we see if our images has been oversized or not. And that prevents display problems. In indesign, these informations are in the links panel. Effective PPI is where we see whether or not our images have been oversized. And this helps to prevent display problems. I know this problem has already been highlighted on Can I see the resolution of images I import into Figma? But it hasn’t been addressed yet. I think this might help designers to think about it. Thank you for your attention.

Hello guys! In this picture you can see how my default work file usually looks. Within all those pages i arranged all the little thingies i later use to execute the design. I would LOVE to be able to collapse those pages intro groups, and only keep the ones i keep visiting during the design process. (Usally between Workbench, Home (or whatever), and project modules) The other pages are rarelly touched. Yet i need them there. Thank you!

We should be able to stack frames/rectangles with background blur. Currently, if a frame with less blur is stacked over one with more blur, it overrides the blur of the bottom frame.

Let’s be real, variables have been a total game changer, but there’s still something missing, right? I mean, who wouldn’t love more control over font family, size, weight, and color opacity within variables? It’s time for Figma to level up and give us that extra oomph we crave! Picture this: effortlessly switching between font families, tweaking font sizes on the fly, dialing in the perfect font weight, and oh, don’t even get me started on adjusting color opacity within variables. It’s the stuff of design dreams! Figma, we know you’ve got the power to make it happen. So why not roll out an update, starting with color opacity? Trust us, the design community will be cheering you on every step of the way. Let’s make Figma even more awesome together! 🚀✨

I’m using the REST API to get the version history of files for a particular date range. It would be helpful to be able to specify a date range to return versions for rather than have to look at the latest versions, then request the next chunk, and the next one, etc etc. It makes for a lot of unnecessary requests to the API when you’re looking at a date range that’s far in the past.

When I switch the colors at both ends of the gradient, the process is too complicated. If there is a quick switching form similar to the current line end style, it will be better to reverse the gradient. I hope to adopt it

Would love the ability to link, or connect, comments to one another. Example use-case: Often, when reviewing my peers’ work, I’ll find an issue that appears on several (or possible even all) screens within a given page in their file. Usually it’s self-explanatory to apply the comment/feedback in one place to all other instances of the same issue but that’s not always the case. Or the repeating offense may appear on Screen 1 but not again until Screen 47 so it may not be as easy to associate the issues as being the same thing. Current workaround: There is the ability to copy a comment’s link and paste that into other comments, thus linking them. This works ok but often it’s a pain to have to go and find the initial comment I’d like to link to. Benefit: Linking comments together would create “threads” or “groups” of related comments, therefore making it easier to duplicate/repeat feedback. Another feature of this could be to add visual cues for linked comments. For example, when viewing

It’d be useful if users without edit access could draw with something like a grease pencil or marker to make annotations for themselves. It could be like a layer that turns on and off and doesn’t affect the design file. Or I’d like to know if anyone has found a workaround for this.

Create option to apply layer properties to selected layers using multiselect Sometimes I create a layer and change it, but I forget to select the multiselect first to apply the layer properties settings to all layers selected using the multiselect. It would be convenient if it were possible to change a layer on one frame, and then apply the same changes to all of them using the multiselect. selected layers that were in the layer that was changed

Problem: The manual position I set to the component only appears once, when I have to set it. I cannot reset the manual position if wanted, because the overlay does not reappear after I’ve set it once.

It works exactly how it is on image. And in case of “Hug Content” basically both options look the same. Is there any particular reason for it not to work normally? I encountered the case when I need bottom row to actually be bigger then top one.

I’m having a hard time selecting the right interaction connector, specially when then overlap like this. (see attached) I might be simplifying the matter a whole lot, and I havn’t looked all the potential angle etc. but here’s a start of what I’m suggesting, perhaps the team can look into the matter? What does the community think?

This feature is an open door to disruption in a design system library file. From my testing, I assume this is only possible if a user: Has edit access to the library file Is making changes to an instance inside that library file I never want this to be an available feature to anyone using a design system component instance. Is there a way to 100% disable this feature? Component changes always need to go downstream, and they need to happen as a result of a deliberate change to the main component, never from a user making a subjective decision while implementing a component, and pushing a change upstream. Yikes. 😕

I noticed that there isn’t an option to directly navigate back to files from the Figma Community. It would be great if there could be a feature implemented for seamless transition between the Community and files.

I am creating a wide set of input components, for each of these components I want to add a label option. Ideally I would be able to create a master label with its options like size, label text etc. that I can add to each of the input fields. At the moment the only way I can give access to the label text is to surface the nested components, which then makes all properties for that component visible in the master component within it is nested. I think it would be really helpful if: A property added to the master component can be assigned to a property of a nested instance of another component, e.g add a text property to the master input field and then assign that text property to the child instance of the text label component An alternative to the above could be to allow users to decide which properties of a child instance to show as opposed to showing all of them. So in this example, when I select to show nested instance properties, instead of just selecting the instance for “input

CONTEXT: A team is working on a master design file with a master theme and component libraries. The master design file component are published for use within brand designs. The team needs to generate brand designs from that master design, that are composed of instances linked to the master design. Each brand has its own theme and component libraries that are used to customise colour, typography and components like headers and footers. The team needs to swap the theme and component libraries for every page of the brand design (to update components and typography) USER STORIES: As a designer working on multiple brands, I want to be able to automate swapping libraries across ALL the pages of a design file So that I don’t have to spend hours going through each page manually swapping libraries from the master design theme to the brand design theme. As a developer of a plugin to increase productivity for teams working on multiple brands, I want to be able to automate library swapping withi

So, here is my routine workflow: I use macbook and a extra 32 inch size monitor, I will open 2 windows, one in the monitor for main design, one in macbook’s screen for component usage. I can just copy and paste instance from the latter to the former, I think it is faster than use shift + I or drag from assets panel. But here is a inconvenient situation. when I trying to scale layers’s slide panel in the big windows so I can see more layer name, the small windows’s layer slide panel was be widen too. And it difficult to use, since there are limited space in the small macbook screen. Processing: Screenshot 2024-04-03 at 1.47.23 PM (2).png…

2024-04-02T21:00:00Z Please add a variable icon to the stroke thickness input field

目前我们的工作版本，会涉及很多页面，我们只会把有修改的放在新的figma文档上，这样做的结果导致一个功能模块会分布到很多设计稿里，所以希望增加在frame上添加tag的功能，我们就可以通过查找这些tag来查找文件。

PLEASE never get rid of this feature! Me and my lead creative are SO happy and love it so much. The “HUH” meme cat truly spoke to us. We love Figma!!!

When I annotate text in dev mode, when its line height is set as ‘Auto’, the annotation shows ‘Auto’ too. However, even ‘Auto’ exists as some numeric value, which does not show up in the annotation. Would be great if the line height could be annotated as e.g. ‘Auto, 19’, showing that its set as auto, but the numeric value associated with it is 19px