Suggest a Feature

I find the thumbnail is slow to update and often doesn’t update for days (at all?). A work around has been to choose “Restore default thumbnail” and then “Set as thumbnail” on the desired frame. The thumbnail has become an important feature to me and I use it to convey information to my team. The inconsistent thumbnail updates are a little problematic. Suggested solution: an option in the right-click menu for the file to “Refresh thumbnail”.

The descriptions written in variables should be shown when selecting/picking them in respective pickers - maybe as tooltip? Otherwise I don’t see, how this could be accessed/taken into account by the users of our library.The grid view of the color picker shows the actual name as tooltip for example. This could also be used to actually show the description. 

Hello Figma Team,My name is Faraz, and I am a UI/UX designer who frequently uses Figma for both design and animation. While I truly enjoy designing and animating in Figma, I often face challenges when developers request animations in GIF or video format with high resolution.Currently, Figma does not provide a direct option to export animations as high-quality GIFs. From a user’s perspective, this creates difficulties and forces us to rely on external tools such as Jitter or LottieFiles, which makes the workflow less efficient.I would like to request that Figma introduce an option to export animations directly as high-resolution GIFs. This feature would make Figma even more powerful and self-sufficient, eliminating the need for external animation tools and significantly improving collaboration between designers and developers.Thank you for considering my feedback.Best regards,Faraz

ProblemSlots are a powerful way to make components flexible, but today they are too open. Even when using Preferred Instances, designers can still insert any component or element into a slot. This flexibility often leads to misuse and breaks design system consistency—especially in large teams.Example:A Button component has an Icon slot.We want designers to use only approved icon components, but currently they can insert:Any other component Any vector or frame Any custom elementThis results in inconsistent UI, broken behavior, and extra review overhead for design system teams.Proposed FeatureAdd an option to restrict slot content to specific components or component sets.When creating or editing a slot, allow authors to:Define a restri

How easy would it be for Figma to have a simple item in the right-click menu (and main menu) for character count or word count? Surely there are plugins like Word Counter, the one that I just tried and it doesn’t work 🤬. And easy enough to do it on the web. But how about I select the paragraph I worked with and see how many words I have? Right there where I am working? Also, if this exists…educate me. 😉

As a file owner working on large-scale design files, managing comments becomes extremely time-consuming. In many cases, there are hundreds of comments across a single file, and resolving them one by one is not practical.Often, during the design phase, some comments are unintentionally left unresolved. Once the project is finalized, there’s a need to quickly clean up the file—but the lack of a “Resolve All” option makes this frustrating and inefficient.It would be incredibly helpful to have a feature that allows file owners to resolve all comments at once. This would save significant time, improve workflow efficiency, and help keep files clean and organized after completion. Would love to see this added 🙏

Hi Figma team,I'm using the Figma remote MCP server (https://mcp.figma.com/mcp) with Kiro (by Amazon). The connection works fine — I can successfully use read-only tools like get_design_context, get_metadata, get_screenshot, etc.However, I noticed that the use_figma tool (write to canvas) is not available when connecting from Kiro. According to the official documentation table at Guide to the Figma MCP server, Kiro's "Write to canvas" column is empty, while VS Code, Cursor, and Claude Code all have it enabled.I confirmed this by connecting the same MCP server from VS Code — use_figma appeared immediately with the full toolset. So the limitation is clearly on the server side based on client identification.Request:Please consider enabling use_figma and search_design_system tools for Kiro, the same way they are enabled for VS Code and Cursor. Kiro already supports Streamable HTTP MCP connections and handles tool approvals properly.Thank you for

It would be very helpful to be able to set all new files to be public/private by default instead of needing to go into every file and change that setting. Does anyone have any work arounds/automations/tips for doing this with a shortcut?

Hello, I’d like to suggest adding a Ukrainian version of Figma. This is mainly for the convenience of users whose English isn’t good enough to read and understand the tool’s names, and relying on translation tools isn’t always practical. Of course, it’s better to memorize the meanings, but that takes a lot of time and often leads to design errors.

Many developers have been asking for access to the file key from the Plugin API for years. The consistent answer is that file keys can't be exposed to public plugins for security reasons, and the only workaround is asking the user to paste the file link — which is frictional, unreliable, and doesn't survive file duplication.The core problemPlugins frequently need to associate per-file state (settings, subscriptions, licenses, local caches, external resource mappings) with the specific file they're running in. The current options all break down:figma.root.setPluginData — stored inside the file's content, so it's copied verbatim when the user duplicates the file. Any custom file ID we generate and store is cloned along with it. figma.clientStorage — scoped to the user's device, so it doesn't persist across collaborators, browsers, or machines. Useless for file-scoped state.

I can’t seem to change text colour inside shapes. I only get the option to change the background. The only way I was able to get it to work was to create a separate text layer change the colour there and then paste it inside the shape text area.

 When creating grids on Figma, it would be useful if one could pick a specific column or row and just drag it across the layout to reorder content.Sometimes the content is too complex to select each individual cell and just move it around with the arrow or dragging. It could be cool to drag the whole column or row to reorder content.I think this is a natural instinct for most people, and not being able to do it when designing is kind of restricting in my opinion. The handle could even be the current “circle” that appears above/aside the table.   

I’d like Figma components to support conditional/dependent properties inside the Properties panel.Current problem:Large design system components often expose many boolean, variant, text, slot, and instance-swap properties at the same time. Some of these properties depend on each other, but today they stay independent.Example:- If `Show Badges = false`, then `Slot Badges` should be hidden or disabled.- If `State = Active`, then `New Message`, `Show Separator`, and `Swap Icon` could automatically switch to predefined values.- If `Badge mode = Match`, then credential badges should be hidden automatically.- If one badge group is enabled, another mutually exclusive badge group should be disabled.Current workaround:We have to create more variants, nested components, or expose multiple booleans manually. This works, but it makes component APIs noisy and allows invalid sta

Copy/pasting prototypes is possible with simple click interactions, as explained here: Create interactions – Figma Learn - Help Center however this does NOT work for conditional interactions with multiple if/then/else statements, which is arguably much more important, as it takes way longer to reproduce/copy over to another component.

I wish I could use text string variables to manage common property names across component variants. Many components in my design system share the same properties (eg, theme: light/dark, state: default/hover/pressed, size: small/default/large), but I have to hand key each of these for each main component. I wish I could have a list of these property names that could be reused between components. Having that would:Reduce the amount of manual entry Eliminate potential for typos Ensure a consistent vocabulary that translates better to tokens/code semantics Increase likelihood of consistent component variable taxonomy 

It would be really useful to have custom CodeSyntaxPlatform values. We’ve just created 100s of variables in code and used Tailwind tokens for the WEB platform, but it obviously it makes no sense when CodeGen is showing CSS (i.e. Web): It’s fine to have some core platforms, but being able to assign syntax for arbitrary platforms make a lot more sense: variable.setVariableCodeSyntax('WEB', `#${hex}`) variable.setVariableCodeSyntax('TAILWIND', `${prop}-${key}`) Ideally, there would be a UI for this, too:

Hello, it would be nice to have the option to insert floating components inside text (like Emojis). Use case would be for signs or infos in complex dashboards. Its a hustle to do this now manually and also set kind of boundingboxes to sync different heighs of text and component. Regards

There are 2 organizational things that I’ve been really wanting since starting to use Figma:Tab Groups: As someone who has a ton of different projects/clients, I would love to have the ability to group my open Figma files into tab groups. It would be amazing to be able to have a bunch of my projects open without overwhelming crowding in the tab bar. This could be similar to browser tab groups. Page Groups: Creating design systems is complex and super layered!! It would be extremely helpful to be able to group pages within a file or be able to establish parent and child pages.I know this is not the first time these things have been requested, but I’m hoping they could be added as a quality of life update in the near future!

When creating tokens and working with variables Dev Mode generates code where the group name is included as part of the token name. Currently this doesn’t make too much sense (for me at least) and in Figmas own variables tutorial it would result in spacing tokens being called “SpacingSpacing-sm” if you would look at the tokens in Dev Mode. Can we please get an option to exclude the group names from the generated code? The groups as I seem them are for organising and not necessarily something we want to automatically include in the token name. Semantics are important for tokens so if I have to leave out part of the name and only have it as part of a group name it makes reading the token and using it correctly in Figma so much harder. Definitely interested in hearing others experience regarding this! Maybe i missed something or should rethink our structure.

I’m having trouble exporting PDFs of frames. Do you know if the export functionality embeds the fonts? I will import the generated pdf frame into another work that requires to be PDF/A compliant, so I need the font embedded in the frame in the first place. I tried with Adobe Reader, and it does not say “embedded”, which is usually a sign that it’s not. I tried with another software (Okular), and it does say “fully embedded”.

This has been mentioned here: Hide layer using variables - #5 by Andreas_Braendhaugen1 Invert boolean variable for layer display - #14 by Desislava_Slavkova Inverted Boolean Property - #2 by drewcovi_usb but those topics are all closed. I am looking for the availability to HIDE a layer when a Boolean variable is TRUE and SHOW it when it is FALSE. So, the inverse of the default/current behavior. I want to do this without using components. Use case: When a variable is true, show one frame. When that same variable is false, show a different frame. I can get basically this by using two different variables:

It would be useful to have a tree menu, similar to the layers panel, to organize pages into subcategories. On structured projects, having all pages listed flat makes it nearly impossible to understand which areas to work on, and you waste too much time scrolling through them. A menu that mirrors the layers structure for pages would be a much better solution.

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.

As an Admin i want to be able to choose in a Workspace Level, which Workspace is allowed to use the Open Session Feature in FigJam. Currently there is either “on” or “off” for the whole tenant, which we cannot use due to security topics.This should be included like also to select for AI feature, or public link sharing.

Nowadays iPads have M4 and M5 processors completely capable of running something like FigmaI think for many people on the go and for many designers it would be great if the Figma app on Mobile, at least the iPad app would work as the desktop app on Mac.I’ve even found myself using the web version with Magic Keyboard because it’s what I have on a trip or so and sometimes the inspiration and ideation must flow