Share Your Thoughts

I think it would be great to see keyboard shortcuts for the ‘Auto height, Auto Width’ text box sizing features. I use these all the time and it would be really beneficial to have a quicker way to change these 🙏

 i can do this all day。。。。。。。。。。。

Although I find the new autolayout UI extremely convoluted and overdesigned, the ‘hug/fill parent’ feature is great. However, It would be immensely helpful to have more control over how the elements fill the parent. Currently, the only option is for the elements to fill the remaining space, but oftentimes, I need certain elements to take up a certain proportion. Example: I need element-1 to take up 2fr (~66%) and the rest to take up 1fr (~33%). It would be a game-changer if we could use ‘fr’ units. Framer does this beautifully and it’s vital for efficient, adaptive layout workflows:

Add native two-way sync between Figma variables and a design tokens file so changes made in Figma or in code stay aligned automatically. Figma already supports variables through the REST API and Plugin API, which teams use today for custom sync workflows, so built-in syncing would reduce manual reconciliation and plugin dependence.

Hey Figma So I have been building our component library and stumbled through this issue where I built parts of the component that are not needed to be published because they are only make sense to use them inside the main component. So having these nested components being published make it confusing and clutters the library. Can we please allow Instance swap property and Slots to have these components show up I literally picked them as Preferred component but they won’t show up since they are marked as Hidden.  

I have a single page site that has a nav bar that scrolls to different sections on that page. I want to add sub pages for some of the content on that page, and I’m trying to add the same nav bar and anchor a nav menu item to a section on the main page but it doesn’t seem like its possible unless its on the same page. 

I'd like to suggest adding additional readiness statuses beyond "Ready for Dev". For example:Animation Ready UI/UX Ready Legal ReadyThis would allow teams and agents to understand which aspects of a design are complete and which still require attention, rather than relying on a single development readiness indicator.

Add native JSON / Lottie format export support for Figma animations and prototype interactions directly from the Export panel.Why is this needed?Currently, to export UI animations or micro-interactions as light-weight .json (Lottie) files for web and mobile apps, designers have to rely entirely on third-party plugins (like LottieFiles or Aninix).

Add a unified, searchable variables table directly in Dev Mode so developers can review all variables, modes, and collections in one place instead of only seeing variables tied to the selected layer. Dev Mode already supports variable details, suggested variables, and access to local variable collections, so expanding this into a full-file view would make multi-theme and multi-brand systems much easier to inspect.

I'm building a blog with Figma Sites CMS, and articles vary a lot in how many images they use, some have 1, others 5+, in different arrangements. Right now a CMS Page is one shared template for the whole collection, so every article renders with the same fixed layout. If an Image field is left empty, it just becomes a transparent fill, the layout doesn't collapse, so I end up with blank gaps instead of a clean design.Figma Sites already ships a big library of pre-built blocks with different image/text combinations (Insert > Blocks), which is exactly what a blog like mine needs. There's just no way for the CMS to pick a different block per item based on how much content that item actually has.Two things that would fix this for my use case:1. Conditional visibility tied to whether a CMS field is empty, so an unused image slot collapses cleanly instead of leaving dead space (similar to "Is Set" / "Is Not Set" conditions in Webflow or Framer).2. The ability to swap which component/block

I want to share feedback on the Figma Make credit system, because in its current form it is not workable for real projects.Yesterday I spent one working day building a page in Make (Full seat, 3,000 credits/month). By the end of the day I had consumed almost the entire monthly allocation — without reaching the intended result. The core problem: the agent frequently makes mistakes, ignores constraints, and breaks previously working parts of the build. Each mistake requires another prompt to fix, and each fix consumes more credits. The more rework the agent causes, the faster credits drain. Effectively, users pay for the model's errors.Suggestions:1. Improve agent reliability, or stop charging full credits for correction cycles caused by the agent's own errors.2. Add cost estimates before execution, usage alerts, and spending caps.3. Reconsider whether 3,000 credits is a realistic monthly limit for professional iterative work — right now it can disappear in a day.I like the product conce

Figma can you please add the Font Miranda Sans. Its on Google Fonts. Thank you. 

Hi! Many keyboard shortcuts do not work when the Russian keyboard layout is active. To use them, I have to switch to the English layout first.This interrupts the workflow, especially when working with Russian text and frequently switching between typing and design tools.Please make keyboard shortcuts work consistently regardless of the active keyboard layout.

Annotation orientation control (vertical placement)When laying out flows horizontally, annotations from one screen's frame overlap the adjacent screen because they render to the left/right. Request: allow annotations to render above/below the parent frame instead, with the same anchor logic rotated 90°. Ideally a per-frame setting with a global default.

Currently you can set things like, 5.99 or 4.32 but you can’t show 5.00 by default. This looks weird when you start adding amounts like #amount + 0.5 which will then look like $5, $5.50, $6, $6.50. It would be nice if instead it showed as $5.00, $5.50, $6.00, $6.50

The current Tables feature in Figma feels quite limited. It would be fantastic if some basic functionalities could be introduced soon, such as: • The ability to easily resize cells without needing to adjust font size • The option to merge cells • Top, middle, and bottom text alignment options These enhancements would bring Figma’s table functionality more in line with what we already have in tools like Keynote and Google Slides.

As a non-admin user there doesn’t appear to be a way to see a list of the plugins that are approved for use by the organization. Currently only admins can see a list of approved plugins in Resources tab in the Admin Settings. Non-admins can only see a list of installed plugins. This list is accessible through the menu option Plugins > Manage Plugins… Would others derive value from a list of approved plugins?

I’d like to be able to choose a thumbnail (either a frame from the video, or upload a thumbnail) for an object that has Video fill. Currently Figma uses the first frame of the video as the thumbnail, and if that video starts all black, then the thumbnail is just black. It will show fine in prototype view or mirror once the video starts playing, but when you are editing it would be helpful to see a frame of the actual video so you can adjust properties of elements (e.g. colors, opacities, gradients) and see what they’ll look like composited with video.

Hello Figma Team,I really enjoy using Figma and I use it every day.I would love to see the Android app support the full Design Editor, not only viewing, commenting and prototypes.Many designers work directly from phones and tablets, especially when they are away from their computers. Having access to tools like Text, Shapes, Fill, Layers, Typography, Effects and Export in the Android app would make Figma much more powerful and useful.Please consider bringing the full editing experience to Android devices.I believe many Android users would benefit from a complete mobile editing experience.Thank you for your great work!

Part of the value of utilising the Figma MCP for skills that generate slide decks is consistency, but what would help a lot with ensuring consistent output is being able to use existing slide templates within the MCP to generate new decks.Is there any plan to add this capability to the Figma MCP?

To reduce component weight, my design system team has been exploring using variable modes to toggle between different “variants” of a component, rather than just using variants. The benefit of this is that for these “style” specific properties, where just styles are changed like fill and stroke, using modes significantly reduces the weight of a component in the system. In this example I use a Badge component, and variables to change between the colors of the badge.However, my component code still has a “color” prop. Because I don’t have a color prop on my Figma component, but rather a “BadgeColor” mode that controls this property, is there a way in which CodeConnect can still map this to the correct code property? Currently it doesn’t seem like CodeConnect can read anything that is not a property. Realistically all I need is the CodeConnect to be able to read the string value of the mode, and map that to the actual code prop.

I was writing an interaction annotation for a screen that has the same pop ups as other screen so wanted to tell our devs that they can see the pop ups in this other section and redirect them back and forward to the pop ups.

I got the issue that I could not extend the column span of a layer if it stands at the end of row in Grid.I understand that a layer’s colspan cannot exceed the maximum number of cols, but it should have been automatically wrapped to the next line when the colspan number is still valid.Can you help to investigate this? I have found a workaround (at the end of each video), but it is time-consuming.

When exporting variant names, the file name becomes a combination of all the variant properties. There is no way to control the variant export name, which is especially difficult for developer hand-off. In this example, I have a back icon variant group (Named “Back”) containing both an Apple and an Android variant of the back icon. If I then go to export the Apple variant as an SVG, The variant export name then defaults to “OS Type=Apple.svg” It would be even worse if I had multiple properties. For example, having two more properties could result in a variant name export as “OS Type=Apple, Direction=Left, Style=Line.svg” This is a very poor naming convention, especially for icons. What I would like to have is the ability to control the name given to each variant export. In the above example, I would like the Apple icon to export as the name “back.ios.svg” and the Android icon to export as “back.android.svg”. This way, our developers can export assets as needed directly from Figma wi

Hello!I was going through our team files today, and organizing some that we shared with other vendors. I realized for one of the projects, we needed a ‘draft’ page for our team to ideate and brainstorm there, but didn’t want the vendor to actually see the WIP.I was wondering why isn’t there a page-level permission for viewers? This way I can hide / lock the ‘playground’ or draft page within a file from non-designers!