Suggest a Feature

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

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 your consideration!

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. User-pasted URL — adds friction, has to be re-requested after duplication (but we can't detect the duplication, so

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.

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: Thanks.

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.

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

So I have this document that we use for one-pagers in my company. It exists in portrait, but I’m taking an existing one and making it landscape. When I take the original page and rotate it 90 degrees, the grids disappear. So far I’ve tried removing the grids and resetting them up shutting down Figma and restarting closing all tabs and reopening needed tabs switching on/off grid view I’ve turned the colour of the grid opacity to 100% All result in Nothing Any help would be great

Can we add image mirror/flip option, specially in components.  

It would be really great to be able to have more flexible way to manage colors than just hex. for example when i create a hover color in my css i use “color-mix” which takes the base color and applies a white transparency into it.  i figure a way to do that using color styles by applying two layers together the base color and a color transparency on top, but i cannot do that in variables, it just forces me into a single hex/rgb color.I even tried to point to a color style from within the variables but couldn’t. In this day of css we need more flexibility than just hex and px. If you don’t evolve you’ll go the way of Axure, just saying. 

Current: Site > Settings > General > Custom codeAdd section: Site > Settings > General > Non-page requests So I could addPairs of request and static content: robots.txt (and add static text content) some-verification-file-name.txt (and add static text content) sitemap.xml (and add static/dynamic content) Redirects request (and redirect url) This should cover a wide range or common scenarios. 

We’re using templates as an early way to handle branching in Figma Make. There’s a primary prototype that the team remixes and iterates from. As work progresses, we manually pull changes back together, and when a remix becomes the new source of truth, we promote it to the primary prototype and archive the old one.This process is very manual and hard to stay on top of. Having real branching and merging for Figma Make files, similar to what exists for design files, would be a game changer. Hoping something like this is on the radar and shipping soon. 🤞

Comments are not preserved when duplicating a page, frame, or section, which creates friction in revision workflows.Our team collects client feedback in comments, duplicates designs to begin revisions, and then loses the original comment threads. This forces us to manually recreate feedback or constantly reference an older version, which slows iteration, increases the risk of missed feedback, and adds overhead across projects.A helpful solution would be the ability to preserve comments on duplication, anchor comments to objects instead of canvas positions, or show comments from a previous iteration.This is a significant pain point for an organization of over 6,000 employees, where even small gaps in functionality can have a wide-reaching impact. PLEASE HELP!

Am curious if there’s an easy way to exclude the second fallback parameter from any css custom properties displayed within the dev inspector? Our dev team will not utilize the fallback values, and is hoping to sync these variables 1:1 with the css custom properties defined within the codebase. We’re aware we can manually edit the variable and exclude the second parameter, but would love if there were a way to make this the default behavior.i.e. we would prefer color: var(--primary-100) over color: var(--primary-100, #f3f3f3) as a default if possible.

I work for 4 different companies with unique Figma accounts. All the projects I am currently working on are open, which is about 20 tabs. Switching between profiles for these different companies makes my workflow SO slow. Is there a way Figma would consider adding the ability to switch profiles in the open file so I don't have to close everything and start fresh, losing time and often forgetting what I was doing in the first place?  Thank you! 

Hey! How can I transfer the AI generated Prototype in Figma Make to Figma Design and continue editing it manually there?

I'm building a responsive alert banner and trying to achieve a behavior similar to fit-content in CSS. Here's what I need: The banner container stretches to 100% width, Inside, there's a button and a text label, The text should stay on one line and hug its content until it reaches the limit of the container, Once it can't fit anymore, it should wrap onto multiple lines (essentially behave like fill). Think of it as:"hug content until there's no space left → then behave like fill".This should happen dynamically, depending on the container width,so no fixed max width.Is there any way to simulate this behavior in Figma, maybe with some clever auto layout nesting or constraints?Trying to avoid duplicating the component with two variants (hug and fill).Thanks in advance for any ideas or workarounds!

When copying vector-text content from FigJam into Figma Slides, the pasted elements cannot be scaled properly, which breaks layout, readability, and the overall structure :(This creates friction in the workflow between ideation and presentation, I had to recreate a lot of content manually instead of reusing it. Unexpected I have to say.Enabling proportional scaling for grouped vector (strokes!) and text elements would make it much easier to move seamlessly between tools and maintain consistency across collaborative work. Thanks in advance :)