Share Your Thoughts

When inserting a component, I want to prioritize inserting a local component rather than one from another library.For example, if I want to use a TextInput component, I want the local version. That’s why I filter by “Created in this file”:The problem is that this preference is not saved. So whenever I want to insert again, I have to:open the insert dialog type “TextInput” grab the mouse open the dropdown select “Created in this file”This gets annoying when wanting to insert multiple components, or multiple instances of the same component. If not for that dropdown selection, I could do it with the keyboard only. Now I have to switch from keyboard to mouse and sometimes keyboard again.You might ask “Why add an external library if you’re not going to use its components?”. Well a library can have hundreds of components and you only want to use a subset in this file. But for some components like a TextInput, you want the local version, not the library one.Anyway, I feel like saving the prev

Hi there. I’m loving the Chrome Extension so far, but would love it if there was some functionality to refine a selection to copy, similar to what the https://paper.design Chrome extension does to “fine tune the target”. This makes it easier to capture exactly what I want rather than capture a container element with the element inside it then extract it in Figma. I know doing this is not a big deal but the change would be a nice quality of life improvement.

Figma, in my humble opinion, started as a design tool that rivaled Sketch. It eventually took over the market, and now almost everyone has abandoned Sketch. Figma has become the most widely used product design tool.What has happened since then, however, seems to be a lot of sidestepping and creating offshoots that move away from what the product was originally intended for.FigJam — why? Users are already using Miro and other tools that do this better. FigJam feels oversimplified, and in the end, I just use Figma itself to run workshops. Assuming that people who don't use Figma are going to come in and adopt FigJam is a mistake. Most people who don't use Figma don't enjoy using it.Slides — why? Most businesses are still using PowerPoint. It doesn't matter how much you push Figma Slides; it almost always ends up back in PowerPoint. This feels like a major departure from what Figma is supposed to be.Coding? What in the world? There are already so many tools out there that write code. Why

Just going to complain because who ever is behind the wheel at Figma, from a product experience point of view, is not thinking about good UX and is instead just making things harder for users. You used to be able to open a plug-in, then save it for easy access. There are many versions of the same plugins, even paid ones and I would like to be able to quickly jump to those especially after trying a few that aren't what I need. Instead I have click about 2 to 3 times, then enter text to search for it, then use it, then wonder where it went or even have a hard time finding it again. Now the ones I paid for are hard to find too - these are ones Im paying for and should be easily accessible. Please, make it easier to jump to a list of plugins users use often or have paid for 

Currently, corners can only be rounded at whatever size you set. However, it would be great if you could set different styles of corners such as inverted rounded or chamfer as you can in Illustrator. The goal would be to create a style like the image below: Does anyone use a plugin to achieve this effect?

I can’t use the site design feature without clicking a “get started” button with fine print that does not clearly state the breadth of the privacies waived. So much for free.

To design for responsive web, we need the ability to use layout grids and percentages for widths of frames. For example: width=50%, or width=6 columns of the defined layout

Frames should support a max width defined as a percentage of their parent frame.I run into the same scenario repeatedly: I have several frames in a composition set to hug their contents, so the parent frame wraps them once they grow past its width. The problem is:When a frame is set to hug, max width only accepts px values, which isn't responsive. If I switch it to fill, the parent container never wraps it, because the frame no longer has an intrinsic width.So the min and max width/height on auto layout children only accept pixel values, this makes them break down in responsive compositions, since a px cap doesn't adapt when the parent resizes.The suggestion here is allowing percentages making these constraints behave the way they do in CSS, so you can use values like max-width: 100% or min-width: 50%Today the only workarounds are hardcoded px values or restructuring layers, both of which fall apart as soon as the composition needs to respond to different widths.

Right now, when a parent component changes its properties or variants, the Slot inside it keeps its content and ignores those changes.While I love using slots for the flexibility to add custom elements, there are many times when I also need that slot to automatically adapt to the active variant's styling or layout. It would be amazing to have an option or a toggle that lets Slot behavior sync with variant changes  

When using the AI image generation/editing feature, the "Cancel" operation is bound to the ESC key. Since I often perform other operations (like switching windows, using shortcuts for other tasks) while waiting for or working on edits, I frequently press ESC accidentally. This immediately cancels the ongoing process, interrupts my workflow, and even causes me to lose unsaved progress. It’s very frustrating to restart the entire generation/editing process repeatedly due to unintended key presses. I hope the team can optimize this interaction: 1. Remove the ESC key binding for Cancel, or 2. Add a confirmation prompt before canceling the task, or 3. Change the shortcut to a less commonly used key combination to avoid accidental triggers. Thank you for your attention!

I use Sections as an organizing structure for all the prototyped pages in my project. When I am prototyping and creating links, seeing all the Section names is really cumbersome because they make the list long, and I will never want to link to them.It would be nice to have an option to exclude them from the list of linkable 'pages' — similar to constraints for variables.

Suppose I own a file but I want to change/hand over the file to my teammate which I can not do by myself. The other teammate who is going to access has difficulty for those files after removing the email id from which the file has been created. The idea is that the actual file owner should have access/option to change the ownership of the file so that it can be easily accessible to other teammates. Or there can be multiple owners of the file (Max 2-3). Please have a look at the statement mentioned. Thank you!

ProblemCurrently, Figma does not allow designers to create a reusable style for link-like or inline action text.Text Styles in Figma mainly control typography properties such as: Font family Size Line height Letter spacing However, common link or inline action properties like: Text color Font weight variation Underline / decoration intent cannot be defined as a reusable style and applied consistently across files.As a result, designers either: Manually restyle text every time, or Convert text into a component, which is not ideal for inline usage inside paragraphs or labels. ExampleA typical UI pattern:“By continuing, you agree to the Terms & Conditions.”Here, “Terms & Conditions” is an inline text link that needs: A specific color token Slightly different font weight Optional underline or visual emphasis Today, this styling has to be applied manually each time, which makes consistency difficult in large design systems.Suggested ImprovementIntroduce a way to crea

Currently check designs suggests the wrong tokens even though I have explicit names for tokens.For example, it tells me I’m using a hardcoded value for a horizontal or vertical gap, fine, but it suggests a border radius token or border width token. Meanwhile, I have tokens called “spacing” that could be suggested.Same thing for corner radius adjustments, it suggests border widths even though I have border radius tokens.Is there a way to configure this if we can’t get the “smart” version yet?Thanks ! :) ps: the feature is really nice by the way and already saves a ton of time ! 

Khi tôi gõ  >= hoặc =<, tôi rất kỳ vọng Figma có thể tự động chuyển nó thành ≥ và ≤

I work a lot with dashboards a lot which means variable height cards in various configurations. I would like the figma grid to support a “Masonry” layout for grids where the horizontal and vertical gaps are kept consistent.Masonry grid exampleCurrently it’s only possible to have a grid layout that wastes a lot of vertical space like this.Regular gridI’m aware this can be achieved with AL but the responsive layouts are a pain.Please 🙏

It would be really really nice if a series of parameters could be declared when automatically renaming layers: lowercase, uppercase, separators, etc. It could be something similar to the bulk layer renaming feature, but with AI. Use case example: I have a project which has all layer names in lowercase and separated with hyphens, I would want the new layer names to have the same layer syntax when renaming them with AI.

It’s 2026 and Figma still doesn’t have a proper table component feature nor negative margins, shadows & gradients as variable.  

Creating buttons in Figma is fantastic, but when working with multi-layered components that have custom corner details, resizing often causes distortion even if saved as components. This makes flexible scaling challenging and affects design consistency. Don’t you think it’s about time to add native 9-slice scaling support? It would significantly improve precision and workflow. Please consider this feature for future updates.

I want to recommend an improvement to the way Ai uses library (or rather does not use them currently).By default AI cannot see what libraries you have within the assets panel. When I requested use X library It did ask me to add them to assets even though they were already active and available to meAfter a bit of back and forth it then revealed to me the + button under the chat to enable libraries.It make me think this is very unintuitive process. I would expect the AI to simple be able to see the libraries added already to assets and why the need for this (duplicate) step

It’s very inconvenient and slows things down when you add an additional fill with 20% opacity. You have to go into the opacity settings every time and set it to 100%.

I’ts so freaking annoying that you can’t collapse the assets panel! 

Please consider addressing the following two common issues with annotations:1. Annotations can obscure the design. When a design frame is selected, it should be brought to the front instead of being covered by unrelated annotations.2. Annotations do not support copy and paste. Users have to recreate and re-enter them manually, which is very inefficient.These are very common use cases, and I hope Figma can address them as soon as possible. 

Hey everyone,This has been driving me (and apparently hundreds of others) crazy since 2021: there is STILL no native way to properly move or duplicate an entire page from one Figma file to another.Copy-paste or “Select All” destroys page background/grid/rulers, breaks prototypes, loses comments, turns library styles into local duplicates, and forgets locked/hidden layers. Duplicating the whole file then deleting pages is the only “workaround” — but it’s a nightmare with 50+ page files or design systems.I’m a fellow designer who’s fed up and seriously considering building a free Figma plugin called PagePort that would let you:Export any page (or batch multiple pages) with 100% fidelity (layers, auto-layout, constraints, page props, prototypes where possible) Import into any other open file in one click Choose Move (delete from source) or Copy Smart remapping for styles/variables/libraries + basic prototype reconnection Progress bar for large pagesWould this solve the problem for you? Wh

Obvious benefit would be to allow for things like specific values related to loading to be passed through on the code side...