Share Your Thoughts

Hey there! I was also wondering if it is somehow possible to include also the layer of variant controls to be exposed or hid! I often have cases where I need to nest base components e.g. an icon wrapper providing me with the ability to select certain sizes, or color overrides and boolean props of an icon. I am now able to expose all of those or none, but I can’t restrict the users to only be able to select just some of those. What do you think about it?

 Pretty excited about the new layout grid option, but it would be cool to adjust columns/rows count on component instance. That way we can come up with flexible placeholder components for table and form rows, where we have baseline component set up, and by changing, let’s say columns count on such component instance - add or remove nested components, swap them with other basic components, such as text, input, label, and span them to the desired amount

I am using Figma from almost 2 years. It’s a great tool. Previously I was using Windows 10 yet recently switched to Linux(Ubuntu). Figma doesn’t have any official release for Linux. There are some Unofficial desktop versions but they are “BUGGY”. I request you guys to release an official Figma desktop app for Linux.

Hi! First of all-- congratulations on the release of CMS! I’m already super excited to create stuff with it and I’ve been playing around with it this morning. Hereby my humble feature requests for the future of CMS!Categories and tags with separate pages for their content. Search and date picker (for events) functionality. I would love to see component swapping supported inside CMS, so that I can pick a different component per CMS article if I want to highlight it on my list with a special component for example. (A feature like this would be ~ incredibly ~ powerful.) Or/and, the ability to change page variables in a CMS item, so you can for example change the colors of the page based on the variables set in the item. The ability to connect CMS fields to the SEO, so you can attach a meta description and social sharing image to each CMS article. The ability to hide CMS items from lists but still have them in your database and viewable by link. The ability to attach embeds (or iframe’s) i

You know how sometimes you feel like having a copy of a screen in another file (or page), and would like to have it be updated automatically, but it feels overkill to create a main component out of that screen? If you just copy and paste it (for example for creating a prototype in a separate Page without messing your original screens), it’s pretty much instantly out of date. You also know how you can embed Figma files, frames or prototypes in any website, even integrating in other services like Jira and Dropbox with the Live Embed Kit. It works AMAZING, it shows even up-to-date designs, and you’re simply copy-pasting a link, without the overengineering of extra components. What if this would work within Figma itself?? Check this out: Would this be useful for anyone else? We for example would like to have an example of “usage” of each component in the Components Library, which is usually a screen taken from a variety of other files. But they invariably get out of date super soo

We work in a large company with over 100k employees and have very strict rules on how to share content with clients. What we are missing are advanced sharing options for “only-view”. Sometimes, we want to share content as a ‘view-only link’ with the client to receive comments and feedback directly on the artboards. Other times, we want to share as a ‘view-only link’ but without the possibility for viewers to leave comments. This crucial option is currently unavailable for us, and it would be great if this feature could be added to the sharing options. Thanks! 👍

Hi Figma Team,I am writing to suggest adding Indonesian (Bahasa Indonesia) as one of the supported interface languages in Figma.Indonesia has a rapidly growing design community, with thousands of UI/UX designers, students, and professionals relying on Figma daily. Design and digital arts (such as DKV - Visual Communication Design) are now widely taught across vocational schools and universities, where UI/UX design is a core part of the curriculum.With a population of over 270 million people and a booming tech ecosystem, providing Indonesian language support would significantly reduce the barrier to entry for local students, educators, and emerging talent. This small change could have a massive impact on empowering the next generation of Indonesian creators and integrating them into the global design industry.We would love to see Bahasa Indonesia supported in Figma! Thank you for your hard work and for continuously listening to the community.Best regards,

Sometimes when I am working on a specific frame I accidentally click the Figma make sparkle icon and it brings up the chat as a popup and there is no way to click out of this unless you click out of the frame (it is extremely difficult because I use sections to group my frames)

What do you think about having a horizontal scroll on the layers panel? I can’t see the name of the layers and usually widen the panel to be able to see, but since I use a 13", this makes the canvas smaller.

Hi Figma Team,I am a UI/UX designer based in Chongqing, China, and a dedicated Figma user. I am writing to share some feedback regarding the component workflow, specifically concerning icon replacement.The Current Challenge:For example, when I create a button component containing an icon, replacing that icon requires me to first set up an entire icon library, and then swap the instance from that library. While functional, this process adds unnecessary friction and steps to a very common task.My Suggestion:I suggest keeping the existing swap method, but adding an alternative: allowing users to directly paste an external SVG (e.g., from the clipboard) into a component instance to replace the icon. This would significantly streamline the workflow and save designers valuable time.I believe this improvement would greatly enhance the user experience for many designers. I’d be happy to provide more context or a quick screen recording if needed. Thank you for your time and for continuously imp

I’ve got our company’s internal design system packages published into our private NPM registry. But in doing so, I found (after I published) I needed to modify the packages for consumption by figma make. Figma’s NPM private registry would not allow me to unpublish or overwrite the package versions once I published them.This is causing a problem in Figma Make because users are able to select old, incorrect versions of the packages when installing. I want to prevent this by being able to unpublish or delete packages from the registry, but I’m unable to do it.We are experimenting with the best way to handle this for figma make that is easiest for our figma users--and would like to be able to hit a hard reset at some point as we may completely change strategies. Right now, we have 50 or so unbundled packages in figma make. In the future, we may want to bundle those into a single versioned package for easier consumption.To summarize, here is a list of figma make NPM registry-related feature

 I ran into a font issue while working with MCP use_figma and wanted to share it here. I have a font installed on my system (Pretendard) that works perfectly fine in the Figma UI — it shows up as "Installed by you" in the font picker. However, it's completely invisible to the Plugin API when running through MCP use_figma. listAvailableFontsAsync() returns around 7,600 fonts, but none of them are locally installed ones. It seems to only return Google Fonts.loadFontAsync() also fails, and trying to appendChild a component instance that contains text using the font throws a font load error — even into a non-auto-layout frame. Steps to Reproduce 1. Install a local font on your system (I tried both ~/Library/Fonts/ and /Library/Fonts/ on macOS) 2. Confirm the font shows up normally in the Figma UI 3. Run the following via MCP use_figma: const fonts = await figma.listAvailableFontsAsync(); const result = fonts.filter(f => f.fontName.family === "Pretendard"); return result.length; // 0 awa

Hi,The addition of annotations and measurements to Design mode is such a great decision.However this is rendered almost useless if the annotations and measurements can’t be made visible to View Seat users.Often annotations are used for communication with a range of stakeholders, not just designers and developers. It’s not viable to upgrade every stakeholder to a Full or Dev seat to engage with this content.

Seems you can only add numbers or strings to text layers. It would be great if you could output a color value as text. It’d be really useful for setting up a style guide template that can be updated to different themes.

Right now, it's impossible to left-align stacked text layers with different font sizes inside Auto Layout.Because Figma aligns to the text bounding box instead of the actual glyph bounds, font sidebearings create an awkward visual gap. For instance, if you place a heading above some body, the stem of the headline won't line up with the left margin of the body text. It works for letters like T and A, but not for letters with a flat vertical stem like L and B. See attached screenshot below.You can't manually nudge text layers inside Auto Layout. Negative padding shifts the whole container, not individual layers. Community plugins like “Text Visual Alignment” don’t work with auto layout.Suggested solution:Add horizontal trim to type settings (right next to vertical trim) that crops the sidebearings to the outer edge of the glyph bounds.This would be a massive improvement to type in Figma!

Hello,some feedback from my side regarding Folders, I like the options of a nestable folder, but I find it hard to navigate to the files I’m looking for. The folders are named, but the file thumbnails that were visible with Projects were a huge readability feature that I’m really missing now.I was searching for it in settings, but couldn’t find a way to set it. I actually added a description to a folder, but did not actually see not one place that the description was shown? This part is especially confusing.If I could make an improvement suggestion to a current implementation it would be to have a setting to show or not to show some folder contents thumbnails, similar to the previous implementation.Fingers crossed this can be done!

Color variable aliases were recently given the ability to define a new transparency value without detaching the actual color from the source variable. However, only the opacity can be set and even that’s only if the source color is solid, instead of allowing existing opacities to be offset.It would be really cool if that system could be extended to also allow modifying the other axes, not just the transparency. Since you can’t define a color with a hue and saturation but no lightness, adding this would also ripple out to the opacity by allowing offsets to the existing color’s opacity, instead of what currently happens where if the source is not solid, the feature gets disabled altogether.The use case for this is absolutely massive, letting you far more deeply align your color palette to a single source of truth. It strongly fits the ideals expressed by the recent “Control opacity at scale” feature. It further reaffirms the vision that Figma can be the gold standard for creating actuall

It would be useful if Figma supported Force Click on MacBook trackpads as an alternative to double-clicking.For example, when working with components, layers, or other interactive elements:Regular click → Select the object Force Click → Perform a double-click actionThis would make better use of the pressure-sensitive input available on MacBook trackpads and could be especially useful for users who prefer trackpad-based workflows.

A few years ago there was a fix - The icon on the instance inherit color override, imposed by main component, when swaping icon or changing variant. Great!but… Problem If I modify the icon color on the main component - change color style or manually pick new one, doesn’t matter. The instance with swapped icon doesn’t notice the change! Steps to reproduce:Place an instance Swap the icon on instance Change variant's (main component) icon color Instance's icon color will remain not updatedNote: Of course, all layers properly named to keep the naming integrity. The example: Current, far from being perfect, workaround:If you change an instance to a different variant and change it back, the color will update. Obviously, a lot of effort when you have 15k instances of the modified badge. Use unique variable (semantic). Modify value but don’t touch the name! Sounds nice but be real, semantic naming for each element is an overkill for 80% of the products. Hated but still working - color overlay

Figma’s file browser always resets the sorting to Last modified, even after I select Alphabetical. This happens when I refresh the page, reopen Figma, or navigate between folders.This makes it difficult to create and maintain an intentional folder structure. For example, our folders are numbered to communicate a clear hierarchy:01 Websites02 Campaigns03 Pitch decks04 BrainstormsThis structure only works when the folders are displayed alphabetically. When Figma automatically switches back to “Last modified,” the order changes whenever somebody edits something, and the carefully designed structure is lost.Please either: Remember the user’s most recently selected sorting option, or Add a setting that lets users choose a default sorting method. Ideally, the preference could be saved globally or individually for each folder, since different contexts may benefit from different sorting methods.

Summary: Allow edits to your local dictionary. Details: You can accidentally add a misspelled word to your local dictionary in Figma, but they don't give you as the user or their support / engineering team to remove it. That misspelled word will just never be spelled checked for you in your added misspelling again. Our engineering team has confirmed that it's not currently possible to remove words that have been added to your local dictionary. They have also confirmed that it's not yet on the road map but the team may address it in a quality week. Help article content: "Once a word has been added to your dictionary, it cannot be removed." is why I'm reaching out for help to get it removed.

Walnuts are a popular dry fruit for people who want to include nutritious foods in their everyday diet. Premium walnuts are appreciated for their rich taste, crunchy texture, and natural nutritional value. They can be enjoyed on their own or added to breakfast bowls, salads, smoothies, desserts, and homemade recipes.When choosing premium walnuts, look for fresh kernels, a clean appearance, pleasant aroma, and good texture. Proper storage in an airtight container can help maintain their freshness for longer.For those searching for healthy walnuts or quality dry fruits, walnuts can be a convenient addition to a balanced eating routine. They are easy to carry and can make a simple snack at home, work, or while travelling.If you plan to buy walnuts online, consider factors such as freshness, packaging, sourcing, and overall product quality. A reliable dry-fruit brand can help provide properly packed walnuts suitable for everyday consumption.Frequently Asked Questions1. What are premium wal

It is impossible to annotate a parent frame that has multiple frames in Figma. If an auto-layout frame is made up of 3 nested frames, we can press “Y” and annotate only the nested frames. We can’t click on the parent frame to annotate the entire frame. See attached screen recording for reference.Annotations are an important feature for the dev mode that Figma charges a bomb for. This simple annoyance ruins the user experience. Does anyone know an easy way to annotate the parent frame?

Can we allow Connected folder to have a sub-folder? Perhaps not 10 levels of nested folder. We can limit it to 1 or 2 levels should be good enough.Thanks!

While establishing local variables for a dashboard with large-scale numbers, I’m finding that the value field does not support “,” (commas) as a character. This makes numbers beyond 3 digits much harder to read at a glance. It also breaks stylistic choices for typographic reasons. One solution that comes to mind is to have a global style mode for whether commas are auto-placed in numeric strings, either at the local variable stage for numbers or in type-setting options. This would reduce work on the user’s end for having to manually place every comma, and also ensure consistency from a calculation standpoint (so that Figma has an accurate number to reference in equations).