Share Your Thoughts

The create a Figma Slides outline using Figjam is useful, but we need to be able to turn off the AI content fluff which ist adds to the slides because it is generic and meaningless and makes the ideation process harder particularly for neurodivergent people. Adding noisy words that mean nothing make it hard to think conceptually.  Creating a presentation can be a great way to organise thoughts and structure ideas. The fluffy content just gets in the way.            

Hi, can anyone help me revert this UI in my Figma design file back to the default UI? I’m having trouble figuring out whether certain elements are set as auto layout, frames, or something else. It’s making it harder for me to work. Any tips? T_T

With Miro, we are able to copy cells from a google sheet/excel, then paste them into Miro where each cell becomes an individual sticky note with respective colors applied. This is great for transcription and affinity diagramming during research. I’d LOVE to see this in FigJam 🙂

We have a connected project with an outside vendor who is helping us create new components in one of our shared libraries. We’d like them to be able to create a branch on our existing library to submit a changed/new component without giving them full edit permissions.Full edit permissions would allow them to make changes to the file without branching or to merge changes without our approval. And we only want changes to be added with our approval.Having this sort of “viewer can create a branch” setting would eliminate the need for us to collaborate in a separate file before moving the component into our library.Sharing in case it might also be a helpful feature for others.

See a simple exemple below :  

Hey ,Its glad to hear that we have figma dev mode server , well done folks .but there is a problem most of the time i am facing i given a figma frame link it fetched the frame correctly but it generated completly a wrong screen which was not even 1% equavalent to what i gave .i used claude 3.7 model for the generation . Figma generated this screen (output)  Figma frame input  

I've been using and testing Figma Make to create interactive prototypes based on the screens and flows I’ve already designed.It would be really interesting to speed up the design-to-code workflow if the prototype in Figma Make could be updated live. That way, I could iterate on changes and improvements in my design without having to go back to Make and write new prompts to explain those changes.This could further streamline the handoff process for animations and interactions by providing more structured code for developers.

I was really excited when i learnt about the inclusion of grid in figma, but was disappointed to find that it is quite under featured. One of the main things holding it back is the ability to set min and max widths/heights on rows and columns, and possibly freeze a row/column too. The current solution of having separate components causes to many alignment issues to be useful. For this you would probably need some way of selecting individual rows and columns too.I don’t know what you have down as priorities for upcoming developments, but these would definitely help Grid be useful 

I would like to add a max-width to a text box while using auto layout to keep the word count per line at a reasonable minimum. Currently, I have the text element set to “Fill Container” which makes the text respond very nicely to the screen size. But because it is set to “Fill Container”, the text spans the entire width of the element which makes the text lines more difficult for users to read quickly.

Hot take,Figma Make, in it’s current beta form, is underwhelming when it comes to being able take a design and turn it into a usable coded prototype quickly.This feature will have a huge impact on designer-developer workflows only when the speed to getting to a Make prototype is faster than getting to a noodle prototype. Until that happens, designers will continue to stick with what is fastest/most effective for them.Being able to provide Make with the entire context of a prototype + developer notes + design library inside a given file/page seems to be the best route to doing this.I hope the refactor needed to get to being able to provide access to all of this data is well underway, but if not, I’m putting my trust in the rest of the community to get some movement behind this idea here in the portal.

Nested properties do not show up when selecting multiple instances of components Example when selecting 1: Example when selecting multiple: My expectation would be to also be able to set up the decoration left icon when I'm selecting both layers. 

Hey guys,I don’t use masking too often, but everytime I use, I am baffled about the lousy UX :)) I mean it’s like nobody gave a flying !@#$ about it :))The mask has to be underneath the masked object. Totally opposite to any form of logic, especially since the mask is alwas smaller than the masked object, so selecting those two has to be done by clicking/dragging over the area to make sure both are selected. That can be a pain in the butt if you have many elements on the frame, and then you have to rely solely on finding the elements in the assets panel. Good lunk with that :)) If you mask an object, you have to probably group it afterwards? Otherwise, if you wanna move it, you’re just moving the masked object behind the mask, while the mask stays in place. Makes perfect sense????!!!! If you wanna edit the mask you have to find it in the assets panel, no click/hover will help you in that situation.I can probably come up with

Our team is part of a larger organization, and all our Figma files are in one Figma Team for which I am a team admin. We have some Default Libraries set for the entire team, but need the additional ability to set Default Libraries for specific project folders. I’m not seeing the settings to do this right now.

Just saw the new sketching and fill tools appear. You’re on track to own vector production. Now go after raster/print (seriously)! Amazingly, Quark Xpress is still alive and seems to have developed some serious content-management tools. Buy them! Bring print production into a collaborative Figma space. 

A la Adobe Illustrator, please. I want to glide in and out of zooms, not jump.

Sorry for the long message, but it's really important, so I wanted to share the full story.I believe the option to trigger auto width and auto height text resizing via the command palette was unintentionally overlooked. This feature fits naturally with other text-related actions already available in the palette and should be included for consistency and usability.Adding it would not impact the UI or workflow for anyone who doesn’t use it, but for those who do, it can be a significant efficiency gain. It’s a small fix with meaningful benefits, and optional shortcut support would be a welcome addition.Currently, for every text element, we have to manually change the default resizing settings. On UI screens with many text boxes, this becomes a repetitive and inefficient process that adds unnecessary clicks and slows down the workflow.Adding a command to the command palette for auto width and auto height would solve this without affecting the interface or exi

You can do that right now like this:https://forum.figma.com/ask-the-community-7/how-to-delete-a-variant-property-26406?postid=51847#post51847But there are a couple of problems:1. You will lose the component description2. It doesn't feel right in general having to do it this way (moving the variant out of the component) when you should be able to do it the same way you can ungroup elements. I already created a post to suggest this feature, but then I realized I created it as a question and I recreated it to make it a conversation instead.

1. Describe the bug/issue you’re running into? I cannot modify the thickness of lines, both in arrows and in figures 2. Are you able to consistently reproduce it? If so what are the steps? select object or line and when the options appear, there is no tool to change the thickness 3. Share a screenshot, recording, console log, link to the file, etc.

The problem is, I felt like I was being ignored because I had to change from ‘Bent’ to ‘No endpoints’ over 100 times. It was really painful and distracted me from my workflow. I wish I could quickly switch the connector style (Bent, Curved, or No endpoint) by using a shortcut. I could  keep on typing “X” when I want to change an optional setting (Bent, Curved, or No endpoint) on the keyboard. It would keep the same settings for the last time I used them (currently, it defaults to ‘Bent’).  

Problem:When on design mode, you can move between slides with up+down and right+left arrows.But when presenting you can ONLY move between slides with the right+left arrows, which is un-natural to RTL languages (such as Hebrew).Solution:Adding the up+down arrows option to the present mode can be very helpful here.

When trying to add an interaction to a frame (such as On Click > Back), I would expect clicking the (+) icon on a frame to allow me to edit interaction properties. Instead, you have to go to the right pane to do this.XD had something like this and thought it was convenient. Seems like an easy win to me.  

When I was working on large-scale projects, I found that some design drafts often couldn't be done with Figma and were made using Photoshop. However, I needed to display them in my Figma design drafts for members of the project team or developers to view. But at this point, I have two solutions: one is to convert PSD files to PNG photo format, and the other is to convert all design drafts to third-party annotation software. So my idea is whether Figma can develop a PSD parsing function. If this function takes too much time, can it provide a thumbnail image for viewing PSD annotations or a plugin like function? What do you think? I often experience lag in Figma UI 3.0, which is not as smooth as before

Allow branching of branches to allow for feature branches from the development branch and development branches from the master branch. This would be closer to what we currently have in Git and would allow for more control. The development branch could represent all reviewed and approved feature design work that had been done but not necessarily released live in code. The master branch would represent what is live in production.

The ‘Team Fonts’ feature provides a centralized font library, allowing team members to share and manage commonly used fonts. Through this feature, teams can ensure consistency across all design documents, while also making it easier for team members to find and use the fonts they need. For instance, fonts unique to Mac users can be uploaded to the ‘Team Fonts’ for sharing with Windows members. We believe this feature can further enhance Figma’s user experience, especially for teams with a substantial need for font resources. We look forward to Figma considering our proposal and are willing to provide further feedback and suggestions to help refine this feature.

Hello Figma Team,As we continue to build more detailed and complex components using the properties panel, we’re finding it increasingly difficult to maintain visual clarity and organization—especially when there are multiple variants or nested properties.While the original designer might understand the structure, it becomes quite inefficient and confusing when collaborating with other team members or handing off to developers.It would be incredibly helpful if we had the ability to add custom dividers or section separators within the properties panel. Even a simple visual line or labeled grouping would significantly improve usability and communication within teams.Is there any plan to support this kind of feature in the near future?