Suggest a Feature

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? 

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

I have noticed that it is not possible to assign specific variables from a component to the internal components that make it up. For example, in a component composed of multiple internal components, you cannot assign a text variable from the main component to its subcomponents. This creates an issue when a property, such as a text variable, needs to be changed in multiple places simultaneously, as it must be manually updated in each internal component.It would be ideal if the system allowed assigning specific variables from a component to its internal components to streamline the management and editing of shared properties.

Record Prototype | A feature I wish existed in Figma 🎥. Adobe XD released this many years ago and had the time to die before it even existed in Figma. 🤷‍♂️. So, what’s stopping Figma from doing it?

We constantly do a lot of routine work and we often have to change the parameters of shapes, texts, etc. This is especially true if we need to apply the same operations on different objects. I suggest, instead of clicking on the panels or navigating menus, use a key combination that will repeat the last successful action. Here is video example Another video Would you use a function like this?

It would be cool to set a numerical property type for elements within components. List based components (i.e. tabs, table of contents, etc.) are the primary use case I can think of, but there are probably others. Having the ability to increase/decrease the number of items within a component instance (using a number counter type input or something), would be a great alternative to building the components with random/maximum number of nested elements, and then hiding layers—or nesting a series of numerical variants, or some other alternative.

When using the color picker, if the object you’re picking from has a color style applied, the color picker doesn’t apply that style to the selected object — it just applies the hex value (or whatever color model you have set) of the pixel you click. This can lead to messy colors not adhering to your style guide. Instead, the color picker should apply the color style of the clicked object if it has one. (You could click the stroke to apply the stroke’s color style, or the fill to apply the fill’s color style.) If you do want to be able to pick the pixel color instead of the style, there could be an additional modifier key to hold while clicking. With the current functionality, if you want to apply the same color style to another object, you first have to click the already-styled object to see what style is applied (assuming you may have multiple similar shades and can’t eyeball it), then click the object you want to style, and then find that color style in the list and apply it. The pro

When working with large files, I encounter such wasteful actions as expanding/collapsing each selected group of layers.I find it better to perform these actions in bulk. Here is my solution to this problem. Please vote if you are also troubled by this time-consuming process. 

Context: In Figma Design file, setting padding requires adjusting both sides (top +bottom, right+ left). While having the ability to combine longitudinal sides as one and latitudinal sides as another is helpful - it still requires to insert the same number two times(individually) for the times when the padding is same for all 4 sides for anything, which can be time-consuming and frustrating.Idea-suggestion: Introduce an option to apply equal padding to all sides with a single input, streamlining the process and improving efficiency.

If I open a file and accidentally make a change, then immediately undo it, I still get a new entry in the list of file versions. Now everyone else thinks something’s happened and has to figure out what it wasn’t.As one example of an easy accidental change, it’s not uncommon to accidentally move something when you select it to inspect it.If I undo changes back to the first change I’ve made in that session, no new file version should be shown. I didn’t make any changes; there’s no new version. Including a version in the list is confusing.

Silakan hubungi Call Center agoda 0831_21288181, tlpn/WhatsApp Layanan pusat bantuan resmi agoda

We have a navigation bar component in our shared library. We want the basic dropdowns and user profile info to overlay when clicking these menu items. Currently all overlays break when bringing in a component, and we have to make a local version of the library component. It would be great if the overlay from the library can work wherever it exists, rather than having to duplicate the overlays in every location.

make duplication of frames and other forms not horizontally, but in the visibility area of ​​the canvas, because it often happens that I duplicate something, and then look for this something, if I duplicate it next to another frame, which is out of the visibility area, while vertically there is space for duplication next to the duplicated frame, and the vertical enters the visibility area

Selling resources on the Figma community could be optimized  with these features:Break down of purchases per subscription type setup by seller in resource Metrics tab eg. Monthly vs Annual Add a notification when someone unsubscribes and detail the subscription type, doing the math each month to measure churn and user count per subscription type is a trrible waste of time.  Show monthly churn: New users per sub scurption type, Lost users per subscription type Trends graphs per sub type Allow retention offers or user feedback triggered by user unsubscribing 

I use Figma for UI and graphic design but also for illustration and some motion now. And one thing that I miss often is brushes ! Vector ones of course. Not even complicated ones, without transparency, maybe just a pencil, a paint brush and a marker. Maybe just the ability to add automatic variations to the strokes to give them a more natural or hand drawn feel. I tried Variable-Width stroke plugin but i wasn’t convinced. The option could be add to the stroke panel, in the advanced stroke options. Am I the only one who dreams about it ?

Hello Figma Community! 👋I’d love to propose a feature that could improve visibility when designing in Figma: the ability to adjust line thickness dynamically when creating shapes or lines.🎯 Why is this important?Currently, when drawing shapes or lines, they appear with a default stroke width, which can sometimes be too thin, making it difficult to see clearly—especially when zooming out or working on detailed UI elements. This would be particularly useful for:✅ Wireframing – Ensuring clear visibility of structures.✅ Annotations & Guides – Making key elements stand out.✅ Improved Accessibility – Easier viewing for users with visual impairments.🛠 Suggested Features:1️⃣ Dynamic Thickness Control – When creating a line or shape, allow users to set a default stroke weight for better visibility.2️⃣ Auto-Adjust Stroke Width Option – A setting that increases stroke visibility based on zoom level.3️⃣ Custom Presets for Line Styles – Save default stroke weights for different project needs

So you can loop videos now in prototypes, but I am using them ads backgrounds a lot, where it would be cool if the transition in the loop is more smooth in stead of a hard cut. Maybe it is an idea to add the option to have videos ‘boomerang’ forward and backward in a loop.

I wish that I can turn on or off each properties in nested instance, so that my team will understand which properties are allowed to use in the Component

Suggestion: It would be incredibly helpful to have a status update for variables that have been created but aren’t being used anywhere. Additionally, for variables that are in use, a way to map or locate all their instances across the file would make managing and organizing them much more efficient.

I can’t believe this basic text formatting issue is still unaddressed in Figma in 2025, but I need to indent a full paragraph — every line if it, not just the first line, and not with a quote. Has anyone found a workaround? I know I can give this paragraph its own text box, but that just stinks. Other ideas? Plug-ins anyone has found that work? Thanks! And Figma — for the love of all that is holy, please fix this.

Similar to Figjam, I would love to see sticky notes available from the bottom toolbar maybe under region tools. Currently having to copy them over from Figjam or older Figma projects. Figma toolbar - Region Tools with Note 

Add access to variables in Dev mode. The variables are needed to be visible in the Dev mode, because they want to see all variables when we adding new theme or make any changes, so it’s to hard and impossible to take all changes from the components and the plugins doesn’t match our way and needs.

By smoothing strokes we can make some designs look more soft and clean, it would help a lot.