Share Your Thoughts

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 creating a new project within a workspace, you’re able to change access to invited people only, but it gives access to everyone in the project’s containing workspace. Below is the screen with messaging when I change access to Only invited people. “Only people you’ve directly invited can access this project” means, to me, that only people I’ve sent an invite to within the project space will be able to see its contents. However, when you create the project and go into “Share”, everyone in the workspace where the project was created can access the project (Shown below). You have to go into that row and remove the access of that group. This feels deceptive and creates an unnecessary step

When aliasing a color variable to another (img 1), or using it directly on an element (img 2), we should be able to override the opacity without the need to create a variable for each transparency variation: Cant override opacity in the alias: Example 2 Cant override the fill opacity:

When working with local variables and tokens I find myself constantly opening and closing the local variables panel. It would be nice to have a shortcut added for displaying and hiding that panel. If there is not a shortcut added in first version, then this action could be listed in the MacOS menu bar as a command, so that a custom MacOS shortcut could be added,

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!

Hi Team,I am writing to implore you to restore a small but critical interaction detail that was removed in a previous update.The Issue: Previously, when a user adjusted a property via a slider (specifically Drop Shadows, Strokes, or Corner Radius), the blue selection bounding box would temporarily disappear. This allowed us to see the exact effect of the change in real-time.Currently, the blue selection outline remains visible while adjusting these properties. Because the outline sits directly on top of the edge of the element, it physically obstructs the pixels we are trying to style.Why this is critical: We are designing blind: It is impossible to fine-tune a subtle shadow or a 1px border when a 2px blue line is covering it. Broken Workflow: What used to be a fluid process is now a friction loo

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

Dear Figma Support Team, I am writing to inquire about the current support for color fonts in Figma. As a designer, I greatly appreciate the versatility and creative possibilities that color fonts bring to my work. I have recently been experimenting with various color font formats, such as OpenType-SVG and COLR/CPAL, which allow for intricate multi-colored typography. However, I have encountered some challenges when attempting to utilize these fonts within Figma’s design environment. It appears that Figma currently lacks full support for color fonts, as I have experienced difficulties with the proper rendering and editing of these fonts within the platform. It would be immensely beneficial if Figma could extend its capabilities to fully embrace color fonts, enabling designers like myself to fully explore the potential they offer. Color fonts have become increasingly popular, allowing for more expressive and engaging desig

Feedback 1: since Figma Desktop App version 126.1.2 text styles picker always shows libraries of styles in collapsed state. It’s super annoying, since search doesn’t work until you un-collapse it.Feedback 2: please fix up/down arrow behavior on styles. Example: the text span has style “Body/Emphasized” → I press arrow up expecting it to switch to “Body/Emphasized” → instead Figma selects “Headline/Regular” (the style that just happened to be below the search box). I papercut myself on this multiple times every day for the past couple of months now, at least.Figma’s a great product, I love it, but bugs like these are a big let down for me. I believe basic features like text styles should be dogfooded more to remain best in class. 

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.

You can duplicate a file, and create a branch of the current file but when your in a branch you can only duplicate to a new file not a new branch. I always have this need I create a branch and don’t want extra files I just want to create extra branches off of the branch not the original file which has been significantly modified at this point.

Picture this: You step into a role at a rapidly scaling enterprise launching multiple products simultaneously. Initially, team autonomy feels efficient. Everyone builds their own UI elements and moves fast. However, as the product suite grows, fractures begin to appear. You start noticing inconsistent visual styles, duplicate code, and misaligned user interfaces.As the developer responsible for creating cohesion, you realize the solution isn't just "fixing bugs", it’s implementing a Design System. This system serves as the anchor that keeps all teams aligned, regardless of how fast the organization grows.Bridging the Gap: The Birth of a Unified Sys

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,Bowe

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 alltog

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

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?