Suggest a Feature

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!

Hello everyone! I think having a shortcut to open/close the local variables would be very helpful. For example in cases where I’m prototyping and need to access the local variables to ensure the accuracy of the variable names or values that I’m assigning in the interactions. Currently, if I want to do this, I have to switch between the prototype panel to the design panel in order to open the local variables, check them and then go back to prototype. Note: I am aware that it is possible to keep the local variables window open, but this often leads to numerous bugs in the prototype. For example, when it is open, I am unable to drag the prototype interactions to reorder them.

It looks like there’s only one input field in the settings to set the language, and there isn’t a button to add multilingual variants. What should I do to create a variant in another language? Or can I handle it another way by directing to different URLs? For example, I want users with their system language set to English to open mydomain.com, and Spanish-speaking users to open mydomain.com/es.

Hello 👋 First, I’m happy about the opportunity where I can make an impact on this amazing product. My idea is pretty simple but can make a huge difference in the way we share files with stakeholders and colleagues. I suggest adding the ability to give different access (viewer/editor) for pages within a Figma file. Because in most cases, we’re trying to include a whole project, feature, or function, whether small or big, in one Figma file - it becomes a real pain-point if the lowest level of grant permissions it’s the file itself instead of the pages within the file. I’m sure a lot in this community can agree with me that many times you gave people access - it was relevant to certain areas of the file, and less to other areas. I want to give content writers access to a specific page where they can edit and review content. I want to give developers access to a specific page where they can play

Text weight should be allowed as a component property. Not as overrides or manual variants but simple text weight or size switch. I want to stop creating multiple duplicate variants within a component just for a font size change or a font weight change. I don’t think there’s any feature like this yet unless I am missing something.

Whether you search from the left side bar or press Shift + I, the thumbnails are too tiny to display details. Some of the assets would look similar from afar but if we’re able to resize the thumbnails as well as the window, it would reduce time dragging the wrong component.

Hey there.As you know, we can already apply multiple fill color or apply multiple variable color to a single frame. But we can only apply one “style” to a single frame. The problem comes when you want to give a single frame multiple effect. assume I have a focus ring, and a subtle shadow. my elements might sometimes have shadows, and sometimes have a focus ring, and in some cases, they might have both. for now, if I want to create styles, I need to make 3:focus-ring-neutralshadow-smfocus-ring-shadow-neutralI understand that the logic behind the style was to make layers of attributes (styles) all saved as one name. but in cases you want to mix a few things, you have to save all combinations that you might use. is it possible that to be able to add multiple effect style to a single frame instead of creating more customized styles? Image below shows how “Fill” has a plus button and can have multiple values (Varia

There should be a way for Figma Admins and Workspace Admins (and potentially Team Owners) to be able to communicate Figma-specific news and information to members of specific projects/connected projects, teams, workspaces, or the entire organization (and groups, if they are ever added)Currently, organizations have to use email, slack, Microsoft Teams, or other tools to communicate about Figma topics, and these messages are easily overlooked since they are outside of a Figma context.It would be helpful to have a way to message discrete groups from within Figma. Examples of things that need to be communicated:We made a major design system upgrade New sticker sheets/templates are available We have deprecated holiday colors. Please remove any hard-coded holiday colors in your active designs. We have a new Workspace for xyz New reference designs are available in your Connected Project. Please check the comms portal for more ab

I'd like to be able to select a component and see all instances of use in the file. Sometimes my files get so large that I lose place of where I am using certain comps, or I am jumping into someone else’s file and it can be super confusing, if I don’t know where they are using that component. 

I’ve had multiple dev’s ask me where to find the core token to a second-order token value for a color when referencing mocks that use our design system. They are unable to see you can hover over to the more icon, and the only “actionable” thing they appear to be able to do is “copy” the variable name to their clipboard. Just asking to leave the “more icon” visible by default, there’s no real reason to hide it. 

it’s different from just using history. we are working on a file that was ongoing for years, some of the frames are old, some are new. we want to see what is the age of each screen to understand the timeline of our work. we could scroll back in time and see, but then we would had to jump between times, trying to discover and guess when a screen was created, rather then the possibility of just clicking on it and see the date of the creation

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.

It would be nice if there was a way to set the default layout guides when you push + between two slides. Now it’s always set to one column and one row.

Hi! First, thanks to the Figma team for all the hard work. Now, let’s talk about Figma Slides Templates. To edit the template styles, I have to select a slide first — which feels a bit unintuitive. In Figma, when you click on the canvas without selecting anything, you can access the file’s styles. Can we bring that same concept into Slides?When I open the template selector, I can edit the styles there through a dropdown. Is that really the best or only way to manage styles in Figma Slides? I don’t think so.Colors & Text Styles: I can delete them, but only through a pretty complex interaction — right-click?Layout Grid: How can I set a default grid? Right now, I have to manually add my custom grid to every new slide I create. If we can't set a default, the feature kind of loses its purpose. :( 

Hi,When designing screens for our platform we use 2 design systems within one frame and even within the same component. We have:Our own design system with light and dark theming Either Material Design or IOS 26 with light and dark themingCurrently it is, to my knowledge, not possible to use these two efficiently in tandem. For example:I can switch both to dark mode but then variables used from one design system used in components of the other design system will not change. To illustrate this: I use the tab bar from the IOS 26 library but override the text labels with variables from our own design system. Now, when I switch to dark mode these overwritten values will not change.Is there a solution that I am not aware of to tackle this issue? If not, perhaps a universal switch that works across libraries would be an idea?

Please include REM as a mode of measurement as it is becoming more and more used by developers. Having to manually convert the measurement is so tedious.

Video settings have a dedicated button when not in Design Mode. When in Design Mode this button is nowhere to be found. So if I want to adjust the settings of a video I must get out of Design Mode first. Is that intended? Not Design Mode Design Mode        

Two related topics for working in Figma Slides:Is it possible to set a default animation for a slide deck? I’d prefer fade in over any sliding, and would like this to be set when I add an animation for any object If not possible, is there an easy way to set/configure multiple animations? The only way I’ve been able to do this is to select multiple items in the design tree (where items can be hard to find sometimes), rather than just selecting multiple animation objects in that bar (using e.g. the shift key).Otherwise I’m really enjoying using this great tool!

Take your images to the next level with an Image Upscaler. This smart tool enlarges your photos while keeping them sharp, clear, and full of detail. Unlike basic resizing, it intelligently enhances textures, edges, and overall quality, turning ordinary images into high-resolution masterpieces.Perfect for:• Enhancing low-quality or old photos• Preparing images for printing or large displays• Boosting social media and marketing visuals• Professional projects that demand clarityUpscale your images effortlessly — bigger, sharper, and more stunning than ever.

Does anyone know how to turn off Figma’s auto-formatting? I’m trying to type '- ', but it looks like Figma is assuming this text must be a bulleted list. I’m having a similar issue when using text that’s in the format of an email address or a url. Figma is changing these to unwanted links. I’d like to turn off all text auto-formatting.

It would be great if we could select different device frames for each flow. This would give huge benefits to those who design responsive websites side by side.

I’d like to suggest the ability to expose fill properties—specifically image and color fills—as editable component properties in Figma. Use Case: In designing components like cards, avatars, or thumbnails, it’s common to have a placeholder image or color that needs to be customized per instance. Currently, to change the fill, I have to drill down into the component’s layers and manually adjust the fill, which is time-consuming and prone to errors.  Proposed Solution: Allow fills (both image and color) to be exposed as component properties, similar to how text and instance swaps are handled. This would enable users to change fills directly from the right-hand properties panel when selecting a component instance, streamlining the workflow and improving efficiency. Benefits:  Simplifies the process of customizing components with different images

The wrap function for auto layout has been a great addition but I keep hitting a wall when trying to illustrate expectations of alignment/stretch of wrapped items as the width of container/screen/viewport changes.An example is with cards containing content of different length. Expectation: card containers should stretch to fill vertical gaps in grid so they all share the height of element with most content (as it works with CSS grid or the align-items: stretch of Flexbox)Current behaviour: I am limited to choosing between fixed-height or hug contents for the cards. Result: card heights cannot dynamically adapt and I am have to write extensive documentation for devs and cannot freely create prototypes using dynamic content.Am I missing something?  

Would be nice to have the ability to insert a UI component that sticks to the end of multi-line text similar to how the ::after function works in html. usage for this in my field is a “caret” (>) or external link symbol following link text. would be helpful for “buttons” as well.

While the most common use for MCP is probably building code prototypes, our team is also using it to create documentation via Claude Cowork. The heavy lifting is done via annotation, and while annotations are great for describing what elements in the frame do, they’re kind of sloppy for declaring what tapping them does. If we had prototype interaction support in MCP then LLMs could derive flow which would eliminate needing to annotate buttons with things like “goes to ‘view name’ “.