Suggest a Feature

I guess it’s a tiny thing but it will be super helpful to have an option with each element to remove it from final exports. Like sometimes I have some elements which I don’t want to be in the final export when I am batch exporting multiple frames. For me, I faced this issue when I wanted the gridlines/safe-areas not to be visible in the final export. (I’m talking about the manual grid lines, not the layout grid row/column option from Figma) Maybe there is a way of doing that that I haven’t come across yet and as a learner, I would greatly appreciate it if anyone could enlighten me.

Hi all,Have you considered adding a feature to the auto layout “gap” feature that could allow a user to set a minimum gap i.e. 8px and a maximum gap i.e. 40px?I’ve recently needed this function for building bar graphs. I need to make them responsive without getting too small and overlapping on each other or too big when expanded.

With the new update, we have a great new feature, but unfortunately, it’s not usable with our component structure. Exposing all props of a nested instance also exposes props that we don’t want in the context of the consuming component. What if we could also select which properties to expose? This would lead to a cleaner sidebar with only valid props.

Simple as the title : Allow components to be set as file thumbnails. We need that possibility in our company to be more flexible with our thumbnails, wich may change year by year.

To the Figma Team and the broader Community,I am writing with an urgent and passionate plea: please make Code Connect a part of the Professional plan. To gatekeep this incredibly powerful feature feels like a direct rejection of the modern, agile way so many of us build products today.The world is moving towards small, high-impact teams, single-person companies supercharged by AI, and freelancers who handle both design and development. We, the users on your Professional plan, are at the heart of this movement. We live and breathe the transition from pixel to production code.Why are you creating this artificial wall between our designs and our code? Code Connect isn't just a convenience for large organizations; it's a revolutionary workflow enhancement for the exact type of user on the Professional plan. It promises to eliminate the friction that we face every single day. To lock it behind a higher paywall is to create an unnecessary and painful

Hi Figma team,We’re running into a structural challenge in our workspace that’s slowing down collaboration within our creative team. As our organisation grows, so does the number of projects we manage in Figma. Each project gets its own folder, but because folders can’t be nested or organised into deeper layers, everything ends up sitting in one giant list.This creates a messy, hard-to-navigate workspace — especially when multiple teams and long-running projects are involved. We often work across different clients, internal initiatives, and design streams, and the lack of subfolders makes it difficult to keep things structured and find what we need quickly.Our request:A more advanced folder system that supports multiple levels (e.g., Workspace → Client → Project → Deliverables). This would allow us to group related projects, separate clients, distinguish internal vs. external work, and keep our workspace clean as it scales.W

Hi, We are working on a pixelart project and figured out it would actually speedup our workflow A LOT if it was possible to disable Anti-Aliasing everywhere for viewing, editing and exporting. Having the option to disable it per object could also be interesting. Is this something you guys could add? Thank you very much.

Our team uses Quasar Framework with Vue.js for all front-end development. Currently, Figma Make generates React-based code.It would be extremely helpful if Figma Make could generate code directly using Quasar + Vue.js, or at least provide an option to switch the output framework.

There are not enough typographic controls in Figma Slides, mainly - paragraph spacing. Example: when creating bullet points they are really squashed and there is no easy way to adjust the spacing between them without going to Figma and bringing it back to Slides. 

The help button blocks the prototype content, and it is suggested that the help button can be hidden or moved。

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.

OAuth App does not have permission management functionality, so permission management functionality needs to be added, such as adding editors and readers-only.

An edge case however I’d love to see this update eventually. I have a segmented button component that contains nested button component variants. This segmented button component lives in many different places in my UI, utilising the different forms of the nest button component (text , icon, icon and text) I’d like to be able to set a min width to the nested button components inside my segmented button component instance WITHOUT having to set the min width to the master button component.

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. 

Hi everyone,I’m running into a strange shortcut behavior difference between my work and personal Figma accounts. Platform: macOS (Turkish-Q keyboard) App: Figma Desktop + Web (tested both) Mode: Design mode, Move tool active, not in Prototype etc. Issue: In my personal account, pressing ⌥ + ⌘ + ↑/↓ rotates the selected object. In my work account, on the exact same device and setup, the same shortcut correctly changes the layer order.  What I’ve tried (none fixed it): Cleared Figma cache (~/Library/Application Support/Figma) Removed and re-added both accounts The behavior persists only in my personal account,

I’ve been asked a couple of times if the font size can be made bigger by colleagues within the feedback panel because they can’t see it. We might be a bit older than most using this software but it would still be a helpful setting to include.

Thanks for adding annotations to Design Mode. I have been spending the last day annotating some new design ideas. People who have access to the Figma file love that they can read come design rationale and interaction behaviors. For others, who do not have access, or do not use Figma it would be great if I can export the annotations associated with objects inside a frame.  Thanks, K.

I wanted to share an idea that’s been on my mind: I think Figma could benefit from a dedicated design staging environment. Developers have staging to validate functionality before production, but designers don’t really have an equivalent space to validate design behavior at a higher fidelity. A staging-like environment in Figma would let designers build and test more realistic flows, interactions, and states — something deeper than prototypes but lighter than full development. It could help teams surface UX issues earlier, experiment safely, and hand off work with more clarity. I also think it would make it much easier for developers to understand the design. Right now, presenting prototypes in Figma can get messy, especially on bigger projects. For example:– Sometimes the Figma UI can get in the way when sharing previews.– Prototype links end up long and awkward to share.– You usually need separate URLs for desktop, mo

Bringing this up for visibility. I have a page for “components” and a page for layouts in my design file. These components have many states, so I try to keep things organized by separating project specific variations of key pieces in their own page away from the prototype mockups.  I have a tooltip in these components - on hover it displays another component as an overlay. This works great in the component page - but use that component elsewhere in the file and the overlay doesn’t carry over. I can add the overlay, but have to connect each instance of the tooltip (it’s a quoter, so there’s lots of possible variations) on every variation of my component - which defeats the purpose. It looks like this is something others have asked for: 

We want to use it to link design variables to the design tokens in our application. Our company runs on a Professional plan. There are only 10 users that need access, so we don’t have any need to go to an Organization or Enterprise. I saw the same question here, but it wasn’t answered and just pointed to the Plugin API which has an entirely different use case.

Auto layout is cool. Thanks Figma! However, to change the display order, one has to manually change the order of each item in the Layer section, which can be annoying when dealing with too many items in the layout. A solution would be to add three layout buttons, right below the current ones, that do just that: reverse the order of display. Much love. I hope this helps! Names of the button and much more

Hi,I often need the super useful new “Translate to...” AI feature, it’s great, thank you!One way to make it even greater would be to save which language was used last and use it as the default selection. Now I always have to type “ger” to get “Germany” and press enter, bc “Arabic” is the default since it starts with “a”. Just like the cmd+P menu has a “Recents” with the last action on top, I would propose to introduce this for the language selection of the “Translate to...” tool :) Thanks for the consideration,Mikka

{Commenting as Guests} Clients wanting to give access to prototypes to temporary teams without the need to create accounts as guests only, allowing comments and feedback within Figma prototypes. Possibly allowing these users to make comments on prototypes as Guests with temporary names.

We have a design system set up with tokens (variables) to enable all components to switch between light and dark mode. For developers/viewers to see what a screen should look like in Dark mode, we have to duplicate that screen. But as an editor I can set the colour mode variable at the Page level to Dark and all screens on the canvas/page turn to dark mode. If developers/viewers could also do this, I could delete the dark mode duplicates of every screen and only have one copy of each screen, defaulted to light mode, and then just toggle dark mode as needed. This would be much more efficient on memory usage and maintenance.