Share Your Thoughts

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.  

Can I edit the variables defined in a published library locally? There is a library file (Say File A) with a collection of local variables defining some string and numbers shown on a component. The component is published (with all variables too) I added this component to another file, say File B, but when I want to edit those strings and numbers locally in this File B, I can no longer see the these variables, nor editing them. Seems like I can only edit the published component in the library File A (if I have edit access) and this will change all the instances too. Can I instead edit it locally, meaning edit the values of these publish variables only in File B?

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.

I’d like to suggest a small but powerful improvement to the layout guides workflow in Figma: an option to delete all layout guides at once from a frame or page. Currently, users must manually remove guides one by one, which becomes tedious and time consuming especially when working with complex layouts or multiple frames. A single-click option to “Clear All Layout Guides” (similar to how rulers or grids can be toggled) would significantly speed up workflows and improve usability.

Hi Figma community. I would like to know if any of you uses a way to make changelogs automatically that update once there has been a change in the components (in our design system library) and that it can detect the type of change that has been done, the name of the component, date.If you know any plugin that can work for this please let me know!

i know this has been posted before, but Figma really needs to address this issue. pasting an email address should not just format the existing text as a link with the new text as a destination. when creating prototypes with lots of dummy accounts, or even with real data, copying and pasting lots of emails becomes the hardest part of my day, and there are no key shortcuts either. i have to copy, then right click, paste to replace. or “copy as text.” it’s obnoxious, and frankly i don’t think anyone using Figma has ever needed a functional email link for a prototype, it’s not like we’re creating live products where someone might actually click the email link to send an email. please fix this Figma, it’s infuriating and breaks the flow of creating prototypes. When basically every prototype i create for work requires a list of users and their contact information, it becomes a daily problem which destroys efficiency. at the very least, allow us to paste them without formatting using cmd+shif

If you have selected an object such as an artboard or screen (or have selected it by mistake), including many nested text objects - typing “Control-B” BOLDS / UNBOLDS all text in the selected object, including all nested text… While I can see for simple objects this is convenient… It’s a HUGE PROBLEM if you have a large screen or perhaps an Artboard that has a bunch of screens on it… Its very easy when using the keyboard to accidentally select the artboard by mistake, It is very easy to accidentally type CTRL B while copy / pasting objects (intending to press CTRL-V) or using other keyboard shortcuts… The result is that ALL of your text becomes BOLD!! Your entire text on all of your elements on all screens if you select the parent screen by mistake… If you don’t notice this for say 20 minutes and continue working, it is near impossible to fix...This is massively broken as it becomes a huge pain in the ass if you discover that all of your text weights are now incorrect throughout all yo

Hello,Our team is using the new annotations feature for category, and something that would be nice as a feature add is the ability to toggle showing and hiding annotations based on category. This would enable content team members to toggle just content annotations and dev teams to toggle dev and accessibility, etc. maybe somewhere in this panel​​​​Another item of discussion is if Figma allows plugin creators to access annotations. There are a lot of really great plugins out there for annotating automatically. Envinced has a really nice one for example called Design Assistant. This tool will scan the page and then add annotations through their plugin, but as new frames on your page. Some large workflows might have hundreds of screens, so the more and more frames and such added isn’t the most valuable. Having a way for plugin creators to access annotations where their automation would apply them there instead of as frames would be really great. Thanks!-Amber

As far, Figma make can be used in a Figma site page to make code-real sections, elements and interactions, but if it’s applied over a component coming from a design system (in a figma design file or in the figma side file) it overrides any component micro interaction making it hard to use it as a combo.For instance, I have a button CTA with a set of variants for the states: default, hover, focus, selected, loading, disabled. If I use this component in a Figma site (website-test) and click over it > go to Make icon-button and ask to include an interaction “when clicking on it download ‘X’ PDF file the component then loses all micro interactions (e.g., hover state)It seems something quite vanilla but the fact is, Make can help creating micro interactions Figma doesn’t have yet such as “download ‘x’ when clicking, or scroll to ‘x’ section of the page… and if it overrides components micro interactions (change variant to) it doesn’t have any sense for us to use it at all.Would be nice to

No matter how hard I try, when I want to search for an asset, I forget that I have to switch to the asset tab first. I always have to X out of my search and switch back to the asset tab, then search again. It would be helpful to add Assets to the “This page/all pages” filter list.To me it’s confusing that the search icon is in line with both the File and Assets tab when you are on the File tab. This implies I can search both.When you switch to the Assets tab, the search bar is below which implies you only search in assets. 

My eyesight isn’t terrible, I do wear glasses, but the annotations text is too small and makes reading it quite difficult. Perhaps allow for setting the annotations text size in a user’s own seat account?Also, why on earth are annotations hidden behind a paywall? This is crazy. I can’t use them with my clients so I have to use my own annotations library instead which is obviously less convenient. Ta!