Share Your Thoughts

Figma’s current image crop is non-destructive, which is useful, but I’d love to have an option to permanently delete the pixels outside the crop.For example, add a “Delete Cropped Pixels” option when cropping an image.The workflow could be: Crop the image. Choose Delete Cropped Pixels. Everything outside the crop is permanently removed. The image can no longer be uncropped or moved to reveal the deleted areas. Normal non-destructive cropping should still remain available.This would be especially useful when working with large images because it could help reduce unnecessary image data and keep Figma files lighter.Photoshop already has a similar Delete Cropped Pixels option, and having the same choice in Figma would make image editing much more flexible.

I’d like Figma’s Slack integration to post a notification when someone creates a named version history entry in a file.the message including the title and description of version history entry.

I’d find it useful to set an aspect ratio for cells in Grid Auto Layout. For example, I could set the columns to fill the available width and give each cell a 1:1 aspect ratio. Its height would then automatically match its width, even when the grid is resized.

Looking to better understand gradient behavior in Figma.The example below shows a setup for a Skeleton loading layout/animation. The gradient sits above a background layer with a light grey color.skeleton reference I want the gradient to provide a small white highlight wave, animated across the background layer. It has stops of 0%, 24%, 48%, and 100%. Three of the stops are fully transparent (to match the CSS). Even when set to fully transparent (#00000000), a fill color is present in the transitional areas. This should transition from white to transparent.Currently, Figma requires setting the transparent color to match intended visual styling, here requiring setting the transparency to match the background layer. This feels like an unexpected setup step, and clunky.Is this intended? How does this align to CSS?  

I get nervous having edit-access to a Figma file sometimes, especially as an engineer. I don’t want to accidentally make a change to something in the file. It would be great if there was a way to switch myself to a read-only mode (temporarily) to avoid accidentally breaking/changing something. For now, I’ve just been creating a new branch. If I change something on the branch, then I don’t need to worry.

Upon creating ideations with Figma make and publishing it as Figma Site, and sent to end users.The end users must have a facility to add comments to the figma site. 

On the vertical bar on the left (as per screenshot) how can I swap the 'Agent' button to the 'Assets' one so it's under 'File' instead?    

Hi! First, thanks to the Figma team for all the hard work. Now, let’s talk about Figma Slides Templates. To edit the template styles, I have to select a slide first — which feels a bit unintuitive. In Figma, when you click on the canvas without selecting anything, you can access the file’s styles. Can we bring that same concept into Slides?When I open the template selector, I can edit the styles there through a dropdown. Is that really the best or only way to manage styles in Figma Slides? I don’t think so.Colors & Text Styles: I can delete them, but only through a pretty complex interaction — right-click?Layout Grid: How can I set a default grid? Right now, I have to manually add my custom grid to every new slide I create. If we can't set a default, the feature kind of loses its purpose. :(  

Hi guys! I’m also interested in this improvement.

It’s the year 2023, and Figma still doesn’t have native table support. I just spent 30 minutes re-jigging all the “cells” in a four-row, six-column fake table because I had to delete one column, add another, add icons, and then manually re-fit/resize all the cells to get things to align properly. I can either fake a table row with a horizontal autolayout, or fake a table column with a vertical autolayout, but it’s still not a table. I want the ability to create a special frame called a Table, that: has an arbitrary number of columns and rows auto-resizes columns evenly based on content width has one or more Header / footer rows can scroll with overflow content (optional) has optional properties for hover / click states (cell, column or row) has optional properties for alternate-line shading can toggle columns or rows to hide as needed can merge or split cells as needed can set text alignment for a column (center, left, right, or currency / decimal) can set to automatically use monospa

It would be nice when a designer need to share a page in figma file, they can limit access to other pages for the gustes.So guests see only the specific page and can’t navigate to the other page within the Figma file. What do you think? Many thanks

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

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: Responsive Component Swap Based on Container WidthIt would be extremely useful to have a way to automatically switch a component variant or nested component based on the width of its parent frame or container.When designing responsive interfaces, components often need to change significantly between desktop, tablet, and mobile layouts. Auto Layout handles resizing well, but sometimes resizing is not enough — the component itself needs to change.For example: Width > 1200px → Desktop Navigation Width 768–1200px → Tablet Navigation Width < 768px → Mobile Navigation Ideally, we could define breakpoint rules d

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.