Share Your Thoughts

Hello, In my design system, I would like to map a container variable that would be a fixed value in desktop but a fill container in mobile.  I tried by setting a fixed value of 0 get the attention of the designers in order to make them change the value on their own but is there a way to automate this directly in the variable? I understand that this is not how variables are working but if there’s a workaround or a way to fix this, I’m taking it <3 Thanks ! 

It would be helpful if we could pick from existing variables when naming a new variant property maybe through a dropdown or suggestion list to avoid name mismatches and improve speed. 

Management of Dev Resource links is critical in our design systems. We are developing a multi-brand design system at Thryv that supports both React and Vue.js, and need to add resource links to a composed Storybook which documents a lot of components.Dev resource links are not editable from branches. We have our main file set to view-only so that design contributors have to branch to work for system integrity. They can’t add the dev resource links as part of their definition of done, putting the weight of that responsibility on the owner(s). Dev resource links can’t be automated easily for repititious components like illustrations that may all use a shared resource, but each component needs a link (and yes, I understand variants -- they are not appropriate for this circumstance). Between being an Electron app and lacking standard accessibility controls, hidden buttons that reveal on hover, and the links themselves changing positions after being saved, it’s challenging to work with some

For sales or anybody that want to show data about his product or company, it would be cool to be able to add line charts or pie chart easily. Right now we need to edit it ourself, but non designers would not be confortable to ajust it. It will be fun to have a tool to create chart where we just have to put our data and it create the chart.

It seems that all the emails I was getting previously on approved seats has disappeared. The only settings available to me now are for auto-approved seats. However, as I’m working in an organisation with multiple admins I would still like to get an overview every day on the approved seats by my peers. Is there a way to re-enable the general emails for approved seats, regardless if these were auto-approved seats?

the idea is simple. often times I am creating a design, in witch two objects share a curve/edge, but have a different fill color. the only way to make the different fill color is to create two separate objects, but then later on if you have to edit the line you have to edit all instances of the object. or sometimes I have the same object that I want two different fill colors on, and again I have to make two separate objects. the same goes for strokes. so, I sujust that there be some way to within one object have totally different fills and strokes. there is already a way to have multiple fills, but they only layer on top of each other with different opacities, and same with strokes. I think that the different fills and things could be added using this same UI, witch would also allow the mixing of different fills as well. you could also apply / remove the different fills to different area using something similar to the new paint / bucket fill tool. anyways, I know this might be a bit ch

It’s a great idea when I start a dialogue in Figma with other designers to give them the opportunity to invite them into the conversation. Some kind of sound signal or popup so that they can hear that I am calling them to talk 🤙. like a phone call. accept or reject. Only for participants who are currently working in the same file. But in the future it is possible to call me to a specific file and talk there. And I will immediately get into the conversation on the file that I am invited to. Because every time I go to a private chat on Telegram or Skype and ask them to talk to me in Figma.

One of the issues that I’m encountering is because their is now viewport height or width options, you aren’t actually able to independently scroll multiple frames. Ie if you want to be able to scroll a side menu bar independentally of the content. You actually aren’t able to do this unless you set a specific height for the page and then clip the content to be able to scroll the overflow.The issue with this is because the you have defined a fixed height for the page, it’s not actually recognising the dimensions of the viewport, so if the viewport in the browser window changes it’s size relative to the fixed height you specified in the Figma Sites. It actually breaks the scroll behaviour because you haven’t been able to tell the page that the actual height of the page it needs to be referencing is not the fixed height defined in Figma Sites but should in fact be 100% fill to the vertical viewport height instead.

In Figjam, I would like to give URL linking to image that I do use in flow chart. Anyone know how to do this as its a small but useful feature. 

I think you are on the right track with Figma Make with the recent feature of being able to select a design system library. However, if you take this a few more steps I think you might have something:Expand the definition of a Figma design library object to include design system concerns including: design components, design tokens, and guidelines (general usage, component usage, accessibility compliance, motion, etc.) - similar to what you can add to the Guidelines.md file. Allow designers to edit all of these concerns in Figma, attaching them to their design system. When the user selects a design library in Figma Make all of those concerns come with it. Think of it as a schema or blueprint for building components and applications. Provide the ability to connect to existing production (React, Angular, Web Components, etc.) components in GitHub so that designer prototypes are rendered with a very high level of accuracy and fidelity. Alternatively, generate components based on the guidel

My colleague was relying on version history and started flattening shapes for an illustration. It would be great when you select flatten from the menu that Figma would save the state before executing the flatten action.

Figma should allow customization of the message shown to users requesting a seat. We have specific eligibility requirements, and currently, I have to manually follow up with each requester to confirm their eligibility. This creates unnecessary administrative overhead, especially with multiple administrators involved.

I think it would be handy if, when publishing a library, I could easily select/deselect:All variables, All text styles All effect styles All layout guide styles All other (ie. components)

Hi Figma Team,I’m a regular Figma user and truly appreciate how powerful and intuitive your design tools are. One thing I’ve often felt limited by during prototyping is the lack of a smooth scroll experience — especially when simulating navigation or scroll-to-section flows.It would be amazing if we could have true smooth scrolling, similar to how real websites behave (with easing, momentum, and natural flow). This would greatly help us mimic real-world experiences more accurately during prototype testing.Hope this is something you consider for future updates. Thanks for all the great work!

I can’t seem to delete other peoples comments they have left. I am the creator / owner of the figma file and can only delete my own comments. Wondering if this is this normal? Why can’t we delete other peoples comments? The only solution I have found is to copy and paste the frames into a new design file which seems somewhat absurd?

I’ve been using Figma as a guest collaborator and I wanted to share a bit of feedback. When I click on a team that has shared a project with me, I’m taken to a team overview page that appears empty or says I’m not a member—despite having access to a project. I only see the shared project by navigating through Recents, which feels a bit unintuitive.It would make for a smoother experience if I could be taken directly to the project I have access to, or at least see it listed within the team view instead of a blank page. I think this change could reduce confusion for guest users and make collaboration easier. 

It’s frustrating that Figma still doesn’t support background blur in overlay settings. We can tweak color and opacity, but no blur—something that’s essential for many interface styles. A common workaround is adding a blurred background directly to the overlay component frame, but that breaks things like dismissing the overlay by clicking outside or smooth blur animations. Blur is so common in UI design today, it really should be a built-in feature at this point.  

Annotations can be hard to find and are often critical. A central spot that allows me to make sure I see them all would be very welcome. I’d suggest clicking an item on the list in the panel should focus the element and its annotation in the main canvas. Thanks.

As a designer, I’m frequently mocking up flows in which a user must scroll down to take an action. In order to accomplish this, I end up removing auto layout and manually moving the content to the intended position.It would be excellent if we could set a scroll position in design mode, or simply use a scroll tool to click and drag the content.

In the right panel of Figma Design, when opening the Variables dropdown menu or applying variables for any numeric input (Corner radius, Gap, Padding...). Next to each token, there is a new thumbnail representing a number value “1234”. It’s disturbing the reading of my variables. How can I go switch to the previous dropdown design ?Thank you 

I’ve started using Figma Buzz to create templates for our clients. I love that I can publish a template, send them a link and then they can use a copy for their own uses without accidentally breaking the design when the guidelines are locked. I also love the bulk create feature within it. There’s just one thing I’m struggling to be able to do. Within our company we create thumbnail covers for all our design files and Figjam boards and slides so that when we see them within our team folders we can easily identify which project is which. These usually have details like what type of file it is, the project name, the client etc. When I add one of these in to my Figma Buzz file, it’s visible as a page in the published template link. I would like to find a way to hide this from the published template link, so that it’s only visible to us. If there’s already a way to do this, please let me know 😄 but if not I would love to suggest this as a feature. 

Default artboard sizes can be added, so that it will be help full to start design and also for prototyping it will be very useful. 

Hi everyone, I’ve been dealing with a bug for years now. We all know that to make a layer stretch with the frame horizontally, we can set its constraints to “Left + Right.” However, when the layer is set to “Fixed” in the Prototype tab, it’s no longer possible to select “Left + Right” in the constraints. I noticed that several people have reported this issue in the past few years(Here). Is there any chance this could be fixed soon? (It’s really frustrating!)

As far as I saw for now, it’s not possible to create an interaction that drives the user to a certain page section.It’s helpful to be able to assign the html tag to our ‘blocks’ and define if it’s a div, section, and so on; but we need a way to assign ID to the divs so we can redirect to specific sections on the screen from everywhere in our site.Example: inside a page we can have several sections (about the company, about the team, about the company values, about the open roles and career paths) and we could include those sections in a footer menu to easily redirect users to their specific section without the need for them to scroll looking through to find the info they are interested in.It’s a normal micro interaction in websites, and it would be nice to have it included in the final feature. 

Currently, when layout guides are added to a component, they also appear in all instances of that component across the design file. This causes significant visual clutter especially in high-fidelity UI screens where the focus should be on the content and layout, not the guide structure used during component creation. We’d like to suggest that layout guides be visible only in the source component, and not inherited by its instances.