Suggest a Feature

It would be great if a section within a section only showed the compact label (where the label displays inside the section) only if there isn’t enough space outside the section. Currently if any section is put inside another section, the inner section will always display the label within the section (compact). This is fine if there isn’t enough space outside the section to display the label, but if there is enough space then it should display the label normally on top of the section. For the way I organize files this would improve readability since I add extra space around sections anyway.

Still have no idea how to submit a bug lol.

Add the ability to Hide sections on Figma files as we have on FigJam

I need an option where I can tell the prototype view to scale the Figma frame to the prototype device viewport, so that I can change the device type and all the elements are altered according to the defined constraints. (Not just scale all elements) As it is now, I have to decide to design for a specific device viewport to make it appear as intended for that device.

I keep facing difficulties while trying to find something in the community. The previews take forever to upload, so I have to check files based just on titles and I almost never find what I need. Would be cool if you could optimize the preview sizes, so they load faster

comments will sometimes get stuck and stay on the same location of my screen, regardless of where I have scrolled. They will stay the same size regardless of if I zoom in or out. This can only be fixed by hiding and unhiding the comments, at which point they will return to correct functionality for a short time.

Hi guys. Please add a function of a fetch data like in artboard studio app. Video example — https://youtu.be/Pch9B80KnPY?si=6HpSZAi5c4auwMry&t=797 (time - 13:17)

1. Describe the problem your experiencing and how your idea helps solve this There is no way to search for a page/frame in a given project. A user should be able to quickly jump to an arbitrary page/frame by typing the page/frame name in a search box. Introducing a “Jump to…” feature similar to Zeplin’s CMD+J would solve this problem. 2. Add as much context as possible (screenshots, Figma files, mockups, etc.) Zeplin’s “Jump to”:

Can we have a layer type that is an iframe, and we can insert a code inside it to be rendered in the prototype view?

Have swapped instances adopt the color variable and mode that was set on the first instance within the object/component. Basically to mimic the kind of cascading that happens with CSS. My example situation: A button that can have several icons within it, via instance swap. The button I’ve made to have border, fill, and contents colors via theme and state modes—which respond to the container it’s in. The default icon instance within the primary button is assigned the primary contents color. The default icon instance within the secondary button is assigned the secondary contents color. The initial color of the icons within the a separate icon library file can’t be both the primary and secondary colors—SO it would be best if the incoming instance adopted the color and mode of the default instance if it has been assigned there. Conversely I’d think there could be situations where you’d want to

We create and share our design system components with the whole company and we’d like to have a more rigorous process when we publish modifications of the Figma file. If the publish description would be required instead of optional, designers could not forget to add a description to their modifications anymore.

Hello Awesome community, It would be very helpful for Design System builder community support if we could create styles based on other styles, aka style variants to support use cases like these 3: Type Style A needs to be used with an underline to emphasize that the text is a hyperlink. There is no way to amend the style A without unlinking it at the moment. So either I create an extra style or I have elements in my design system that are not ruled by Type Styles; in both cases this creates extra work and potential for errors when updating the typography for specific projects based on the Design system file. Color Style B is used as a Primary accent color @100% opacity but also as a SurfaceTints and State Brushes with varying opacity values. This requires a design system file to include individual color styles for each case (aka Brushes based off

The problem: I’ll be working in one file where I turn snap to pixel grid off because I’m working with type or vectors or really small distances and then I’ll move to another file and forget that snap to pixel grid is off so I’ll resize things and they’ll end up being off by like .02 pixels. Solution Make snap to pixel grid setting only apply to the file you’re in. (Oh and it would also be awesome to have a snap to pixel grid setting that is just for smaller amounts so it snaps to .25 and .5 pixels but that’s something else entirely)

I know that we all love our new variables for text, values, colors (though you STILL need to allow us to plug our existing style library colors in to the variable colors instead of forcing us to remake the primitives for them!), and bools, but I also want to do it for instances! If I have a button and I want to change the icon on it for different button “modes,” I’d like to make it so instead of hiding all the icons on the button with a complex set of bools that toggle them on and off, I could just have it change instances of the icons on the button so that different modes would swap the current icon instances with whatever the mode called for. For example, let’s say I have a “cancel” mode for a set of various button variables. I want it so changing from default mode to this “cancel” mode would not only change colors, text, values, etc, but would also swap the default ✅ icon instance I assigned to an ❌ icon I made for it.

I want the option to add or remove images, and keep the images stay equidistant from each other on the circumference, rather than horizontally or vertically? Adding to that, is there a way to have auto layout settings on a custom path?

Email notifications when you or your team member delete a file you have created. Files go missing all the time & are found by looking in the deleted section. Would be great if owners/creators of files/folders are notified when someone actions a delete

In addition to the very important general need for the ability to find and replace within the scope of a selection, a valuable feature for someone like me would be the ability to replace strings SEQUENTIALLY. For example, I have coordinates that are all labeled “1-1” and I want them to range from “1-1” to “1-15”; right now, because I have HUNDREDS of layers that include the suffix “-1” I have to update each of those manually to “-2”, “-3”, “-4”., etc. within the scope of my selection. If I could just select to replace and increment the “-1” part of each text field sequentially within my selection that would open up whole new worlds of efficiency for me.

Love, love, love the fact rectangles snap to the edges of image fills when resizing them to their original proportions. What would make it even better, and quicker, is if you could double-click on an edge and have it resize to their original proportions instead of carefully dragging them.

When I set a corner radius on a top level layer, that radius should also change any nested layers. For example, my team has components for Table Header Cell and Table Row Cell. I put those components into layers for each row and then in another layer for the table itself. I put a 2px corner radius on the table layer but still have to add a 2px radius to the top two corners of the table header row and also a 2px radius to the top left corner of the first table header cell, etc.

It would be handy to see the usage dates on the admin teams table across the organization, such as last modified, last viewed, etc. To find and clean up miscellaneous teams that are spin-up. And move files into the appropriate teams that will manage care and feeding.

Es necesario tener Figma en español en la app para poder probar los lectores de pantalla en ese idioma. Ahora se mezcla el idioma de mi lector con el idioma de la app haciendo muy difícil la comprensión para mis usuarios ciegos con los que pruebo la usabilidad

If I have a component with a variant whose width is set to fill in the master container and an instance of that variant also set to fill but whose container is a different width than the master container this should not count as a size override on the instance. It means if I then want to change the height of the master variant, it will never take effect until I switch the instance to fixed width and reset the size. “Fill” should count as its own size independent of any particular nominal width resulting from fill. Failing this or in addition to it, width and height should be considered separate overrides.

Hey all, Suggesting a new feature so that I can have a menu item for cropping the imported item. I know it is in the command+/ shortcut and then you can type it… or otherwise you can double click and then edit the properties there. But if it was in the menu bar when I’m using my desktop app, then I could just tag a shortcut through the system preferences on my Mac. So please if you are reading this Figma engineers, a noob like me would love a feature like this. Thanks for reading.

It would be really great to be able to define a new variable that use another variable AND an other color on top. The main usecase for me is to be able to have for example : Variable A : My primary color New Variable B : My primary color + a dark overlay ( 000, 3% ) which is the “Hover effect” for example This way I can change my primary color ( Variable A ) and have all the others colors ( hover, active, disabled … ) which update instantly without having to set every color individually.

picture a FigJam with a software flow made by a design team… its accessed by someone on the dev team. That person can only slightly interact with design team’s layer, and can adjust it’s opacity. Then they do their own stuff over top of the design stuff to start to outline their process in direct reference to the flows. Each team can see (or not see) each others stuff.