Suggest a Feature

Analytics are critical for understanding adoption and impact in Design Systems. Right now, insights are tucked away in individual library modals, which makes it difficult to monitor patterns at scale.A single Analytics hub — with dashboards, trends, and cross-library metrics — would create a far more useful workflow for teams that need to track quality and usage over time.

After discussing the subject at length with the support, here’s a summary of what Figma allows and doesn’t allow in terms of library sharing (hint: it’s not that simple), and how it could be streamlined: Currently, as a component library creator, here are the options you have in order to share your library (I will not include the options for a Starter plan, they are legitimately limited) As a Pro user: Publish it and share it within your Team (to users you - or your admin - pays for) using the Team library feature. They can access the component anywhere inside the Team’s files, and get realtime updates. Links are preserved throughout even with multiple files. Share it on Community (to users outside your Team): they can duplicate the file to their respective spaces, without live updates. Links won’t be preserved if the library includes multiple files. Share it via link (view-only) to selected users: they can either duplicate it (although not as easy as a Community file), or use it as a

before 🤗Previously, you could generate a [no expire] tokennow 😔If users rely on tokens to access the figma open api, forgetting to replace expired tokens can cause serious problems.The expiration date of the limited period will cause the figma token to no longer have usage value. 

I get nervous having edit-access to a Figma file sometimes, especially as an engineer. I don’t want to accidentally make a change to something in the file. It would be great if there was a way to switch myself to a read-only mode (temporarily) to avoid accidentally breaking/changing something. For now, I’ve just been creating a new branch. If I change something on the branch, then I don’t need to worry.

Whatever I try, I can’t seem to work with .mov or .webm videos with transparent background on Figma. Whenever I upload them, I get a black background. Am I doing something wrong? Or is there a workaround for this?

The text in a frame can be independent of other frames, or it can flow between connected frames. To flow text between connected frames, you must first connect the frames. Connected frames can be on the same frame, or on another frame in the document. threading text linking text frames linking text boxes

When we add a delete or close button on a list item or another element on the prototype, the button interaction should delete that item. This way, we don't need to create component structures and states. We can restore the deleted item with reset state. I tried to explain it with an image.explain imageThe red button was added to delete that row. Within the actions area, there will be a “delete item” feature, such as ‘undo’ and “close” operations. In the green marked area and on the prototype, that button will remove that item.

How can I view Figma prototypes on my mobile, or is that currently only for web desktop?When I copy the share link and open in on my mobile, it opens up in a very small view and completely unusable on phone.

The window for NFL groups in the direction of host potential customers upon pre-draft outings shut closing 7 days, nevertheless there are continue to status trickling out. The hottest of individuals is Texas offensive deal with Kelvin Banking companies Jr. , a projected 1st-spherical choose who frequented the Fresh England Patriots at 1 place inside of the Wilson of KPRC 2 Houston was very first towards write-up the check institutions Jr. , 21, is coming off a 3-period occupation with the Longhorns that noticed him start out all 50 video games he looked within and get paid many affected individual honors. Inside of 2024 by yourself, he acquired the Outland Trophy as the state's easiest lineman, the Jacobs Stopping Trophy, and was called initial-staff All-American and initially-personnel at exactly higher than 6-foot-5 and 315 bodyweight, Financial institutions Jr Mitchell Wilcox Jersey. brings together superior establish with an explosive initial phase and natural and organic actions t

test

How to send or import multiple frames to Figma Make from a Figma Design file?It seems that it is possible to send one frame to Figma Make and it will create a new Figma Make file from that one frame. However, when multiple frames are selected (e.g. different screens of the same prototype) then the “Send to Figma Make” option disappears.I can also see an option to Import from Figma, but the interface for this is terrible when you have thousands of Figma Design files in your enterprise and they each have multiple components within them. Worse still, it seems you cannot import a frame, only components that have been published.Is there something I could be doing differently that would make it easier to import multiple frames from a Figma Design file into the same Figma Make file? As a designerI want to be able to import multiple frames into Figma MakeSo that I have an interactive prototype of what I have designedGiven I have multiple screens designedWhen I select those multiple screensThen

I’d like to know WHO created every annotation, just as with comments.Or at least make it optional. I often want to add “comments” for stakeholders that I want to persist, be visible always, and not be resolvable. So I go with annotations. But I want my name attached to them. At least sometimes.And I find myself asking people “who are these annotations from” quite annoyingly often.

The main source of inspiration for this idea was to match the keyboard shortcuts themselves to different keyboard layouts. Right now, users who don’t use US keyboards have to memorize the location of the keys, rather than to use the actual character location to be able to use the shortcuts. Those involving this region are primarily the case: ABNT2 layout (Brazil). And here’s an example of confusing shortcuts: Although this problem could be solved by just rebinding the shortcuts to the actual character and not the location on the keyboard, I’ve noticed there are some other issues concerning key bindings. On this forum post, a member of the community asked for help on backing one layer level with a different shortcut from what Figma has right now. This makes the user adapt their workflow to the tool, and not the other way around — and that hinders efficiency. It would be nice if the tool itself provided some sort of customization on this regard. Although being a workaround, Mac users c

The Problem In figma, it is currently not possible to persist certain compository styles without having to think of all the possible use cases before and putting them in there, or to provide a component just so that it can be used as a reference, a starting point. The reason for this is that once a layer is in a component, it cannot be replaced, removed, multiplied or reordered. This makes sense, but limits what a component can do. Examples Buttons that are capable of showing any icon. The Icon can only be replaced by a different icon of the same size or the same parent component (icon/*). Meaning, that all icons that are available need to be thought of before. This breaks the components capabilities, because it all of a sudden needs to be aware of the icons it can display. Text-Content Content that consists of a variable structure of headlines, paragraphs, lists, quotes, etc. Designing a Template for a view that will receive content from, for example, a CMS is impossible as a

Sometimes when too many tabs are open, their names are getting truncated and it would be quite difficult to jump from one tab to another. E.g. tracing a component back to design system to check master component and documentations before jumping back to working file, it would take some time to locate where the working file tab is. Suggesting a feature to incorporate a search bar (collapse if it’s not activated) or even just a keyboard shortcut to let user quickly scroll through and search among opened tabs. Something like command+tab in macOS or control+tab in Figma but with better visual and thumbnails.

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.

When clicking “Review library updates” (with the blue notification dot on the library icon), the Manage Libraries panel still opens to the Recommended tab instead of Updates. This makes it easy to miss actual updates — especially since the Updates tab no longer displays any visual indicator to show that updates are available.The Recommended tab is useful, but it’s far less important than reviewing and accepting library updates, which happen more frequently and directly impact active work.Two improvements would make this clearer and more consistent: Default the panel to the “Updates” tab whenever updates are available. Add a visible indicator to the Updates tab itself (e.g., a blue dot or badge count), so updates remain obvious even if the user switches tabs or reopens the panel. These small changes would make library updates easier to notice and act on, especially in large files with many linked components.

Similar functionality to AE, and also Figma’s native Sweep functionality with Ellipses, the ability to trim any path’s Start and/or End points would allow for more optimized design and prototyping. Some examples: Elegant design/prototyping of custom bar and line charts as well as interactive sliders (RN my adjustable horizontal charts and sliders components are leveraging AutoLayout right padding to adjust a stroke set to Fill) More advanced/custom loader animations Easily make drawn path animations

I have multiple Figma accounts with multiple clients and multiple projects. I also have a handful of designers on my team. Because all of us manage changes requested by the client, we often miss some tagged comments because the structure of notifications in Figma is just a long list. I would love to be able to tag comments as “To do list” and then reference and jump to all those action items and mark as complete. The more I convince companies to adopt Figma, the more comments there are (by non designers). I’d also love to tag comments as “ideas” or by topic so i dont have to guess click on everything to see which comments i need to look at. Essentially I want to “View groups” of comments that are most relevant and just hide the ones that are needed on the page for others but are in my way when I’m doing my work.

Working with comments in Figma is still very inconvenient. There are several features that are greatly missed for easier management: Group management of comments. For example, to select a group of comments and move them on the page, to another page, delete them, or resolve them. For now, I have to go through and delete comments one by one! Lack of access policies. Case: I shared the prototype with a client, but I don’t want the client to see the internal comments from team members (comments from the editing mode are accessible in prototypes for some reason). «Done» all comments on a page/file. Basic filters: by user, specific day. Tags! Different team members comment on different topics: UX, art, dev, business, etc. There needs to be a way to filter comments not only by team members but also by themes. The simplest thing: hashtags! For example, we could specify something like #front-end in comments, and then click on the hashtag to see all comments related to that topic.

It would be really nice if I could pop out the variables into their own window. Currently I can only have it as a dialogue in Figma, which means it always overlaps over my design and especially on smaller screens this becomes quite the issue. I often need to see variables and my design at the same time, so moving it to a second monitor (or even on a laptop quickly switching with alt + tab between the two) would be very helpful.

Many people have said the same thing, but I’m here to recommend supporting percentages within auto layout. I’ve seen many people asking for the same thing.Percentage width auto layout would help us be more efficient. Auto layout “Fill container” is great for sections being sized equally (50/50 or 30/30/30).When we’re designing content with sections, the sections are generally not the same width as each other to indicate importance.Myself and many other designers would love to have autolayout support something like this:The main container has the same spacing all the way around Each section takes up a specifid percentage of the container (70% and 30%) When the modal grows and shrinks, those sections maintain their width of 70% and 30%  Without spacing With spacing 800px wide     1000px wide      This is what autolayout currently supportsIf we use auto layout, each section must be a specified width or the same width as the other sections.  It makes

Hi Figma team 👋 I’m a product/app designer and I work with large, complex files that contain many components and extensive documentation. The new behavior of Figma Annotations — where they briefly “float” or animate during scroll before becoming sticky — is extremely distracting in daily use. Because my design system files are dense and rely heavily on annotations, this micro-scroll animation triggers constantly. It feels like a bug or glitch every time I move through a frame, and it makes focused work much harder. Feature request:Please add a simple toggle to disable this animation and allow annotations to be instantly sticky (or fully static). Even a basic on/off setting would significantly improve usability for designers working with large files. Thanks for considering this improvement!

I was thinking of what if @figma adds CYMK Color, which can be used for printing purpose. Recently was designing a poster & wanted to print it but, after printing colors were changed. So i thought what if @figma can add CYMK Color in the software. Let me know what you guys think

We have a Design System with parent components composed of nested instances. Both parent components and nested instances are in the file “A”. To avoid having thousands of components available within the Assets when publishing the library, the nested instances are hidden with “.” at the beginning of their names. The problem: When using the component library from file “A” in file “B”, everything works fine. The issue arises when a nested instance from file “A” requires an update. Firstly, it does not allow me to publish the nested instance update without removing the “.” from its name, and I also cannot publish the parent component containing the updated nested instance. If somehow I manage to publish the parent component, file B will prompt me to update it, but the updated nested instance does not receive the changes made. Is this a bug? Or what is the correct way to work, update, and publish nested instances so that they always receive their updates without cluttering the Assets librar