Suggest a Feature

I find managing template colors really difficult in Slides. I can’t easily organize, re-order, or rename them. I’ve found some ways to hack it but it feels really convoluted trying to provide color options in the templates I’m making. I think Slides is doing a really great job on most fronts and I love the product, but I find myself just using colors from other libraries because managing them within Slides is so confusing.

Figma can you please add the Font Miranda Sans. Its on Google Fonts. Thank you. 

Hi! Many keyboard shortcuts do not work when the Russian keyboard layout is active. To use them, I have to switch to the English layout first.This interrupts the workflow, especially when working with Russian text and frequently switching between typing and design tools.Please make keyboard shortcuts work consistently regardless of the active keyboard layout.

Annotation orientation control (vertical placement)When laying out flows horizontally, annotations from one screen's frame overlap the adjacent screen because they render to the left/right. Request: allow annotations to render above/below the parent frame instead, with the same anchor logic rotated 90°. Ideally a per-frame setting with a global default.

Currently you can set things like, 5.99 or 4.32 but you can’t show 5.00 by default. This looks weird when you start adding amounts like #amount + 0.5 which will then look like $5, $5.50, $6, $6.50. It would be nice if instead it showed as $5.00, $5.50, $6.00, $6.50

The current Tables feature in Figma feels quite limited. It would be fantastic if some basic functionalities could be introduced soon, such as: • The ability to easily resize cells without needing to adjust font size • The option to merge cells • Top, middle, and bottom text alignment options These enhancements would bring Figma’s table functionality more in line with what we already have in tools like Keynote and Google Slides.

In other design tools you can simply press a key, and any selection outlines, grab handles, etc. get hidden while the key is down, so you can preview and evaluate how things look, without having to de-select everything and lose your selection. Apparently there is no way to do this in Figma =( This is important while experimenting with different colors, fonts, etc., and in Figma it could be used to see how different sizes, variants, and states, look in your design, without those selection handles and outlines getting in the way of you previewing things.

As a non-admin user there doesn’t appear to be a way to see a list of the plugins that are approved for use by the organization. Currently only admins can see a list of approved plugins in Resources tab in the Admin Settings. Non-admins can only see a list of installed plugins. This list is accessible through the menu option Plugins > Manage Plugins… Would others derive value from a list of approved plugins?

I’d like to be able to choose a thumbnail (either a frame from the video, or upload a thumbnail) for an object that has Video fill. Currently Figma uses the first frame of the video as the thumbnail, and if that video starts all black, then the thumbnail is just black. It will show fine in prototype view or mirror once the video starts playing, but when you are editing it would be helpful to see a frame of the actual video so you can adjust properties of elements (e.g. colors, opacities, gradients) and see what they’ll look like composited with video.

Hello Figma Team,I really enjoy using Figma and I use it every day.I would love to see the Android app support the full Design Editor, not only viewing, commenting and prototypes.Many designers work directly from phones and tablets, especially when they are away from their computers. Having access to tools like Text, Shapes, Fill, Layers, Typography, Effects and Export in the Android app would make Figma much more powerful and useful.Please consider bringing the full editing experience to Android devices.I believe many Android users would benefit from a complete mobile editing experience.Thank you for your great work!

Unified Variable Mode Switching Across LibrariesWhen multiple published libraries contain variable collections with identical collection names and identical mode names (for example: collection “Theme”, modes “Light” and “Dark”), Figma currently shows a separate mode switch for each library.It would be much more efficient if Figma detected matching collection and mode names and presented a single switch to the user. Changing the mode would automatically update all matching libraries at once.This would greatly simplify multi-library design system setups where core tokens, and product-specific tokens are split into separate libraries (and different design teams) but share the same theming structure.

Part of the value of utilising the Figma MCP for skills that generate slide decks is consistency, but what would help a lot with ensuring consistent output is being able to use existing slide templates within the MCP to generate new decks.Is there any plan to add this capability to the Figma MCP?

To reduce component weight, my design system team has been exploring using variable modes to toggle between different “variants” of a component, rather than just using variants. The benefit of this is that for these “style” specific properties, where just styles are changed like fill and stroke, using modes significantly reduces the weight of a component in the system. In this example I use a Badge component, and variables to change between the colors of the badge.However, my component code still has a “color” prop. Because I don’t have a color prop on my Figma component, but rather a “BadgeColor” mode that controls this property, is there a way in which CodeConnect can still map this to the correct code property? Currently it doesn’t seem like CodeConnect can read anything that is not a property. Realistically all I need is the CodeConnect to be able to read the string value of the mode, and map that to the actual code prop.

I was writing an interaction annotation for a screen that has the same pop ups as other screen so wanted to tell our devs that they can see the pop ups in this other section and redirect them back and forward to the pop ups.

I got the issue that I could not extend the column span of a layer if it stands at the end of row in Grid.I understand that a layer’s colspan cannot exceed the maximum number of cols, but it should have been automatically wrapped to the next line when the colspan number is still valid.Can you help to investigate this? I have found a workaround (at the end of each video), but it is time-consuming.

When exporting variant names, the file name becomes a combination of all the variant properties. There is no way to control the variant export name, which is especially difficult for developer hand-off. In this example, I have a back icon variant group (Named “Back”) containing both an Apple and an Android variant of the back icon. If I then go to export the Apple variant as an SVG, The variant export name then defaults to “OS Type=Apple.svg” It would be even worse if I had multiple properties. For example, having two more properties could result in a variant name export as “OS Type=Apple, Direction=Left, Style=Line.svg” This is a very poor naming convention, especially for icons. What I would like to have is the ability to control the name given to each variant export. In the above example, I would like the Apple icon to export as the name “back.ios.svg” and the Android icon to export as “back.android.svg”. This way, our developers can export assets as needed directly from Figma wi

Hello!I was going through our team files today, and organizing some that we shared with other vendors. I realized for one of the projects, we needed a ‘draft’ page for our team to ideate and brainstorm there, but didn’t want the vendor to actually see the WIP.I was wondering why isn’t there a page-level permission for viewers? This way I can hide / lock the ‘playground’ or draft page within a file from non-designers!

In design mode the layers sidebar just shows all information and allows for fluid horizontal and vertical scrolling.In dev mode, it all of a sudden just cuts off everything above a certain width.

Hi there! I would like to know what Figma is going to do to comply with the US sanctions against russia regarding design software coming into effect in September. I haven’t seen any new updates on the topic. It seems like the old approach described here will be in violation of the new sanctions. For example, Notion has already communicated here that to comply with the US sanctions they will restrict access to their platform for all users in russia. Please vote for this topic to draw Figma’s attention to this serious matter.

Hello Figma Team,First of all, thank you for building Motion. It has made it much easier for designers to create engaging animations directly inside Figma.One feature that would significantly improve Motion is a built-in Typewriter (Auto Typing) text animation.Currently, designers who want text to appear letter by letter have to create complicated workarounds by splitting text into individual layers or manually animating masks and keyframes. This becomes especially time-consuming for longer paragraphs or multiple text elements.I propose adding a native Typewriter animation with customizable controls such as:Character-by-character typing Word-by-word typing Adjustable typing speed Start delay Blinking cursor (optional) Cursor styles (line, block, underline) Delete/backspace animation Pause after completing a sentence Support for multiline paragraphs Compatibility with existing Motion keyframes and easingThis feature would greatly benefit designers creating:Product launch videos Social m

I often have a need to annotate designs from different perspectives, like..Accessibility Analytics tracking Localization...and the stakeholders have a need to easily find and check the annotations related to their responsibilities.Currently in Figma I can create color-coded categories for annotations and use them to tag layouts, which is great. I can even filter them to some extent.What makes the filtering almost unusable for me is that only ‘All categories’ or a single category can be chosen. ‘All categories’ is too much: layouts will get flooded with annotations. Unfortunately just selecting one (like ‘Tracking’ in the image below) Figma still shows all the rest as these reduced mode red things (see lower image). What I’m getting at is that there should be a way to easily toggle any combination of categories visible/hidden. It’s weird that in the Filter by -list you can’t choose to display say “Accessibility” and “Interaction” and the rest would be hidden. Showing all those reduced m

Today: As an agency, we’re frequently starting new projects for new clients. We’ve evolved a set of best practices for Figma file organization, per-client design systems, etc. These best practices have been captured in a Starter Project project in Figma. However, to use this Starter Project each designer must duplicate each file in the Starter Project individually and then move them over into a new project. Idea: We’d love to see Figma support duplicating projects in addition to the existing file duplication functionality. This would be a small but noticeable improvement in efficiency for spinning up new client projects.

Dear Figma TeamThanks for all the efforts and products you are producing for the wolrd it is really inspiring us all. Since Figma products have a lot of features and it is hard for anyone to know about all of them, I suggest to build an AI tool where I ask it on how to use a feature and it will produce a video with voice on how to use this feature and it can suggest more videos on youtube if I need more explanation or deep dive.

Is it possible to view a user’s drafts as an Enterprise admin or a Team admin?As an admin I really should be able to view all files that have been created, but it seems that user’s drafts are still private even after the update.

In their current state, comments try to accommodate multiple use cases into a single system: general note-taking, questions to ask stakeholders, functionality/purpose annotations, feedback, prototype tour points, etc. When all these use cases pile up in a single page, it could easily start to reach over 100 individual comments and makes it difficult to distinguish between them. I’m proposing expanding the functionality of the comments feature to allow for the most common use cases to be different comment types. Invision does a great job of this by changing the color of the pin when a certain comment type is selected. This allows users to quickly identify the most relevant comments to them and ignore the rest. (From Invision) What would make it even better is if the visibility of types of comments could be filterable from the right toolbar. When the comment tool is active, editors could filter down which types of comments they would like to see. They could also determine if a comment t