Suggest a Feature

Why you placed this button so far? It would be nice to group all the buttons together. Now I have to move my cursor far from other actions I’m working with.  

Figma supports enabling/disabling some OpenType features from the UI.https://help.figma.com/hc/en-us/articles/4913951097367-Use-OpenType-features From the plugin API I can see which features are being enabled withhttps://www.figma.com/plugin-docs/api/properties/TextNode-opentypefeatures/but the property is read-only. How can I programmatically enable/disable some OpenType features?Also, is there a reason why it’s accessible on UI but not Plugin API?

Similar to linking the string variable to component properties to update the variantWhy not component linking with same solution? Just need to have same structured nameThis enables component usage mapping, figma make also can easily configure the global component if we have this function ready and running

I would love to see the ability to define a set of brand colors within a Figma Buzz template that end users can easily apply to (parts of) text.Specifically, it would be great if template creators could: Add a predefined selection of brand colors to the template. Make these colors available as text color options for users of the template. Allow users to apply these colors to specific words or text selections (not just entire text blocks). Use case:For branded social posts or marketing materials, users often want to emphasize or highlight a specific word in a headline or sentence using a brand color.At the moment, users can technically change text colors by unlocking the template. However, this removes all restrictions.What’s missing is a controlled middle ground: Users should be able to select a word and apply one of the predefined brand colors.

It’s a distraction to look at the files that I won’t be using again. I want few files to be stored but not as active ones. It’s better if we have tabs or statuses for the files like active and archived. Did you guys feel the same?

Another post requesting some way to differentiate pinned tabs from each other.The option to change the favicon, colored, or letting the title run into an ellipses — one of these or all of the above. As it stands right now,  having them as a small squares with no way to tell them apart doesn’t make them nearly as useful.

I’d love to be able to copy and paste conditionals/variables statements, this would save time and errors. For example, I used a similar if statement multiple times and just needed to change 1 or 2 variables and numbers. But to do so, I had to re-write the statements every time.

I really like the idea of having the UI panels auto hide/show on hover from the left and right edges. It makes the whole experience feel much cleaner and more focused, especially when you want to fully immerse yourself in the working space. You still get quick access to the panels without them constantly being in the way, which feels nice and intuitive.

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

I’m often going through my Recents to find my files, and will often click on the file I’m looking for that comes up first - whether it’s the prototype or the design file. It’s annoying that they’re saved differently. I wish they were condensed into one item that could give me the choice (open as proto? open as design?). Though, also, I’m also almost never trying to open up the proto from my library. I’m almost always going to the design file.  

I think Buzz is a great idea - along with social media templates, maybe email templates could be a cool addition as well (if Buzz is a bucket for all things promotional)

Our team is automating workflows with AI, and we’re loving Figma Make. Only thing is, we can’t collaborate via comments like we’re used to in Figma. Any way to drop comments/feedback right in Make so we’re not bouncing between tools or risking things getting lost?

In the Figma editor, you can change the blend mode and opacity for Sections. But blendMode and opacity properties is missing in both Plugin API and REST API, so it is not possible to read/write it. Please add these properties to the SectionNode object.

I prefer to use my mouse to drag font size up and down to dial things in but the interaction zone must be 1 pixel in size at the moment. In comparison, the drag zone for line stroke is massive and never an issue. I’d be so happy to have this improved, although my mouse accuracy has gone up as a result XD 

Implement variable font property in plugin API and rest api Unfortunately it is not possible to get the complete properties for variable fonts via API access. Please implement the CSS property “font-variation-settings” for “wght”, “wdth”, “slnt” … “opsz” Or have I overlooked something, how do I get the information via the APis?

All the time I work with component variables and for content on the screens I need to pick random variables. Would be very nice to have the button to not change each instance manuallyThank you

Team-Scoped Commenting for PrototypesDesigners frequently need feedback from multiple teams (Product, Engineering, Marketing, Legal, Leadership) on the same prototype. Today, separating feedback requires duplicating files or links, which introduces version drift and overhead.Proposed solutionEnable team- or audience-scoped commenting on a single prototype link. One shared prototype URL Comment visibility determined by: Email Domain Team / workspace group Reviewers only see comments from their assigned group(s) Designers see all comments across groups Key capabilities Create multiple “feedback groups” per prototype Group-only or designer-only comment visibility Optional group switcher

As a math and science teacher who uses Figma every day, I would like to request that superscript and subscript be added as options in text boxes on FigJam boards. Please! It would be so helpful when typing exponents, chemical formulas, and more. Thank you! -A dedicated and loyal Figma enthusiast

Within the canvas, I’d like the layer panel to display only the items that are currently within the visible viewport. Without working with the wrapping into new sections feature.At the moment, the panel shows one long list of all layers and frames, which makes navigation slow and cluttered—especially in larger files. Filtering the layer list to what’s in view would: Improve focus and readability Lowering level depth – more flexible way of working imho Speed up navigation in complex canvases Reduce cognitive load when working on specific sections Optional nice-to-have: a toggle to switch between “Visible frames only” and “All layers”. If anyone has tips and tricks, please let me know!

In Finland, we have to attach the invoices to all card payments for bookkeeping. Now I need to every month to go to Favro and manually download the invoice. Please add a feature where I can define an email address for the invoice emails and automatically send new invoices in an email with the PDF invoices attached so that we can automate the download and processing of the invoices. The subject of the email should have the same structure each month ("You Figma invoice YYYY-MM-DD) and the PDF invoice name should be unique and contain the date of the invoice, for example, Figma incoice YYYY-MM-DD

Hi all,Recently, there was an announcement that it is possible to generate diagrams and flow using Claude Opus with the Figma “connector”. Now I wanted to try this but it seems that Figma make does not use the Figma connector, because it cannot create anything on Figjam. This is frustrating, it means the Figma subscription is not enough at the moment to be able to access a feature mainly thought for Figma users.I hope this gets solved. So far, make was able for me to turn excel files into csv flows, but it would be awesome to be able to make Figjam components directly (like the demos show when using Claude).

There’s no visible scrollbar in Figma prototyping mode. Yesterday we’re having user testings and once again this same topic popped out. Some of the users didn’t thought that they could scroll prototype because scrollbar wasn’t visible. One of the user was using laptop’s touchpad and he wasn’t able to scroll with only using touchpad. Guiding user how to use prototype during test can harm testing situations. Atleast it’s sure that if user thought that he can’t scroll it leads to biased feedback about product. If there’s some reason not to have scrollbar it could be atleast optional feature that designer could turn visible scrollbar on from options. It’s not only who has came across with this weakness in Figma. Here’s old Spectrum thread about same topic but Figma hasn’t done anything for this yet and I hope

Let’s follow the desktop browser mental model of putting cursor focus in the search input field after opening a new tab so users can immediately begin typing a filename without having to use the mouse to click into the search field first.I’m so used to being able to open a new tab with Cmd+T and immediately begin typing my file name without my fingers leaving the keyboard in Chrome, that it would honestly save me quite a bit of time in the long run in Figma too. 😅I can’t tell you how many times I’ve opened a new tab and begun typing before realizing my cursor wasn’t in the search field yet. (The number would be embarrassing, and continues to climb!)

I can’t seem to change text colour inside shapes. I only get the option to change the background. The only way I was able to get it to work was to create a separate text layer change the colour there and then paste it inside the shape text area.

Have you ever sent over a design file for feedback to open it a week later with 40+ comments? I have and I’m sure you have too. The problemIt takes a lot of time to review comments after a feedback round. It can get repetitive and sometimes the feedback can mean the same thing but being written differently. If you have a lot of different commenters, the list becomes long and tedious to go through. The solutionOne button to summarise comments that will produce out a summary and propose the next steps. Each summary should include links to the root comment so the user can review the original comment. The summary could be in a tab in the comments panel where you can toggle between original comments and summary to easily go back and forth.