Suggest a Feature

One piece of feedback I've consistently run into as a designer is the separation between Figma files and FigJam files. While they're closely connected in the design process, they're treated as completely separate artifacts in the file structure.In practice, many designers use a single file as the source of truth for a project. Research, workshops, journey maps, IA exercises, brainstorming sessions, requirements, explorations, wireframes, design concepts, and final designs are all part of the same workflow. Today, that work often gets fragmented across multiple files, making it harder to find information, maintain context, and keep project history connected.I'd love to see an option where FigJam and Figma coexist within the same file structure. For example, when creating a new page, users could choose between:Design Page (Figma) Whiteboard Page (FigJam)Both page types would live within the same file, similar to how pages already exist today.Benefits could include:A single source of trut

I spend a lot of time undoing the automatic auto layout adjustments that Figma applies in order to maintain the existing layout structure. This is frustrating because I understand how all the resizing parameters work, and I only change the ones I want to change. But in an attempt to help me and retain the current layout, the UI changes parameters that were previously the way I wanted them. So while auto layout still saves me time, it also wastes my time by putting me in a position where I have to go through, layer by layer, undoing the auto-adjustments. (Usually changing a layer’s width or height from “fixed” back to “fill” or “hug”.) I understand some users may actually like this, and it’s hard to please everyone. I would be more than grateful for an option that allows me to disable this automatic behavior.

I find managing template colors really difficult in Slides. I can’t easily organize, re-order, or rename them. I’ve found some ways to hack it but it feels really convoluted trying to provide color options in the templates I’m making. I think Slides is doing a really great job on most fronts and I love the product, but I find myself just using colors from other libraries because managing them within Slides is so confusing.

Hello,I have always been a big fan of your platform, especially because it was one of the few that had not given in to the model of charging subscriptions for standard use.However, it is now no longer possible to create more than three FigJam files, which seems to me like the beginning of changes that may gradually reduce features that were previously free.I have always recommended Figma and would not like to stop. Please do not follow this trend, as this was exactly what set you apart from others.I am Brazilian and used a translator to write this message.

Hi Figma team, Since images in comments launched, teams have used them heavily for visual references and bug reports. There's still no way for plugins or integrations to read or write those images. What we found:- GET /v1/files/:key/comments returns only the text of a comment that has an image. There's no attachment field, including with as_md.- POST /v1/files/:key/comments accepts only message, comment_id and client_meta, so there's no way to attach an image.- The REST API spec (figma/rest-api-spec), FILE_COMMENT webhooks and the Plugin API don't include comment attachments either.- Comment images don't show up in GET /v1/files/:key/images. Why it matters: anyone who moves, archives, exports or syncs comments (to Jira, Linear, Notion, or between files when a design is reorganised) loses every image. Users see comments arrive without the screenshots that gave them meaning. What would help:1. An attachments array on the Comment object, with { id, url, mime_type, width, height }. The URL

Organization would be immensely helpful if we could create folders for our drafts. I want to be able to organize my drafts into different categories (such as UI kits, Ideas, Wireframe kits, iOS, Android, etc…) so I can find files easily. Right now, the drafts page is a huge jumbled mess and I can’t create Team pages for everything. Maybe something as simple as being able to add ‘tags’ to each file, similar to Zeplin.

Feedback 1: since Figma Desktop App version 126.1.2 text styles picker always shows libraries of styles in collapsed state. It’s super annoying, since search doesn’t work until you un-collapse it.Feedback 2: please fix up/down arrow behavior on styles. Example: the text span has style “Body/Emphasized” → I press arrow up expecting it to switch to “Body/Emphasized” → instead Figma selects “Headline/Regular” (the style that just happened to be below the search box). I papercut myself on this multiple times every day for the past couple of months now, at least.Figma’s a great product, I love it, but bugs like these are a big let down for me. I believe basic features like text styles should be dogfooded more to remain best in class.  

Hi, and apologies for posting a new question – it may well have been asked before. To be honest, I can’t be bothered to look it up. Besides, the more questions on a single topic, the better the chances of success.I’m not really sure how or what to write here, so I’ll just set out my ideas and suggestions – things I keep coming back to whilst working in Figma. Feature request: Linked Component StatesIt would be useful to have a simple way to link the states of different component instances.Currently, if several components need to react to the same interaction, this can require variables, multiple actions, conditions, or additional prototype logic.I would like to be able to connect one component instance to another and define how the second component should react when the state of the first one changes.For example:DropdownDefault → Opencould automatically trigger:BackdropHidden → Visibleand:HeaderDefault → Dropdown ActiveThe relationship could work as a simple dependency:When Component A

I want to be able to export designs in PDF for print (CMYK/Hi-resolution) For now, I was using the plugin TinyImage Compressor but it’s no longer free and I don’t understand why Figma can have this option on it’s own. I’d have to pay $456 a year. If Figma has paper sizes, why don’t they have this option… you can’t print quality good quality colors in RGB. I’m going to have to go back to Adobe for print files. Is this happening to anyone else?

Feature Request: Batch Individual Auto LayoutApply Auto Layout to multiple selected items as individual frames rather than grouping them into a single parent frame. Current Format: Pressing Shift + A or selecting "Add Auto Layout" with multiple items selected automatically nests all items into one new Auto Layout frame. Proposed Enhancement: Introduce a modifier key (e.g., Shift + Alt + A) or a toggle in the Auto Layout panel that allows users to "Apply individually." This would wrap each selected layer in its own independent Auto Layout frame simultaneously. Benefits: Massively speeds up workflow: Eliminates the need to manually wrap 10+ items one by one. Maintains Layer Hierarchy: Prevents accidental nesting and unnecessary "Frame 1, Frame 2" group structures. Consistency: Makes it easier to apply uniform padding and alignment settings across different UI elements at once.

In the Figma UI, you can create a color variable that references another color variable (alias) and override its opacity — producing a "composed color" value. This is extremely useful for building semantic color systems where, for example, surface/overlay = palette/neutral/900 at 54% opacity.However, the Plugin API currently does not support writing these composed color values via setValueForMode(). Attempting to do so throws:Uncaught Error: in setValueForMode: Composed color variable values are not supportedMinimal reproduction scriptRun this in the Plugin API console or inside a plugin: // Step 1: Create a variable collectionconst collection = figma.variables.createVariableCollection("Semantic Colors");const modeId = collection.modes[0].modeId;// Step 2: Create palette/neutral/900 — a base colorconst paletteNeutral900 = figma.variables.createVariable("palette/neutral/900", collection, "COLOR");paletteNeutral900.setValueForMode(modeId, { r: 0.07, g: 0.07, b: 0.07 }); // Works fine ✅//

Hi Guys, Recently ive had to create my own figma drag and drop image plugin as i like the simplicity of viewing my images in a folder and be able to just drag straight into a shape. Currently in takes multiple steps.Selecting the shape Clicking the fill colour Selecting Custom Selecting the image gallery icon Then dragging my image into the small little preview then using a zoom feature at the bottom.I know there are alternative ways to handle this, but the current workflow is extremely frustrating. That’s why I created a plugin, see the link below:https://www.figma.com/community/plugin/1684024395230842248/drag-drop-images Another limitation is that you can only run one plugin at a time. Plugins should remain installed and active in the sidebar. If I open my plugin and then switch to another, I lose the drag‑and‑drop image functionality entirely. Drag & Drop Images This should be a standard feature. Dragging and dropping images shouldn’t require so many steps.Fixed Colour Style Pal

When will you finally add Russian to the Figma interface? It’s been more than 5 years since I started using your product, and I’d like to see all the menus translated into Russian. Why can’t you simply create a translation in the same DeepSeek and add a separate option in the menu to select Russian? Constantly having to keep English in your head is, well, honestly not a great pleasure—just like forcing Americans to speak Chinese, even though for some reason it [Chinese] is present in the interface. Finally add Russian. Are you Russophobes or something? Well, then we’ll go to Pixso and work there, since you simply don’t value the Russian community.

Today: As an agency, we’re frequently starting new projects for new clients. We’ve evolved a set of best practices for Figma file organization, per-client design systems, etc. These best practices have been captured in a Starter Project project in Figma. However, to use this Starter Project each designer must duplicate each file in the Starter Project individually and then move them over into a new project. Idea: We’d love to see Figma support duplicating projects in addition to the existing file duplication functionality. This would be a small but noticeable improvement in efficiency for spinning up new client projects.

It would be really helpful to be able to use a variable to set a Type Style’s Letter Case (under the Type Settings meatball menu). It could be a String Variable, and the options would be “As entered”, “Uppercase”, “Lowercase”, “Title case”, and “Small caps”. I personally use modes to switch between different brands, and some brand styles require uppercase while others don’t allow it. This suggestion may be a small feature in the grand scheme, but I wonder if others would also find it useful.

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,

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