Share Your Thoughts

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.

For the moment the “ready to dev” in the top left corner show all status of a “ready to dev” task (ready + completed)The number shown become unclear the real number of ready to dev task to do. I may have 1-2 tasks but the number show 24. I don’t think knowing the total number of task relevant. It’s would probably better to allowed to filter that number to user specific need. Tx.

Firstly great job Figma Font variables are here!!! Figma tutorial: Variables for typography The only thing missing is the use of percentages in the line-height property. You can not use a percentage in the line-height as it only accepts variables that are a number type. Although the variables for line-height caters for pixel (absolute) line-heights (10,12,14)- it does not accommodate relative line heights. In other words you can’t use percentage variables for line heights that are a percentage of the font size (100%, 120%,150%).

Hello Figma Team, I hope you’re doing well. I’m writing to request that you please do not stop or heavily limit the Figma AI credits after March. The current credit limitation (around 3000–3500 credits per month) is very restrictive for teams like ours that rely heavily on Figma AI for daily design work. If continuing unlimited usage is not possible by default, we would really appreciate an option to purchase a monthly AI credit plan even for just one month at a time. We are fully willing to pay for an upgraded or add-on plan that provides unlimited or significantly higher AI usage, rather than being capped at a fixed credit limit. Figma AI has become an essential part of our workflow, and strict credit limitations significantly impact productivity. Offering a paid, flexible credit or unlimited plan would be extremely helpful for professional teams. Thank you for considering this request. We truly value Figma and

Setting durations, easing curves, delays, especially for Smart Animate animations are essential tools when making presentations in Figma in order to make fluid ‘Keynote-like’ transitions. Unfortunately these are completely absent in Figma Slides at the moment, making it pretty much useless to our team. We will keep making our presentations in Figma Design and linking everything by hand🥲 until these crucial settings are implemented in Figma Slides…

Hey everyone,I work extensively with Figma prototypes, and one functionality I feel is really missing is onScroll.the ability to trigger interactions based on scroll events (similar to scroll animations or parallax effects available in other tools).Does anyone know if Figma plans to add this feature in the near future?If not, are there any smart workarounds to achieve scroll-based animations within Figma itself without relying on external tools?Would love to hear your thoughts!Thanks!

This update is genuinely one of the most frustrating UX changes I’ve experienced in a professional design tool 😡 😡 😡The new left-hand navigation panel permanently steals ~60px of horizontal space on small screens, which is completely unacceptable. That space is my primary working area — the canvas. I am literally losing room to do my job so a panel can sit there doing nothing most of the time.Yes, Variables, Files, Assets, Find, and Library are important.No — they are NOT minute-to-minute actions.They do not deserve permanent, always-visible real estate. This panel is idle 90% of the time, yet it constantly punishes my workflow.On smaller displays, this feels especially hostile. Instead of prioritising the canvas (the entire reason Figma exists), the UI forces a bulky navigation column that adds zero value moment-to-moment and actively makes precision design harder.

Right now, working with branches is quite limiting in the sense that: If I have a Figma project, with 2 frames (Frame “A” and “B”) contained within the same section I open my branch and select “Update from main…” Frame “A” has some changes I want to APPLY to the branch, BUT Frame “B” has some changes I want to KEEP in the branch PROBLEM: because both frames are contained within the same section, when updating from main file, I can only resolve the conflicts by updating all the frames, and therefore losing either the uptades in the branch or in from the main file. What I need: More granularity in what updates from the main file I need to ADD from the main file and which ones to keep in the current branch I’m working. Conflict resolution today is ALL or NOTHING and this doesn’t work. Sections are great for keeping my files organized, but they’re making it IMPOSSIBLE to work with Figma branches. Please fix this.

This makes it easier to use components in designs for different screen sizes. And then you don’t have to calculate every time what 40% or 60% of the width is. This also makes it easier to design scalable applications that grow with the width of the screen.

Figma MCP should provide frame-to-image exporting as a tool. That way AI could export graphics in a page design as `.svg`s, `.png`s, etc... and upload them to our cloud bucket,or put them in our web assets folder.

Displaying the frame in the interface was a terrible decision; it made the interface very cluttered.

I would like an option to hug content until the container it is in is too small. For instance, I am making a tab bar where the tabs are set to fill so they adjust with screen sizes. The title on each has an info icon to the right. The text has to be set to hug for the icon to stay right next to the text. However, that means if the text is long, when the tabs shrink the text extends out rather than wrapping. I would like the option to set the hugged text to wrap when it extends past the parent container without having to manually change it a each breakpoint.

You can currently set multiple stroke colours to an object, but they will share the same properties (thickness, position, etc.). My idea is that you should be able to set all stroke properties on each stroke: Make sense or am I missing something?

WHEN - will Make be able to read the very design system tokens, primititves semantics and componenets that third party applications already can? I love the platform but this is such an own goal for anyone really clued up- when and why is this not allready implemented? Whats the point in figma make ifw e can’t control the design system and connect design system primitives,semantic and componenets with wrappers around shadcn components etc without doing it manually.For anyone with a modicum of development knowledge this is crazy ommission. It puts me off recommending figma. I might have to resourt to my own custom ontoligies and the daft thing is claude etc reads the darn tokens and renders to production so that kind of also knocks figma make out of the game own goal number 2. Someone please please tell me I am wrong. This seem a massive hole in capability which shoulld have been a main reason for building make to start with doh...

I want a shortcut to show and hide / expand or collapse the pages and layers panel. If I got one I’d want the pages panel to open and close by keyboard shortcut. It’s too much work to constantly open and close the pages panel. Overall, I’d say that the pages panel needs a UX review. We’ve now got so many pages that it’s a tough experience, but I’d say that if I could choose a page from a dropdown list as opposed to opening and closing the dang panel everytime that would be awesome. Or, ideally what if when I hit page up or down the magic menu (command + p) or whatever it is called displays all pages that I can search on quickly or use the arrows to thumb through them. Some mail applications to do this today for UG folders and it’s way nicer than trying to find a folder. Maybe use that AI money for things like this and not trying to tell me what names my buttons ought to be. ;) 

Hi Figma community, We are excited to introduce Lyra translate and go by CBG, a Figma plugin designed to make localization and translation part of your design workflow, not an afterthought.As designers, we constantly run into the same problem: designs looked great in one language, but the moment translations are introduced, layouts break, text overflows, and context is lost. Reviewing translations outside of Figma or without visual context is slow, error-prone, and frustrating.So we built Lyra, a plugin that lets you translate directly inside Figma, with full visual previews, so you can see exactly how your designs adapt across languages in real time. We’ve also enabled an export function, so you can send your translated strings for professional translation, collaboration, or production making it easy to move from design validation to global launch without breaking your workflow. We’ve put a lot of thought and industry lessons learned into bu

Currently, only Preview and Code edit modes are visible. Are additional editing modes accessible?

This is so annoying. I shouldn’t have to use the web version to disable this. FIGMA should allow me to turn this off in the settings. I don’t use Figma every day and I certainly don’t want it to open every time I log in. Clearly, this has annoyed several users but you fail to listen. STOP FORCING ME TO OPEN FIGMA AT LOGIN!!

Ver aquelas várias pessoas no arquivo enquanto eu trabalho me deixa ansiosa. / I feel anxious when I see many people in the file while I am working.

Auto-Layout has padding (inner spacing), but no margins (outer spacing). Currently the only 2 ways to add spacing is to: Create a spacer element or Wrap the items in another frame and apply gap spacing This creates a lot of unnecessary frames, and sometimes creates nesting so deep it goes outside the layers panel. Not sure if a technical limitation left this out of consideration in the first few versions of Auto Layout, but it would be much appreciated if it were included in a future version as it comes up as a significant limitation many times a day.

Hello. I was wondering if it is possible to have percentage values in variables, like setting percentage value for frame widths or shape sizes (etc.) that have variable modes applied to them? Percentage values could respond better to content that varies within a frame or frames within frames.

Anyone knows if Figma mentioned something about adding analytics to their slides in presentation mode? Same as pitch.com where you can measure the data from people that open the deck? If not, it might be a nice idea on the roadmap for Figma Slides? What are your thoughts on this?

I was very excited to hear that grids were coming to Figma. CSS Grid was introduced years ago and brought with it many things that flexbox was incapable of doing, so I was hoping for a similar level of new capabilities here, and I genuinely cannot believe that this feature is being shipped in its current state (even as a ‘beta’). This is a very long post, but I feel like this feature has been implemented so poorly that it legitimately sows doubt in Figma’s capabilities to deliver features in the future.Inability to ‘hug’ contents Both rows and grids themselves are unable to resize themselves to match their contents (‘Hug”). Row heights must be either “Auto” (1fr) or a fixed height, meaning that if you want your rows to be sized per their elements, you’ve now manually defined each row height in px (not even a variable value), and instead of getting a clean CSS output, now you have however many rows defined in exact values, destr