Suggest a Feature

The idea is to have a stack of fallback fonts like in CSS. This is VERY useful in Asian languages such as Korean, Chinese, and Japanese, where there are several fonts, but they lack good Latin and numeric characters. In those cases, we replace those characters with a nicer font. In CSS, it is only one line. How it works: If the stack is “Avenir, Noto Sans JP”. If the character is in the first font it will use that font, if it is not there, like a Chinese character, it will jump to the next font. In Figma, we need to search for and replace text. Of course, that doesn’t work with variables. Illustrator has a more complex tool called “Composite Font”, just in case you want to take a look. The Asian design community will be very grateful to have this feature.

I think this is a great idea. I understand Figma wasn’t meant to be used for illustrations, but to be honest, the uniqueness of its vector and node system is very useful, and many of us (UI Designers) work for videogame companies, and more often than not we have to find works around some things that could easily be added into Figma. I will create another post with this, but things that come to my mind: Supporting different kinds of strokes (even if they can’t be reproduced by CSS, maybe a disclaimer or a warning next to the setting would be fine). Sticky nodes (vector’s endpoints), this shouldn’t be so difficult given you already do this in Figjma and when imported from FigJam to Into Figma the behavior is still there. Why can’t we just do it inside Figma? Ability to move the anchor point of an element.

Currently in FigJam, you can option-drag copy (MacOS) elements even when they are locked. This seems like intended behaviour, but it is really frustrating when running workshops. I create a lot of templates for people to work in, and then lock them. I expect those elements to be locked - meaning no interactions! Multiple times a workshop, I or a participant will accidentally copy the template we are working in, rather than a sticky note or other element. It’s confusing, takes time to trouble shoot, particularly when zoomed in, and happens all the time. If this is intended behaviour and it’s useful for others, then we need another solution to prevent unintended copying, maybe something like a template layer, or two-level locking (lock content, lock everything)

When exporting Figma designs to PowerPoint, I’ve noticed a few issues that affect the final presentation quality: Fonts become smaller than intended Blurred backgrounds or transparent fills don’t render properly Overall, the visual fidelity of the export is lost In contrast, the Pitchdeck plugin handles these exports beautifully—fonts stay consistent, and effects are preserved. I’d love to see if there’s a way to either improve native exporting or perhaps collaborate/merge with the Pitchdeck plugin to make the export experience seamless.This would be especially useful for teams who use Figma for presentation design and want to maintain design integrity across formats.Would love to hear if others are facing the same issue or have found a workaround!

Z-index, the order in which layers are stacked, is missing in Figma. I would so like to have tooltips, dropdown menus, etc. get on top of all content, no matter where it is put in the layer list...

Not being able to use keyboard shortcuts in the variable collections menu/manager can really disrupt the workflow. Sometimes for example, because I’m so used to ‘ctrl/cmd+d’ to duplicate something, I try to duplicate a variable using this and accidentally end up duplicating something in my canvas. Just adding some simple shortcuts would improve the QoL and workflow with variables. Here are some quick examples: ‘esc’ to exit the menu ‘ctrl/cmd+n’ to create a new variable use tab/enter to choose which type of variable ‘ctrl/cmd+d’ to duplicate a variable ‘ctrl/cmd+r’ to rename a variable

Please add variable presets so we don’t need to search for the correct variable names for different frameworks (mUI, Angular Material, iOS, Android, etc.)

Hello,it is hopefully on the roadmap already but I would love to see improvements that align closer with CSS like token studio offers. General:make an easy token exporter to code in pure css ( a simple file) Solution 1:Let me select if I wantcopy all tokens for a mode select only the few i really want to override (less cognitive load) or right click and hide/don’t export tokens i don’t need per modeSolution 2:Use css loading hierarchyif i set a collection higher up in hierarchy and use the same token names, it should override the other ones 

No brainer. I’ve either had to ask clients to record a loom of themselves going through a Make prototype or me having to screenshot EVERY SINGLE PAGE of the prototype then send them PDFs so they could comment on it.If there’s a new QOL feature that’s gonna be added to Figma Make, it should be commenting.

It’s been mentioned before but the work flow we use for branches is by a custom task ID. Being able to just search that task ID in the search bar and it show the branch would make it so much easier for everyone in our team including devs to locate branches etc. Is there any plans to make these branches searchable in global search?

When I press Command + T, it opens a new file window where I can create, search, or select a recent file. I usually use this to open my existing files. I used to use this process to open my existing file.If there were a keyboard shortcut to directly focus on the search bar, it would make it much easier for me to quickly open an existing file without using the mouse. 

Hello Figma Team,I’m a frequent user of the Figma app on macOS, and I’d like to share a small usability suggestion that could help prevent accidental interruptions during work.When using the app, I often press Command + A to select all elements. However, because Command + Q is very close on the keyboard, it’s easy to accidentally trigger it. When that happens, the app quits immediately and the current window closes, which interrupts the workflow.It would be very helpful if the macOS app could include an optional confirmation dialog before quitting (for example, “Are you sure you want to quit Figma?”), similar to what some other applications implement. This could help prevent accidental closures caused by nearby keyboard shortcuts.Thank you for building such a great tool and for continually improving the product experience. I hope this small suggestion might be helpful for the team to consider.Best regard,Bowen

Dear Figma Team,I love that you have already implemented slide nesting in Figma Slides:Meaning there isn’t only 1 level of hierarchy of slides listed in the lefthand sidebar, but I can actually nest slides to be “secondary” to a main slide, then while selecting the main slide I can choose to collapse or expand the list of nested slides underneath it.I have always appreciated Apple Keynote for having up to 5 nesting layers.I always use this feature to be able to go through a high-level presentation and then dig deeper on individual slide’s topics / subtopics during the conversation following the presentation.Seeing that you already implemented nesting, all of the controls to actually nest a slide (drag and drop), expand and collapse a parent slide, I wonder why you limited this feature to 1 nestling level: a main level and one nested level underneath.I would greatly appreciate if you could remove this constraint alltogether or up the number of allowed nesting levels to 5 as Apple Keynot

SummaryFigma’s text UI supports OpenType alternates for editable text through its typography controls. However, this capability is not exposed in the Plugin API.The Plugin API currently appears to expose only read access through openTypeFeatures and getRangeOpenTypeFeatures.There does not appear to be a way for plugins to apply OpenType features or alternates to a text range.Because of this limitation, plugins cannot implement typography workflows that apply alternate glyphs while keeping text editable. Key DistinctionsIt is important to note that this request focuses specifically on Discrete OpenType Features (e.g., salt, ss01, swsh, onum) rather than Font Variations (Variable Font axes like Weight or Slant). While Figma already provides some control over variable axes, the ability to toggle specific glyph substitutions via API is missing. ExampleImagine the word: babelSuppose the active font provides several alternate forms for the letter “b”.A user may want to select only the first

It is imperative that Figma address the issue of editable text in PDF exports. Clients, legal teams, accessibility—all need editable/scannable live text. Please!

Hi! Turning off “snap to pixel grid” in a Figma Design file no longer changes snapping behavior when dragging frames around. Whether this feature is turned on or off, a dragged frame still snaps to each pixel, no matter how zoomed-in. Note that some other objects (e.g., vector objects) still respect this setting. It’s just an issue with frames, components, and component instances. Note that If I group the frame, I then can drag the group to any sub-pixel location. I’ve restarted my machine, restarted Figma, checked for updates, reloaded tabs, tried it in other design files. Tried it in the client, in Chrome, and in Safari. Same problem. Can anyone else replicate this?

Hi everyone!Wouldn’t be useful to have the ability of creating instance clones that mirror the state of the original instance?Reading this closed topic () I found out there are other people interested in this idea, where changes you make on your instance (text, spacing, size, etc.) are automatically replicated to your instance clone. So the structure would be: master component > instance > instance clone. It would be even better to have the ability to override the clone, so certain features get automatically updated while others, the overridden ones, remain the same. 

Sometimes I want one boolean component property to both show something, and hide something else. It would be cool to be able to not only assign a boolean property to layer visibility, but also to indicate that it should show the layer if the property is false. Example scenario: Imagine a situation where I’m designing favourites section on the app’s sidebar. I want a sidebar to be a component. Now when favourites is empty, I want to show an empty state with a CTA instead of the CTA. And I want to add a toggle that both hides an empty state, and shows a list of favorite items.

UI UX is mainly focus with the User’s Interaction and Designs, various basics that most of the UI and UX designers need to know to measure the interest of the customer, business processes, and product reach. UI is the activity of teams to collect requirements from the customer or organization, and UX is the complete front-end process, as per the interaction with the user and requirements gathered by the UI team. UI UX Designs can be practiced at [url=https://www.fitaacademy.in/]FITA Academy[/url] with intensive and exclusive programsAlso check: [url=https://www.fitaacademy.in/ui-ux-designer-course-in-coimbatore/] UI UX Designer Course in Coimbatore[/url] | [url=https://www.fitaacademy.in/ui-ux-design-course-in-tiruppur/] UI UX Designer Course in Tirupur[/url]  

Why can’t you underline text styles? I get you could just have text underlined in your design system, but it would be nice to simply add an underline to text while you’re designing as well.

Every time I paste the copied YouTube link where the YouTube video is supposed to start at a specific timestamp it starts from the beginning. When I paste the link into the browser the video starts in the correct spot. Has anyone else experienced this and found a way to get the link to start at the proper timestamp?Figma Desktop App version 125.5.6MacOS 15.5

Feature request: Make variables accessible via floating modal optionally.I’m building a personal portfolio and I don’t have a design system or library. I have also not designed several mockups beforehand, so I’m designing inside Sites. For a very small project like this, it’s not unreasonable. However, I’m finding it incredibly difficult to use variables in the same way as I have been doing so in Figma Design. Previously, I could eyedropper colours from my designs and seamlessly create variables because these could be managed from a floating modal. Changes made to my variables could be seen updating live in my designs because the modal could be moved around and did not completely obscure my design. In Sites, I need to constantly be switching between my file and the variables view, this for each variable I want to add and each time I want to make any modification to my variables.I understand that features are different from one Figma product to the next, but if a feature exists across 2

Add the ability to activate prototype effects when a user scrolls to specific vertical positions.For example: Trigger an effect automatically when reaching a certain Y position (e.g., 1836px). Trigger an effect between two Y positions, starting at one point and stopping at another (e.g., start at 1836px, stop at 1936px). This feature would make Figma Prototyping far more powerful, enabling precise scroll-driven interactions and animations across designs.

Is there a way to reset the prototype with an interaction without forcing the user to press R to reset? I’d rather continue the flow and just reset some key components and variables rather than take them out of the flow and start the whole thing again. Resetting variables is OK, but there are a few components (an add to trolley one for example) I need to reset back to its original state but I don’t see a way to do this.

My suggestion for Figma is to add a “slot” functionality to components. This would allow designers to create more flexible and customizable components, by adding empty slots or placeholders within a component. Users could then insert their own content or elements into these slots, without having to ungroup or modify the component itself. This functionality would save time and increase efficiency for designers, while also promoting a more consistent design system across a project or organization. I believe this feature would greatly enhance the flexibility and usability of Figma’s component system, and would be a valuable addition to the platform.