Share Your Thoughts

Figma's menu corner radius is too big -- 14pxWindows default menu corner radius is 8px (logical resolution)macOS is 9px (logical resolution). When @2x scaled, it actually appears as 18px in the screenshot

Please add it

It would be very useful to have the ability to embed interactive prototypes made in Figma into FigJam, the same way we can do it on websites. This would help when hosting review sessions and gather additional feedback, without having to send links all over the place.

Hello, It would be more than interesting to be able to create variable at a component scope. And of course instance to inherit those variables. Why ? it would be a good way to organize variables. One file can have a lot of different components and subcomponents = a lot of variables. it would give us the possibility to ease prototype creation by preparing upfront variables in components library. it is a good way to get rid of variants. I mean variants are nice but variables are far better :). it would give the possibility to create different set of variables corresponding to different state of the components faster.

With UI3, the font weight of the Figma UI is thinner than it used to be, which makes it less legible. This is particularly bad when reading lengthy comments in my files. As with all body text, I would expect a regular weight, at least in this context. Is there a way to change that in the future?

FigJam seeems to only have these shortcuts: But these are a defined size, what if you want to increase or decrease to the size you want? Like maybe option + Command + > Miro has this, most other apps that have text input also have this (notepad, google sheets, etc…).

Does anyone know of a way to get hanging indents within one block of plain text? So that when a line of text goes beyond the right margin, it’s indented below rather than starting on the left margin again? Kind of like what you’d find on a works cited page of a paper, or in a line of poetry that runs past the margin. And for clarity, I am not talking about lists, bulletpoints, etc. – I am referring to plain/paragraph text

Hello! I ran into a problem that I could not find in your help. There is a Status Annotation plugin, it is very well for work’s control. I make a design for a client, and he’s could control the process with this plugin. But he’s a manager, not a designer. The client usually acts as a viewer, not an editor. This is done so that he cannot spoil anything in the design. But the viewers doesn’t have access to the plugin. Plugins can only be used by editors. Could you make plugins available for viewers? It will be so usefull. Thanks

Would it be possible for the pdf format to come out like Word, i.e. that the text is legible and doesn't come out like an image. This would improve accessibility and mean that cover letters and CVs could be read by ATS recruitment software.

You can embed YT videos into Figma Slides, but appears to lack Vimeo support. Also, we can’t change the Embed settings (turning off suggested videos, etc.) Would love support for these!

The Pages toolbar, wherein you select which page is active, now has way too much space between pages. It’s plausible to click near a page, and get nowhere. In other words, the gutter spacing between rows is too large.

As demonstrated in the video, I am unable to use “select matching layer” within the same frame.

 It would be really helpful if there were a way to view the creation date of a new project when it's first created in Figma. 

As I am publishing library quite often - I need to do it quickly. The current flow is slowing down my process. I need to go to all libraries (it shows Updates by default) I need to switch to This file and then hit the teeny-tiny button Publish. It is way too hidden for a such frequntly-used action. Make it accessible from main UI or add a shortcut. 

We have a range of team members using Figma, but admin users typically don’t log in regularly or use it day-to-day. As a result, when someone requests edit access, there's often little oversight or context around what approving means for the business.One key issue is that granting edit access automatically assigns a paid editor seat — and this cost gets added to our invoice immediately. Unfortunately, not all team members are aware of this. It’s easy to click “approve” without realising the financial implications.From what I’ve read on this forum, there’s no logical solution to this yet except to request a refund. This is giving ‘dark pattern’ vibes.We have people on the team who should never have Figma access such as executives wanting to modify designs.Suggestions: Add a clear warning or confirmation step when approving edit access that explains a paid seat will be created and billed immediately. Introduce a process for reviewing edit access regularly to ensure seats are still requ

Why I need it.Our designers create full specifications for components in our design system libraries and use dev mode annotations for our front end dev’s. As a Figma library builder, I use those same specifications to create the actual components for our Figma libraries. I copy sections from the design spec file pages and paste them into a library page to use them to create the library components.The problem is the sections I copy into my component page are loaded with dev mode annotations that I have to delete (no, I don’t want to just turn the view off) and I have to do that one annotation at a time.Can you please add a Delete all annotations command? Obviously a warning would be appropriate, but it would save me some time.Thanks!Ben

Please add YAML to FigJam code blocks. Others languages are also welcome in addition to this.

I use the Scale options a lot and 9 out of 10 times I know exactly what size in width or height I want to scale to. I also use Tabs a lot to navigate through options whenever possible.In the new UI when I click K and open the Scale options the first focus is on the 1x multiplayer and the Tab goes through the alignment box, it takes 20 tabs to go from the multiplayer 1x option to the Width input.In the old UI, I click K to open the Scale properties, press Tab once and enter my Width…I believe that most users will agree that the Width and Height inputs should come next after 1x in the tab order. (I am not even sure what that alignment box is supposed to do exactly , I have never used it.)  

When working with multiple shapes, you currently cannot edit the anchor points of multiple shapes at once whether they are unionized or not. At my studio, we are working on incredibly complex UI for vehicles, and products, and this feature would be much appreciated, and would greatly increase the speed of our workflow.

Hello, I would like to propose a new feature that will reduce the work of interface design by half or more, and Figma is already almost there.Currently we have to make different size versions (desktop, tablet and mobile) so that developers can view them. With the variables mode I can edit the screen sizes just by changing the global variable, but my developers do not have this button available. It would be wonderful for everyone if this were possible.  

If you have a component with many different variants, it would be good to have a warning before someone accidentally changes the content within the component rather than in the variants. This is inspired by the warning that happened when detaching an instance when you had FigPals.

I often have to use colors outside of Figma. At the moment, if those colors are variables, I have to detach it to select and copy the hex code and re-apply the variable.I think it would be a nice feature to be able to copy the color of that element without having to detach and re-attach the variable. 

Hi everyone 👋I'm a daily Figma user and really appreciate how flexible and powerful Auto Layout has become.That said, there are still a few small but recurring pain points in my workflow that I believe many other users may also be experiencing — especially when it comes to Auto Layout default settings.Currently, certain Auto Layout options like Exclude strokes and Canvas stacking are always turned on or off by default. While this might suit some use cases, it can feel counterintuitive or inefficient in others.1. Exclude strokes — A repeated manual step that can lead to dev/design misalignmentEvery time I apply Auto Layout, I find myself manually disabling "Include strokes."In web development environments, it's common to build layouts using border for visual separation — not stroke.Because of this, including strokes in padding calculations can often result in misaligned spacing between design and front-end implementation.If designers could set "Exclude strokes" as a default, it would h

This suggestion is the result of a random gripe in Figjam, but i don’t always like using stickies in figjam as they are big and bulky and have limited style options. i love the AI sorting features for things like card sorting, but this is only possible with stickies.I’d much prefer to use the rectangles and other shapes to group things like fields in a complex profile. they’re smaller and less annoying to resize and rearrange. this makes it easier to export snapshots to send to stakeholders, as let’s be real - many normal business folks just don’t understand how to navigate horizontal scrolling or infinite canvases. the sorting works great, just don’t force sticky notes. or give us more freedom to style and resize stickies. The rectangles on the left are smaller and easier to style than the stickies.  

It will be good to have a feature to notify a content designer who intends to change a copy in an instance that it will be better if he/she makes the change directly in the component. It will be also good if this notification can take them to the component directly where they will need to make the copy change. This notification will prevent a lot of overrides that happens if multiple people work in the same file and have different skill sets, or are not aware of where the components are “buried” :)