Suggest a Feature

Automatically add page numbers to the selected slide in Figma based on Slide position. Maybe we can select any text and give it the numbering option?

Config 2025 release broke my designs with Grid!And it could be an upgrade, if:Grid could HUG CONTENTS (row, column, grid itself) Rows, columns and cells could be resized (fixed value, %, colspan/rowspan, flex-grow value) Switch between flex wrap (items jumping to next row) and grid

The versioning in Figma Make is available, but since the AI cannot maintain consistency if there is a way to list and name these versions, it will be easier to fix the mistakes and issues.

Add the ability to select which properties to publish of a component and of a nested component. One use case for this is State in many components such as Button. State has Default, Hover, and Pressed. These states don’t need to be published, they are purely used for prototypes. I don’t want to clutter the properties list for consuming designers. Disabled and Error are created as Variants with “true” and “false” values. There’s no need to publish State property. Original idea here requested by XavierV

As a designer using a design system and searching or swapping a component instancr, often a term you search pulls up other components not in line with what you want because of a similarity in name. The most common culprit are icons.It would be great to do a quick negative filter like in VSCode with find and replace when looking for components to swap or insert to negate a group of components. This could also be a quick hack to cut out other active design systems from the keyboard.

Would be nice to limit this permission to developers only, while still allowing other roles to view files. It is about time Figma improves the role and permissions management. We need dev roles or more granular permission settings.

We’re working on a larger Component library that includes non-published components (components with the prefix _ or .) as base components in order to simplify large, complex components. We intended – in some specific cases – to offer regular components as templates, that a designer would then have to detach and work with a bunch of base components to build the desired design. What we have come to realize with this approach, however, is that these non-published components don’t receive updates from the library when they are updated in the main library. Is this intended behaviour? We basically have the option to simply publish these base components as regular components, but that of course would mean cluttering up the assets overview with a bunch of modular components.

As a designer I would like to record my prototype screen or export it as a gif so I can use it in presentations and send quick examples in the team group. It would be great to have the same feature then Principle to record or export the prototype to gif. Does anyone have the same need? Is anyone using a plugin or workaround to help solve this?

It’s currently too easy for contributors to make small changes that go unnoticed by maintainers. Especially in large files, there’s no way to track exactly what changed. Enforcing that the main file cannot be edited unless you branch will allow maintainers to view exactly what has changed and require reviews of contributions.

I wish there was a right click option if Figma that lets you select any item on your canvas and lock it to sticky, so the reference can follow you as you pan around, just a simple “make sticky” and you can still move it around if you need to adjust where it is “sticky” from. aaagh.

Often I’m adding autolayout around a frame/component/element, and the default vertical and horizontal padding is 10px. As well, the gap applied is 10px. It would be amazing to set the default padding and gap to auto-layout elements. This would help with keeping your files clean, but also, to ensure that redundant CSS properties are not added to dev mode output. Clearing and resetting these properties takes time and often the gap is not cleared due to the property not having an affect on single children. Thanks!

Currently trying to pan with spacebar is not working in many scenarios because other areas of the app are “in focus”. This is super annoying because you always have to click inside the canvas to get focus to be able to pan again. However, this selects or deselects elements which is almost never wanted.Even when in prototype mode and an interaction is selected, paning doesn’t work, even though the focus is in the canvas area.Also super annoying, when clicking on a comment, the focus goes directly into the reply input. So pressing spacebar to pan results in a comment consisting of a lot of spaces.This is super annoying and costs a lot of time accumulated during the whole day. Please make spacebar pan work always! No matter where you focus is, as long as the mouse is in the canvas area. Or at least include a setting to control the behaviour.Thanks!

Create tags that can be added to post it notes for user research analysis

I’m in a company with a large sales team, with multiple client meetings weekly. So we have a lot of repetitive slide decks get duplicated and modified, with new content and infographics tweaked on a weekly basis. Templates for STYLING is amazing, as the only designer, I LONG for the days I don’t have to bully clumsily placed pixels, poorly cropped photography and off-brand typography in Keynote on a near-daily basis in order to keep our branding on point. However, despite Figma having by far the strongest offering regarding DESIGN templates (yay), a way to retrieve the CONTENT of slides, making CONTENT changes that could be published to ALL related slides is entirely lacking. If INDIVIDUAL SLIDES could be TAGGED, or otherwise CATEGORISED, it would make searching for, and maintaining relevancy of content much more effective. Currently as a sales team member, if we switched to Figma, I’d still have the problem of remembering not only which deck a certain slide exists in, not only checkin

 Hi 👋,I am developing a plugin that needs to analyze text blocks and split them exactly “line by line” as they appear visually in the Figma editor. The goal is to process each displayed line, including those that result from automatic wrapping (not just explicit line breaks in the text).Currently, the Plugin API only allows splitting text on explicit newline characters (\n), but there is no way to obtain the actual visual line breakdown as rendered by Figma’s text engine (i.e., where lines wrap automatically due to width, font, size, etc.).Why this matters: Many workflows (translation, accessibility, animation, content synchronization, etc.) require manipulating text “as seen” line by line. Workarounds (simulating rendering, OCR, etc.) are complex, unreliable, and do not always match Figma’s own rendering. Only Figma’s engine knows the true visual line breaks, since they depend on many internal parameters. Feature request:Would it be possible to add a method to the Plugin API that

Crossplatform programs

Page dividers or spacing? 🤔 Cause this hack to use a page to fake it is in 99% of all Figma files I’m in. Does anyone else experience this?

HeyI want to do the same result in the image but without outlining the text to path because i want the change the text on different instances. but i can’t do such thing due to the text size being fixed when scaling the container  

I created a component, with some variant and properties.This component is then used in a Buzz template. This is then used to create social media assets.  When I first copy-past the component into the Buzz template file, the properties are here (all of them), and as soon as I publish the templates, they di (see attached screenshots).Also, the nested properties work perfectly.This is weird, is there anything I’m doing wrong, I don’t get it.And I also noticed, that basically I cannot add Variant properties in a Buzz file, it just doesn’t work. Maybe there is a bug on and that is why it removes my orignal properties ?  

It seems like the new accessibility checker for color does not work when using a color variable. It would be great to not have to break the variable to use that feature. 

I work at a large company and often help some of our view only and collab seats navigate Figma files. But I often am not sure exactly what things they have access to. Is there a way I can “toggle” into view only mode like I can into dev mode to see what they are seeing so I can help better inform them?

I’m using figma for development meaning I’m using figma design files shared from a designer which they give me Edit access, I find using View mode more effective for me while developing i.e easier time getting the images sources, it just more convenient for more to use View mode instead, However There is no easy way I am aware of, to switch from edit to view mode other than sharing the file with to a different user and give them only view access.I selected this as a question, because I’m not exactly sure if there is an easier way.What i want is to be able to change between (Edit/View) modes in figma design files.

For example, it would be cool to allow collaborators to create new posts and the like (obviously based on the assets) simply from their smartphones, without having to pick up or carry a PC. Yes, I know there's a desktop version on web browsers, but a more accessible version would be better, perhaps from the existing figma app.

I have set up a lot of my designs using variables and maintaining the variables by manually looking them up in the clunky variables window overview is a real pain. It’s almost at the point that I might as well abandon using variables for language versions.If I had the option to search my variables it would make the process much easier.Also as a bonus it would be so nice if it was possible to update a variable from the artboard. If the object on the artboard has a variable tied to it, when you change that object just make the variable connection into something that lets me choose if I want to update the variable or break it. Would be much more convenient than going the other route.Thanks.

Dear Figma Product Team,I am writing to formally request the inclusion of native artboard presets and enhanced tools specifically designed for foldable devices within Figma. As foldable technology rapidly matures and gains market adoption, designers are increasingly encountering complex challenges when creating adaptive user interfaces for these innovative form factors.The Current Challenge for Designers:Currently, designing for foldable devices in Figma requires significant manual effort and workarounds: Manual Artboard Creation: Designers must research and manually create custom frames for various foldable models (e.g., Samsung Galaxy Z Fold/Flip, Google Pixel Fold, Microsoft Surface Duo) in their multiple states (folded, unfolded, half-folded/Flex Mode). This is time-consuming and prone to inconsistencies. Lack of Standardized Dimensions: Without official presets, different designers often use slightly varying dimensions, leading to fragmented design systems and handoff issues.