Suggest a Feature

Variables is powerful, “Without needing the designer to fill variables manually”Can a Figma bring it in a new way: We design 3–4 screens AI detects: Color patterns Spacing scale Typography hierarchy Then auto-generates: Tokens Components Variants This is realistic because it’s pattern recognition by AI  

Same as in Slack or Outlook, would like to not trouble my commentees at odd hours and just send the comments I make outside of hours , inside office hours!

With the interactive components, a variant can now have a tooltip. But unfortunately hover and clickactions are still mutual exclusive. I’m designing for a desktop application and having a tooltip per inputelement/button is crucial.

With the increasing popularity of iPads among creative professionals and the device's capabilities now rivaling many laptops — especially with Apple Pencil support and desktop-class processors — it’s surprising that a leading design platform like Figma hasn't released a fully functional iPad app. Is this a matter of strategic prioritization, where Figma believes the current user base doesn’t demand it strongly enough to justify development resources? Or is it due to technical limitations, perhaps stemming from the complexities of maintaining feature parity with the desktop/web version on iPadOS? Alternatively, is Figma's vision more aligned with a cloud-first, desktop-class browser experience, where portability across devices takes a backseat to collaborative infrastructure? If so, does this approach overlook the rising trend of mobile-first or tablet-based design workflows? It would be insightful to understand if Figma simply hasn't seen enough ROI or user behavior validation to green

I’m trying to build an iOS app in Make to use very specific features and behaviors that Swift has, one of them being Dynamic Type. Is there a way for me to tell Make to use Swift instead of tailwind and react?

TL;DR: Today, only Variant properties can be set directly by prototype interactions. For Boolean, Text, and Instance Swap, the only path is to bind the property to a global variable and use Set variable from outside. This means component behavior cannot be encapsulated inside the component itself — which has become a structural blocker now that Figma is positioning its files as the source of truth for AI-generated code and apps. The proposalExtend the `Change to` action (or add a new Set property action) so that any component property — Boolean, Text, Instance Swap — can be set directly by a prototype interaction defined inside the component itself. Same mental model as Variant, applied to all property types. The interaction would travel with the component, and each instance would maintain its own independent state. The strategic misalignmentThere is a growing gap between Figma's product direction and what its component model can actually express.On the output side, Config 2025 doubled

Hi Figma team 👋This is a feature request for a Radial Layout system, distinct from Radial repeat.Instead of repeating a single object, this would allow arranging multiple distinct elements along an arc or full circle with: configurable angle range (e.g. 90°, 180°, 360°) controlled spacing/distribution along the curve automatic tangential alignment of each item The goal is to support structured radial compositions, similar to Auto Layout but for circular structures, useful for: UI card stacks / carousels radial menus motion design layouts circular visualizations This would make radial UI patterns much faster and more consistent to build natively.

Hello Figma Team,I would like to request a feature where clicking a layer/frame in the left sidebar automatically centers or zooms the canvas to that selected object.This would be very helpful for large projects with many layers and frames, making navigation much faster and more efficient.Currently, users need to manually use shortcuts like Shift + 2 after selecting a layer.Suggested option: Add a preference setting: "Auto focus canvas when selecting layer" Thank you.

Exactly what the title says. Figma already has a powerful API. Figma Sites is a great starting point but is missing a lot of functionality. Something missing in the new CMS is the ability to add data to the CMS using a REST API.Can the Figma team have a look at this? I think it would increase the value of the product. Best regards,R.

Id love to have scroll position as a variable so that i can make paralax effects and prototype interactions based on how far i have scrolled down a page. I know the new site feature offers paralaxing but why not include it in figma design so that i can show my prototypes fully functional.

I'd like to suggest a feature that allows users to select all objects connected by arrows or connectors in FigJam.Use case: When working with diagrams or flowcharts, it's often useful to select a group of connected nodes—for example, to move, style, or reorganize a specific flow within a larger diagram.Suggested behavior:Right-click a connector or node → "Select connected objects" Or: select a node, then use a shortcut/menu option to expand the selection along its connectionsThis would be especially helpful for large FigJam boards where manually selecting linked objects is time-consuming.Would love to hear if others have found workarounds, or if this is already on the roadmap!

Hey everyone,As a product designer working with a pretty large internal design system, I kept hitting the same limitation in Figma Variables: they’re great for static values, but the moment you want a scalable system (spacing scale, type scale, radii, opacity variants, responsive values…), you end up maintaining a ton of derived variables manually… or in spreadsheets.Variables Plus — a plugin that lets you define relationships between variables using formulas, so derived values stay in sync automatically when the base variable changes.Examples: space_2 = space_1 * 2, space_3 = space_1 * 3 h1 = base_font * 2.25, h2 = base_font * 1.75 col_w = (container_w - (gutter * (cols - 1))) / cols (e.g. container_w=1200, gutter=24, cols=12) “Copy values across modes” to keep modes consistent (instead of duplicating & updating by hand) If you want to try it, the fastest way is to duplicate the demo file: Plugin: https://www.figma.com/community/plugin/1607106236822235286/variables-plus De

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”.

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.