Share Your Thoughts

I lost a key edit to a file, undo wouldn’t recover it. I found it in the version history.Hard to find Couldn’t restore the edit. I found it, but I couldn’t copy and paste it. I hit recover, but it would glitch up and go back to the other edit when I closed it.End result, I had to finish a rush item by cropping a screenshot, not by restoring it in Figma, even though I could see the edit I wanted to restore and tried for 15 minutes.Serious concerns about stability of product after seeing this.

We need a side-by-side visibility!The switch from a floating/movable Variables modal to a full-screen tab has hurt my workflow.I need to see the canvas and variables side by side — to check a token change against the design, compare values across modes, catch mismatches before they ship.Switching back and forth constantly is tedious! This isn't just slower — it's causing errors. Editing without seeing the canvas means working from memory instead of visual confirmation, which leads to picking the wrong step in a scale or missing something like a contrast issue.Please! make it float again. 

Changing the Variables panel to be a tab along the side that takes over the view instead of a panel I can move around has impacted by design flow. I would often have the variables panel open side-by-side to my designs so I can view/add/update variables and build design simultaneously. Now I have to flip back and forth causing frustration and slower process.

When using Find & Replace with Arabic text, Figma always navigates to the first matching result starting from the left side of the canvas.For RTL languages such as Arabic, I’d expect the navigation order to follow the reading direction and start from the right side instead.This becomes especially noticeable in flows where screens are arranged from right to left, as Find & Replace jumps to a screen on the opposite end of the flow first.It would be helpful if result navigation respected the text or document direction for RTL languages.

The recent figma autolayout update has brought up conflicting emotions. From one point it’s great that the autolayout would work closer to code, but on the other hand for teams that do more complex projects than Web UI, this creates a loooot of issues. 3 things in particular, that I know for sure, will break what we've been using in case of complex layouts:"Padding now always gets the room it needs" - Often when necessary, I relied on the fact that you can set auto-layout frame size to 0 and add paddings inside to allow precise position of elements without affecting the size and position parent and sibling frames. Now that won't be possible. ⁠"Inside strokes counting in autolayout" - again pretty sure this will break layouts where inside stroke was used. ⁠"Stacks with gap set to auto no longer overlap" - A lot of cases it's better to have parent in the desired size than have the parent rely on the children. Then we will get uneven distances and paddings in some cases. All of this would

I’ve been thinking about how much difference good file organization can make when working on a design project.For example, how do you usually organize your Figma files and pages? Do you have a specific naming system for layers, components, and sections, or do you keep things more flexible?I’d be interested to hear what organization habits other designers have found useful, especially when multiple people need to work on the same file.

Love what you've built with Motion, using it almost every day.One thing that slows me down is the lack of native audio support. Having to render and add audio in a separate tool gets cumbersome, especially when working in bulk.Would love to see that integrated down the road! Also, any plans for HTML exports?I've looked at plugins but they feel a bit pricey and not very intuitive. Keep up the great work! Peace ✌

Hey everyone. I would like you to consider the text animation feature in Figma Motion. What I mean by text animation is animating text either word by word, or character by character, like the kind of animation we see in Saas promo videos. With other effects to the text like gradient color change that moves along the text reveal. That would be really cool :))

Hello! I noticed that in the Figma article What is Human Computer Interaction?, the author writes:Dialogue. Use clear and concise language to communicate task completion, like  “Purchase Confirmed” pop-ups after completing an online order. On Shneiderman’s website, he writes: Design dialogs to yield closure.Sequences of actions should be organized into groups with a beginning, middle, and end. Informative feedback at the completion of a group of actions gives users the satisfaction of accomplishment, a sense of relief, a signal to drop contingency plans from their minds, and an indicator to prepare for the next group of actions. For example, e-commerce websites move users from selecting products to the checkout, ending with a clear confirmation page that completes the transaction. I understand that they are variations of the same word but I would argue that in this context, it is important to use dialog because Schneiderman is referring to the importance of the graphical interface  (li

Hi Figma Team,I’d like to request the ability to temporarily hide the selection bounding box and handles of an active object without deselecting it.The Problem: As a UI design tool, our canvases are filled with rectangular containers and elements. When fine-tuning pixel-sensitive details—such as adjusting complex borders or multiple effects on rectangles—the selection bounding box directly covers the edges and working area, making it very difficult to accurately judge visual contrast. Industry Standard: Other industry-standard tools like Adobe Illustrator and Photoshop already solve this by letting users hide bounding boxes (e.g., Hide Bounding Box / Show Transform Controls). Having a similar toggle or shortcut in Figma would greatly improve high-precision UI work. The Solution: A quick shortcut or option to hide the transform handles/box on the canvas while the layer remains selected.Thank you for your incredible work on Figma!Best regards,Aleix

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. :(  

Every time I exit Figma and come back, the previously selected sort order is lost, and it defaults to "Last modified" – "Newest first". Previously, the selected sorting option was always preserved.

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