Suggest a Feature

Nice work including Typography and Gradients as variables! But I feel like the ability to use a variable for opacity when defining a color palette is missing. Which means the size of my color palette is double what it should be as you have to define each opacity as a separate variable.

Enhancing variables to have extra logic in place so that variables can be partially based off other variables e.g. Number new_variable = “{other_number_variable} + 4” String new_variable = “{other_text_variable} New Text” Colour new_variable = “{other_color_variable}, opacity 4” Boolean new_variable = “not {other_boolean_variable}”

In Figma, I can create a color variable like Primary/500,but there's no way to create another variable that links to Primary/500 with just a different opacity (e.g., 50%).This becomes a problem when I change the base color — I have to manually update every opacity variation, which is time-consuming and breaks the idea of dynamic design systems.🔧 Feature Request:Allow opacity to be applied on top of existing variables when creating new ones.

My team and I are currently having the inconvenience of having to publish our library every single time we make even a small change (like a font size increase, color change, etc.) and then switching to the working file and manually updating the library. Due to the nature of the project we do this quite frequently and having to publish – switch file – update every single time to see the changes in our designs turns out very time consuming if you add it up. It would be amazing if Figma could integrate a shortcut for automatically updating a library and automatically updating the files it is being used on (like a cmmd+S shortcut!), of course not everybody might want to have this so it would also be nice to be able to turn this shortcut on and off.

Please add the ability to add timeline markers to the Motion timeline. Like in After Effects

Web performance is no longer optional, it’s a core part of the user experience. Yet today, 2026, exporting assets from Figma still requires external tools or manual workflows when teams want to use modern formats like WebP.Adding WebP as a native export option in the export panel would solve a very real and widespread problem:Smaller file sizes without sacrificing quality Faster load times for websites and apps Better alignment with modern frontend standards and performance budgets Reduced reliance on third-party tools or batch conversion scripts (love your plugins folks, but let’s be realistic, it should be a core feature)Right now, the gap between design and production increases unnecessarily because designers can’t export assets in the formats the modern world actually uses. This creates friction, slows down workflows, and introduces inconsistencies (e.i. WordPress natively supports it now).Figma has always been about closing the gap between design and development. Supporting WebP e

Hi! Please consider adding WebP to the native export options. It’s widely used for web performance, and relying on third-party plugins or external converters slows down the workflow. Having it built straight into Figma would be amazing. Thank you!

I often work across multiple pages within a single Figma file/project, and I’d love the ability to open different pages as separate tabs in the desktop app—just like I can open different files. Currently, I have to either open and close multiple pages many times to get what I need from other pages, use multiple windows or duplicate the file, which isn't ideal for managing design systems or multi-page projects.This would greatly improve workflow efficiency for designers managing large files or working across different sections (e.g., desktop vs. mobile layouts) simultaneously.Please consider adding support for tabbed views of multiple pages within the same file.

It would be really helpful to be able to use a variable to set a Type Style’s Letter Case (under the Type Settings meatball menu). It could be a String Variable, and the options would be “As entered”, “Uppercase”, “Lowercase”, “Title case”, and “Small caps”. I personally use modes to switch between different brands, and some brand styles require uppercase while others don’t allow it. This suggestion may be a small feature in the grand scheme, but I wonder if others would also find it useful.

Whenever I create a arrow line, it always defaults to black color with 3px stroke. I often use the arrow line (Shft + L) to indicate any notes/guidelines. Applying default properties like as we do for the text will greatly help with the stroke and color properties for the line aswell. Do you expereince the same thing ? Is there any workaround you could suggest ?

Request:Provide an option to easily duplicate or backup files via an API Reasoning:The REST API comes with a lot of options, but it doesn’t allow you to copy files, projects or teams.There’s an option to download files, but not as uploadable content (i.e. as .FIG), nor is there any option to duplicate them, if they are e.g. used as a template for another team.Possible (i.e. my) use case:I work in an enterprise. We have a base design system with tokens that we hand out to external agencies and do some automatic checks via different APIs. I would like to automate the duplication process of these files completely. However there’s no good option to do this at the current moment.

Would be great if the cursor chat function was enhanced to be able to easily type/add emojis. It’s possible to do so through a MacOS keyboard function but it’s pretty clunky to do it that way.I often find myself wanting to use the cursor chat to show a thumbs up/down or to simply express a quick reaction to something.

I have a very distinct first and last name. My Figma profile uses my full name, which is important for our organization-- coworkers and partners in Figma need to be able to easily tag me in comments and see who worked on files. However, I would like a way to have a different display name and handle for the Figma Community. I don’t really want my questions about plugins, etc. to be publicly searchable if someone were to Google my name. I prefer to have a privacy option and keep my professional work and personal online presence as separate as possible.

Hi,The addition of annotations and measurements to Design mode is such a great decision.However this is rendered almost useless if the annotations and measurements can’t be made visible to View Seat users.Often annotations are used for communication with a range of stakeholders, not just designers and developers. It’s not viable to upgrade every stakeholder to a Full or Dev seat to engage with this content.

When reusing Auto Layout across different frames or components, there is no way to copy and paste only the Auto Layout settings. Users have to manually recreate spacing, padding, alignment, and other layout properties, or use Paste Properties, which also applies changes they may not want. SuggestionIntroduce a dedicated Paste Auto Layout action that copies only Auto Layout properties. When pasting, a small dialog could let users choose which settings to apply, such as Direction, Spacing, Padding, Alignment, Wrap, and Clip content. This would make it much faster to reuse layouts while avoiding unwanted changes to fills, effects, typography, or other design properties.Addition!This could also work to fills, strokes, effects. ExampleRight click an Auto Layout → Copy Auto Layout → Paste Auto Layout on another frame. A dialog appears where users can select exactly which Auto Layout properties to apply before pasting.  

A feature idea: "Spotlight My Pin." When navigating large Figma files, I often lose track of the area I was comparing. It would be great to right-click anywhere on the canvas and drop a temporary pin to save the current viewport, then instantly jump back to it later. This would be much faster than searching for frame names or manually navigating back across the canvas.

Is there a way to turn off the AI chrome when sharing the prototype in "Make"? When sharing in the prototype view, I was expecting it to just share the screens but when I shared the link, it showed the make file with the AI chrome. Is this a big? Or will this be an enhancement?

Is it possible to add comments in Figma, I shared the prototype to few folks wondering if there is a comment feature.

ProblemWhen selecting a frame or Auto Layout containing multiple text layers, there is no way to edit their shared typography from the right sidebar. Users have to select each text layer individually or use workarounds, even when they simply want to change a common property like font size, font family, or weight.The suggestionIntroduce a Selection Typography section that appears when a selected frame or Auto Layout contains text layers, similar to how Selection colors works today. It should display the typography used within the selection and allow users to edit shared text properties across all included text layers without selecting them individually. This would make global typography changes much faster when refining layouts, creating design systems, or iterating on UI screens.ExampleSelect an Auto Layout with multiple text layers. A Selection Typography panel appears in the Design sidebar, allowing changes to properties such as font family, size, weight, line height, and letter spac

Adobe XD included folders in personal drafts so you could organise your own work. I have many projects on the go at the same time which can span up to a year, which only I need access to at this point in time. I can’t move it to my Teams folder because in a large company this creates confusion. In our workflow, when its ready to share we move it, up until then it sits in my drafts, but it is getting confusing with main projects mixed in with R&D.

Hi Figma team,I’d like to suggest a feature that would be really helpful in collaborative workflows: the ability to copy and paste comments between different files.Currently, comments are a great way to communicate within a file, but when we need to reuse or migrate comments such as when duplicating parts of a project into another file we have to recreate them manually. It would be very useful to be able to copy a comment from one file and paste it into another, preserving its content, author, and ideally its relative position.This small improvement could save a lot of time and make collaboration even smoother.Thanks for the great work on the platform!

I’d like Figma components to support conditional/dependent properties inside the Properties panel.Current problem:Large design system components often expose many boolean, variant, text, slot, and instance-swap properties at the same time. Some of these properties depend on each other, but today they stay independent.Example:- If `Show Badges = false`, then `Slot Badges` should be hidden or disabled.- If `State = Active`, then `New Message`, `Show Separator`, and `Swap Icon` could automatically switch to predefined values.- If `Badge mode = Match`, then credential badges should be hidden automatically.- If one badge group is enabled, another mutually exclusive badge group should be disabled.Current workaround:We have to create more variants, nested components, or expose multiple booleans manually. This works, but it makes component APIs noisy and allows invalid states.Suggested feature:Add simple conditional rules for component properties, for example:- when property A = true, set prop

In our design system we have different styles that are connected to variables. We are using a variable font and we can apply number variables to font-weight (300, 400, 500, 700 etc.).We could also use string variables, which works if we used the standardized font-style and weights (“Bold italic”, “Semibold Italic” etc.). However, we don’t.I’ve noticed that when I’ve picked “Italic” and set a numbered font-weight (variable font axes) the dropdown shows the font-style (“Italic”) and the weight (550) separated by a comma.I was hoping and thinking that perhaps if I made a variable that matched the text in the dropdown “Italic, Weight: 550”, it would work. Nope, it didn’t. Proposed solutionSo, we would like if the font-weight could accept this type of combined variable or a more semantically correct solution: separate font-style and font-weight into two inputs in the UI and let us use separate variables for them. Screenshot: Font style and irregular numbered font-weight 

I am an enterprise customer. Our team uses text variables to maintain a large library of metadata. It’s used in multiple parts of our files and has become integral to our workflows via fast iteration and advanced prototyping.Please bring text styling (aka forced line breaks, bolding, italics, bullets, etc.) to text variables. It would be extremely useful to my entire org and help us continue to utilize Figma variables as an integral part of our workflow.Because we don’t have the feature, we run into many inconsistencies across design files and have a hard time maintaining a library.