Suggest a Feature

It would be nice to be able to choose the slide to animate to in Figma Slides. Currently animations only apply to the next slide, but if we could choose the slide it would allow us to create looping animations. Example: In my latest slide deck, slides 1-4 were created to show an animation on the title slide. I’d like to smart animate from slide 4 back to slide 1 so the animation automatically loops while the title slide is being presented.

I use sections a lot to organize artboards and I set these sections to Ready for Dev when work on these artboards is done. When I move these sections around the canvas (to organise the sections themselves) I have to update the Ready for Dev. I tidied up and now I have almost 30 sections that need Ready for Dev updating.

The height of the frame is 400, and the height of the exported PNG image is 401, which is not equal to the height of the frame.

We need to be able to control the state of other/multiple components when setting a single interaction. I shouldn’t have to set up extensive nested variables, modes, or multiple screens of designs to get a prototype to show whether or not a button is active if a checkbox is selected. It takes thirty seconds in Axure and that includes the time it took me to make an account.

Hallo guys, just a suggestion, can you put un-collapse and collapse on right menu on the layers or frame? Maybe also a shortcut key to easily uncollapse the layer or frame? Thank you 🙂

Can we get CSS Text decoration options. Different decoration styles Gaps between Text and decoration Different decoration colors Different decoration thicknesses?

Hi everyone, I have some thoughts regarding the management of libraries and updates that I’d like to share with you. I have been working with a large design system in the last year and a half ( 100+ files including individual components, token files, variable for themes and modes etc…) and I have encountered a few workflow issues. Issue 1: Publishing a component that has broken properties It happens that some component property gets broken or missing in the workflow, but you can still publish the library where that component lives. This causes the component and sometimes the whole library to get not published, but there is no alert for that. So you realise that the component/library has not been published just when you want to load it in another file to use it. The only indication that something is wrong is a little alert icon in the property panel. Suggestion: Prevent a library to get published if something is not right and include what’s the issue with an alert message in the publish

Ability to select an entire section to use as instance swap preferred values to easily add to section options without having to go into the component and checking the newly added one / select all every time. E.g. for icon I have a frame that contains all my icon options as components. Then a “Icon” component that has each of those available in an instance swap, but the “Icon” has the variants such as size, colour, etc.

When setting up accessible UIs, one of the common requests is language accessibility, which in fact makes a lot of use of text string variables for body copy etc… One aspect that would benefit having access to string variables is text inside components, to have each instance read text strings from the variables collections. This would make language accessibility much easier to design!

Figma gave us some custom property settings for stroke. But they only did half the job. If we can add multiple borders or stroke colors…then we should also be able to assign where those are applied. Figma restricted this to only one of the color options. You have no way to tell a shape to have a red border on three sides and a gray border on the other. You know…like you can do with CSS? For example, I had to nest a frame and maneuver top and bottom padding on each size of input field so I could apply the separator line for the addon section.

Unlock a new perspective on your design projects with the Mindmap View, tailored for organizing frames based on their names and connectors. This innovative feature visualizes your frames as interconnected nodes, creating a mindmap that highlights the flow and relationships within your prototype. Easily trace connections between frames, gain a deeper understanding of your design’s structure, and manage complex interactions more efficiently. The Mindmap View simplifies navigation, ensuring that you can quickly grasp the overall architecture of your project, making your design process more intuitive and effective.

Hello, as the majority of Figma users are UI/UX designers. After designing, we must give written documentation regarding the product. Currently, I’m utilizing Confluence from JIRA. It would be fantastic to have document authoring in Figma. Developers do not need to bounce between JIRA and Figma to better grasp requirements. Swadesh Nepali Founder & CEO, Black Tech/RestroX

I think it would be cool if I could open a doc and see the last page I edited. Sometimes I stash work in a multi-page document and can’t remember where I put it.

We often have multiple people working on multiple-but-tightly-related features in the same file and it makes commenting a real pain. I get emails and Slack notifications about comments on other designers’s pages. If I’m going through my own comments, I see all of theirs sprinkled in. To avoid it we work out of separate files. We then have to remember to go merge our files together later, since the work ought to live on as one single file once the first version is out.

Figma needs the ability to link online fonts, removing the need for plugins on the computer. This could be done through code embedding or by searching a library like Google Fonts. Fonts would load while working on a project and unload when the tab is closed, just like on regular websites. There’s no need for plugins to load fonts on web pages. 😛

When a frame is set to fill, and the aspect ratio is locked, the frame should keep that aspect ratio when resizing. Currently, the width will fill, ignoring the locked aspect ratio.

Sometimes, when exporting to SVG Figma likes to add shape-rendering="crispEdges" to some paths in SVGs. This introduces aliasing to the edges of a circular shape This is what it looks by default and when I removed the shape-rendering attribute respectively: (I couldn’t attach two seperate images since I am a new user) I propose this is either disabled by default, atleast for anything circular and provide an option to enable this. In the editor it is rendered normally, and this only happens when exporting the design.

I swear, if this isn’t added soon, I lose my mind and quit Figma altogether. When working on a file, local styles can always be selected on accident when no frame is active. I don’t know what exactly I did, but apparently I manged multiple times to select it on accident and press the delete key while intending to delete something else. So please add a feature to lock styles or add a pop up warning about deleting them; that’s basic error management in UX 🤬. Also when deleting it, it would be nice to be able to restore them more easily; maybe instead of removing a connection completly, add a label which signifies that the link is missing like with fonts. Then you can just copy in your styles again and it at least they reconnect automatically. PS; before creating this topic, I found some posting which suggest that styles disappear randomly from time to time; so maybe I assumed too soon that it was my error; but still, these improvements should be added. And please fix this curcial

Figma can read and activate advanced features from OpenType fonts, but currently it can’t access the same features of many macOS built-in fonts, which uses AAT (Apple Advanced Typography) instead of OpenType. Attached screenshots are two common bundled fonts, Helvetica Neue and Hoefler Text. Using TextEdit, I can access and turn on/off their more advanced features (round punctuation, oldstyle figures, etc), and I can do the same with CSS declarations in browsers as well. However, there is no way I can access these in Figma. Supporting the same advanced typographic features with AAT will make an impact because a lot of people still use default fonts in production for expediency or cost reasons.

So basically what I’d want is a mode for variables that shows/unhides everything? Atm (auto) is set to be the first mode in the variables list - which does not work great, since we create master components that sometimes contain items that are not being displayed in that mode (here: edit). Here the whole “You declared” item is not shown since it’s set to only show in “filled in” and “mode”. Which is bad, since I want to see ALL the stuff that’s contained in the component… And be able to change it without having to switch modes first. Imo it should be the (auto) mode (since this is the default which is convenient); but honestly any built-in mode that does that would be great. (and yes I know there’s a workaround: just create a mode called “show all” and set all booleans to true - but what if I tell you I run out of modes quickly? 🥴)

Basically the title, there’s a reason this feature exists in base Figma. Loving slides so far, especially in design mode and grid view, but the inability to change the canvas background color causes significant usability issues. In dark mode, it’s nearly impossible to see black text elements that have been dragged into the abyss, and it would be equally hard to design a deck with a dark background. At the minimum, I would like to be able to toggle the background color between light and dark separate from the overall app theme, but it would be best to have a range of neutral hue values and/or full hex control like regular Figma.

A lot of search and replace use is adding or removing line returns from text, would be good to be able to do this, all other software I’ve ever used has this functionality.

At one point the Annotation feature in Dev Mode allowed me to add an annotation to a frame, and when I copied that frame the annotation would be copied as well. This doesn’t seem to be working for me anymore. It was extremely nice when it did, because I often copy frames either to make a new iteration, put a copy on a different page, put a copy in a different file, build out a user flow, etc. and having to remake an annotation over and over is hard to keep track of. Personally I need annotations to be connected to whatever I first put them on until I specifically delete it, but I can see how this could be annoying extra work for people who do not need that. Maybe this could be a setting, where you check on/off whether you want annotations to duplicate or not.

Hi Figma Community & Team, one issue we have with using the dev mode annotations is that it is very easy to accidentally delete annotations which are attached to design layers when changing a design. We would need some more security in annotations not disappearing with the design elements, to store important information in them for the devs. Also it would be great to be able to move and attach them to other design elements when changing something. Best regards Mikka

Hi Community & Figma team, we are using branching to keep track of changes in files. Furthermore, we would like to use the Dev Mode annotations. However we noticed, that it is not possible to merge a branch that only has changes to annotations. However, this is necessary in case a ticket of us only contains changes to document for developer resources linking etc. Would it be possible to see changes also as changes to the file to be able to track & branch them properly? All the best Mikka