Suggest a Feature

There should be a option to add like 2 strokes, like heres an example below:https://imgur.com/a/jjNJWNF

Currently I can only define a variable with some absolute value or referencing it to another variable but I would also like to define it using operations on other variables. for example Total Fee Amount = 100000 Paid Amount = 20000 then Unpaid Amount = Total Fee Amount - Paid Amount

Since Figma has all of information regarding design and layouts. I like to reference @ Figma pages or components (in addition to  multiple references) so that I simply build it accordingly to the specifications within my Cursor. That way, the Claude LLM can produce the necessary code while adhering to the organization of my codebase.

Hi folks! I’ve seen the posts regarding text overrides with nested interactive components but I’m seeing a similar issue with non-interactive components as well. In the example below, I’ve set my text layers to all use the same layer name and have the same hierarchy structure but if I swap one of the nested components it resets everything. Everything works perfectly if each atom component is used individually and not nested in another component though so I’m left 🤔. Any thoughts?

I have a big icon library where every icon is its own component set with 9 variants. I need to add the same properties on all component sets. Bulk editing multiple component sets at the same time would be a huge time saver.

Because Figma only supports pixels, and we often have to translate pixels into other units for Fonts, etc., it would be great to document these conversions in the style’s description and have it show in the inspect panel. The description field is already available for editing in the style settings, so adding its value to the inspect panel would make it much more useful.

I spent a good amount of time searching for mockups that match the ones I’m presenting my work in. The device frames presented by Figma are exactly what I’m looking for. There should be an option to “Export with Device Frame”. The prototyping feature does already has a lot of device mockups with pretty good quality to showcase designs. Does anyone else feel that this would save them a lot of time?

It’d help to add “Scroll Behavior” option for the items in auto layout, which gives the option for Position Sticky either for Top or Left (with offset values) depending on the direction of auto layout (vertical or horizontal). This will make creating tabular / grid layouts with row and column freezes possible… especially when creating feature comparison layouts.

We could use IF, ELSE IF, ELSE statements… Many times in code you may want to do many different things based on different string values For example, I might have three different landing pages based on 3 conditions, and upon button press I might want to say IF “has-users”==0 goto empty landing ELSE IF “has-users”==1 goto landing a ELSE IF “has-users”==2 goto landing b ELSE goto other

I’d like to request a new feature that provides more control over sharing permissions for viewers and Dev Mode users. Current Challenge:In our organization, we have internal employees and external agencies set as viewers, and we also use Dev Mode on an organization plan, where developers are automatically set as viewers as well. However, the sharing permissions for both viewers and Dev Mode users are currently bundled under the same settings. This causes issues because we need different levels of access control: Some viewers should be able to export files.Some viewers should be able to copy and share screen designs.Some viewers should only be able to view without any additional permissions.Feature Request:Could you introduce more refined sharing permissions that allow us to control these settings separately? Specifically, having distinct options for:😎 Viewers who can export files.😎 Viewers who can copy and share designs.😎 Viewers who can only view.😎 Dev Mode users with separate per

I’d like to request a new feature that provides more control over sharing permissions for viewers and Dev Mode users.Current Challenge:In our organization, we have internal employees and external agencies set as viewers, and we also use Dev Mode on an organization plan, where developers are automatically set as viewers as well. However, the sharing permissions for both viewers and Dev Mode users are currently bundled under the same settings.This causes issues because we need different levels of access control:Some viewers should be able to export files. Some viewers should be able to copy and share screen designs. Some viewers should only be able to view without any additional permissions.Feature Request:Could you introduce more refined sharing permissions that allow us to control these settings separately? Specifically, having distinct options for:😎 Viewers who can export files.😎 Viewers who can copy and share designs.😎 Viewers who can only view.😎 Dev Mode users with separate perm

Can Figma create a feature when we click a link in Figma that navigate to the design page, then will appear "Return to Link" like "Return to Instance" in component feature? 

 The User Enter Page Manual helps us navigate any page.  

I like shortcuts, but… Some Figma shortcuts override my keyboard layout shortcuts. For example:“OPT+<” or “OPT+>” to insert quotes like this « ». But in Figma its letter spacing controls. “SHIFT+OPT+<” or “SHIFT+OPT+>” to insert quotes like this „ “. But its line-height.Those shortcuts frustrate me, so I want to disable it. Other ones are quite nice.

Make it possible to download comments in the same way as local versions of files are downloaded, with the ability to also import comments along with a local file, now I transfer all comments from one file to another manually, also between pages in files, this is very inconvenient, and does not simplify the task

While I can link width and height to variables, it can be hard to get complex components to scale correctly using them. Having a scale variable that behaves just like using the K key would make things a lot easier. Unlike using the K key it would need to remember the ‘base’ 1.0 scale of an object.

Hey guys, I’ve created a presentation and I exported to PDF to send it to my client. But all the slides are with rounded corners with a white background. Isn’t there a way of exporting WITHOUT the rounded corners? Thank you!

Would be extremely helpful to have the option to always show min-w and max-w in the sizing panel! Selecting the dropdown takes forever. Thanks!

If you copy anything as a PNG, it defaults to 2X size. The problem I’m running into is that I’m copy screenshots from Figma into other tools like Axure all day long. Since “Copy as PNG” only copies at 2X, I’m constantly needing to group objects and create export settings unnecessarily over and over.I’m hoping for one of these solutions somewhere. Ability to “Copy as PNG 1x” with the existing “Copy as PNG 2x” Ability to choose a preference for “Copy” options Ability to respect the export settings of the parent frame when copying children (so I don’t have to recreate export settings repeatedly)Does anyone know if any of these are on the product roadmap to address? Or if something exists that I just haven’t found. I’ve seen this issue come up in forums a few times. Thanks for any help or tips anyone might have.

Hi, Updating components slows down the inability to browse other components from the open review detail of a component. I would also expect the possibility of browsing components in the detail.     Furthermore, if I update all instances, a button to move to the next component appears. However, it does not behave in such a way that it moves to the next component, but to the first, which is strange. An example of use is if, for example, I have the first component in the change list, where there are 300 occurrences, but I want to skip it at the moment, I go to the detail of the second component, update it, but then I have to go back and deal with the second component again.     I would like to see a button "Update all in this change/push/..." in the list of component changes. Now I can only update components one by one or all at once.       Thank you for checking the comment and I would be pleased if some (or all :-)) of them were implemented and I discovered them in one of the next versi

It would be great to be able to add a note when declining someone of Figma access, so I wouldn’t have to write separate email with explanation of decline decision. 

It would be convenient if we could inherit the code syntax from a referenced variable. It makes sense that the variable codeSyntax is interpreted out of the box, but it would be very convenient to inherit referenced variables in some scenarios. We have a variable collections for designers to control color from a matrix using variable mode. When inspecting the variables in use it would only output --background, --text because this is the name of the variable, but in reality these variables reference variables with other names and codeSyntax. These variables would look something like this:--ds-color-accent-background, --ds-color-neutral-background. This would also be the variable used in code. Whats your thoughts on this? 

Context: Currently, when a Figma design file is shared, its entire version history is automatically accessible. If the version history needs to be excluded, the only workaround is duplicating the file and sharing the duplicate — which results in unnecessary file clutter.Suggestion: Introduce an option to control whether version history is shared when sharing a file. This would help keep files organized and avoid sharing internal iterations that aren’t relevant to all stakeholders.

Is there a way to create variables for axes like width, grade, and slant? Or is the new typography variable support currently limited to the following: → Font family → Font weight and style → Font size → Line height → Letter spacing → Paragraph spacing and indent

Currently, if you would like to bold part a text using a certain style, you have to create an extra style with a different font-weight, then jump into text styles and pick a bolded one. Things get crazier if we would like italic, underline, strikethrough as well… 🤯 Fine. But this is not how coding works (something you’re trying to align to). Usually*, we can just mark part of a text in styled with only font-weight property. Something similar is required in Figma with the ability to assign shortcuts so we can easily use i.e. ctrl+B / cmd+B to assign bolded sub-style. Just like all your users work with text in any other software. Optionally, these could be just pre-made options to pick (bold, italic, underline, strikethrough). *I’m a designer not engineer though