Suggest a Feature

Adding auto layout should not change the child’s auto layout settings. When applying auto layout to a parent, the settings of the child’s auto layout width changes for example from fixed to fill, or in some cases from fill to hug. Therefore I have to adjust every child and child’s child again to have things work like I wanted in the beginning. This is a super annoying and frustrating feature. Keep the child’s settings as they are when adding auto layout to the parent.

We definitely need these, until every Styling option that can be applied to text in Figma is added to the great new variables options, it’s not usable as a complete UI system. Text decoration values like underline, slashed, uppercase, are all vital parts of out text style system. Would love to see these be added along with REM/EM support or at the very least percentage support for Line Height & Letter Spacing.

Reopening a thread for interest in a presentation mode in FigJam (here’s the original thread that’s now closed). Of course someone can follow a specific user as they zoom and scroll through a board, but the viewer experience–especially for those unfamiliar with FigJam–could be improved if a specific presentation mode existed. Thinking similar to Miro’s, which would mean also needed to add “frame” elements to be able to have it function like a slide deck.

When showing files in list view, I want to see more meta data for the files. who created the file who did the last edit who has access implemented libraries components in this file … and so on Also I want to configure which meta data I can see, just as in any other table or list view.

It would be very cool and convenient if you could control slides and read notes from the Figma app on your phone like Keynote. Maybe other functionality like marking and pointers from there as well

There is no easy way to copy/paste a line start and end shape when you copy/paste properties between lines in Figma. I use this for creating flow arrows between screens, but it only copies the color, dash/solid, and stroke width. It would be great to include the stroke start and end shapes with these properties so that I didn’t have to set these manually each time I draw a flow arrow.

So, without going into a bunch of specific use case examples, the question is pretty basic; with all the logic and interactive capabilities, why doesn’t Figma just support BASIC state styles for all elements/components?  I mean, I can attach visibility to a variable, but I can’t just set a basic hover state for a box?This makes no sense to me.  I can understand keeping things manageable and not doing a full CSS implementation, but the idea that I have to “roll my own components” just to get something to show a different background color is kind of insane.  I dont want to make components every time I need something in a proto to change in a basic way.  Just draw a box around a core set of universal styling behaviors, attach them to every object by default, and call it a day.TL;DR - Hover states should be a core, definable state by default for every element in Figma, from text to shapes.  Off unless defined, just add the field to the fill, stroke, and other properties (f

I wanted to share my feedback regarding the upcoming removal of the option to use UI2. As a dedicated user, I strongly believe that maintaining UI2 as a permanent option is essential. I have spent significant time with UI3, and despite giving it a fair chance, I find it less efficient for my workflow. This isn’t a matter of needing more time to adjust; it is a matter of sheer productivity. In UI2, I am noticeably faster and more effective.The feedback and frustrations voiced by others in the community also reflect that not all users are comfortable with switching to UI3. While UI3 has a more polished appearance, it compromises functionality. I appreciate the intentions behind the redesign, but in its current form, it does not match the usability of UI2.I would be perfectly content if UI2 no longer received new features. For me, it has reached a point of feature saturation where it feels complete. The existing capabilities serve my needs perfectly, as I believe they do f

I'm super excited by the idea of leveraging AI to streamline design-to-engineering collaboration at our scale. As the solo designer supporting a 25-person SaaS product team, managing efficient communication with dozens of engineers is challenging. I'd love to create an automation—using n8n—to help interpret design feedback or requests and instantly suggest helpful design system context using AI transformers. Imagine someone writes: “A user is able to easily onboard with self-service into a freemium onboarding flow,” and the AI immediately responds with clear engineering notes like “Use attached design system guidelines 12 (image), 15 (image), and 29 (image),” alongside direct links to relevant Figma asset components and simplified wireframe mockups. This would make our design system truly interactive and proactive, greatly amplifying my effectiveness and allowing engineering teams to confidently jump into implementation with ease. As a designer I could define the rules of the design

I would like to be able to export from Figma slides to PPT and keep the embedded prototype functionality. We are bound to PPT by AV teams at events (out of our hands) but we strongly want to use our prototypes in those PPTs. Our current work around is to record video snippets of someone clicking through the prototype, which is time consuming and needs to be re-recorded any time a change happens in the prototype. I was very excited when I saw the new import/export feature but unfortunately without the ability to embed prototypes we won't be able to use it as much as I’d hoped.

Hello!! I would like to personalize Section’s borders like on rectangles. Putting color un the top border of the section could be helpful

There are already plug-ins for that case but unfortunately they are not usable.The case is:I have a component in which different content can appear (text, input, checkbox etc.) I don’t need/want to create a component with all these options to show/hide as most/all of the designs will have a different set of elements inside. I just need the container to be consistent across the application while the content - freely arranged. This should also allow to place other components in the content zone (that’s the main problem with currently available plug-ins).

When you use Webflow, you always know if this value is a default value set by the system or it got overridden by the user. It’s due to the C in CSS. And it’s awesome!In Figma, there are multiple issues with not knowing and specially not seeing whether I changed a value or not.Two things related to that, really needs improvements is the 10px default value in auto-layout and the 0 to clean out a value, instead of empty the value.In Code, a zero is a value and not empty. (none) In Figma, zero means both. And without a color scheme to see where I applied my values on a main component or only on an instance of it, makes it so difficult to work with. If my developers inspect an element, they don’t know if this is an element with no padding or zero padding. In the best case, I can set my default values (e.g for the auto-layout) with my variables, or they are not existing, and I have to set them myself. And if I def

I receive requests to view Figma from persons not within my organization (they are using personal emails which I cannot identify who are them). Suggestion: Allow me to edit and prompt a message when users request to access Figma. This is so that I can put down some conditions for those requestors to be aware not to use personal emails, etc. Or allow me to type in reason of rejection when I reject such request. This is so that such person can be aware why his/her request is rejected.

Using `CMD` and `+ or -` to zoom is too simplistic: it jumps from 50% to 100%. Often, 50% is too zoomed out, 100% too zoomed in. What about 75%?What is the keyboard shortcut to zoom to selected item (as when you double-click a layer)? “Zoom to fit” is for everything, not what I mean.Wacom tablets have a meaningful zoom using the wheel, which helps but it would be better as a keyboard shortcut.

Another QOL Ability to clip content on slides (or even just on export) so that the content outside the slide is not in the pdf

When restoring a component, it should merge more seamlessly with the system. There should be an option to retain or discard modifications made to the original component. This is because sometimes I integrate a component more deeply into the system while still needing to keep certain text and details unique to each page.

It bothers my OCD to no end that the first item pasted into a page is not given the coordinates of x:0 y:0

I would love more spelling functionality. Currently, I need to select text to see spelling mistakes. It would be great if Figma would notify me of spelling errors by a search or a little pop up/count.

Implement variable font property in plugin API and rest api Unfortunately it is not possible to get the complete properties for variable fonts via API access. Please implement the CSS property “font-variation-settings” for “wght”, “wdth”, “slnt” … “opsz” Or have I overlooked something, how do I get the information via the APis?

Hello! We’re using quite a lot the underline styling for text in our interface designs, and copying text properties do not also copy the underline decoration details, like Thickness and Offset.Would it be possible to define a reusable style for underline decoration to keep things consistent and efficient?Many thanks!

A component’s playground dialog, only accessible via traversing through Figma’s UI.Allow sharing a direct link to a component playground, not unlike how you can share Storybook links such as this.The job to be done is to spare devs (or anybody, really) the drudgery of schlepping through Figma’s UI just so they can see how a component was designed to work.Not sure if this functionality already exists, I couldn’t find any documentation for it.

I’m currently working on a product for a client where I need to display CO₂ data. Unfortunately, it’s a significant issue not being able to present the data correctly, as Figma’s settings for font styles don’t support subscript for the "2."It would be fantastic if you could allow this adjustment in the styles to ensure accurate data representation.As it stands, right now I have to detach the font style to design so that the user understands the data.

Hi there, we’re currently running Figma in an enterprise license with 10 UX designers and about 20 developers in total. At the moment our annual costs are around $9000 for the full design seats. With the new dev mode pricing we would basically double our annual costs for some basic features a good design tool should offer out of the box. Our devs don’t need fancy “Customize code output” or “Sync design files with their codebase”. They simply want to see all our variables in an easy manageable way, navigate and inspect frames and components ready for dev and maybe track some design changes. Paying almost 9k additionally just for these basic features is insane, especially since our UX designers that have access to the dev mode basically don’t need it. Also there are basic features missing like exporting dedicated handoff collections of components, frames or flows. It would be cool to be able to get a free dev mode seat to every design seat and be able to apply this seat to

一度アルファベット（半角英数字）入力モードで適当に文字を打ってから（例：aaa） ひらがな入力モードに戻してテキストを打つと解消されました