Suggest a Feature

In Present mode (prototype mode), it is not possible to edit the flow description.This would be very useful to me, as it is often when I review my prototypes that I notice details I want to add or modify in the persistent flow description. And currently I have to go back to design mode to do that.The flow description helps my viewers understand the context and subtleties of the flow they are looking at, so it is important to provide a thoughtful description (possibly in the form of a user story). Note that I don’t want to use mere comments for that purpose, as comments are designed to annotate a specific part of a frame (not the entire flow), and also they aren’t persistently displayed so they can be missed easily. Anyone with similar need?(Such an Edit function could of course be provided to Editors only)

We’re building a plugin that runs part of the workflow in FigJam and the next step in Figma Design. Today, plugins are scoped to the current file/editor type, so moving users to the next step is awkward. What we want to doFrom a plugin running in FigJam, programmatically switch the user to a linked Figma Design file, ideally without asking the user to manually open another file and relaunch the plugin.What happens todayThere’s no reliable way for a plugin to open/switch to another file + editor type. openExternal() with a Figma URL is not a reliable fallback in the desktop app: it often just focuses the app and lands on Home/Recents rather than opening the intended file. The result is a broken UX: we must show instructions like “open a Design file and relaunch the plugin”, which is confusing and feels unprofessional. Why

I love sections because they easily help organize content, but they become less powerful as compared to a traditional group without the power of auto-layouts. Adding new content to a section always involves slowly moving everything else around (usually down) and having to always resize it manually. Having the option of toggling on/off something like auto-layouts for sections would really boost productivity!

It would be so useful to have a zoom to: width of the frame/page. It’s one of the most used views for “scroll design”. And also, when zooming in to fine tune a detail, you want to zoom back to the previous one, alternating between them with the same shortcut - what about ALT-Z? instead of zoom out with click - less used.

Hi everyone! I’ve been using Figma for quite a while, even before Figma Slides came out, and I often used it for presentations. One feature I relied on was animations—especially hover effects, like changing an image on the right when hovering over text. However, I can’t seem to find that capability in Figma Slides. Does anyone know if there are plans to add hover effects or similar animation features to Figma Slides? Or maybe there are alternative solutions? I’d love to hear from the community or the Figma team. Thanks a lot!

Hi everyone! How we can make design systems more self-documenting and easier to audit, especially for larger teams working on accessibility and consistency. It would definitely automate our tasksMy Idea:A Visual Variable Heatmap overlay in Figma that shows the usage frequency and distribution of: Color tokens (e.g., how often a specific color is used across frames) Text styles (e.g., font size, weight, line height combinations) Spacing tokens (e.g., padding/margins used most often) The heatmap could be toggled on/off per page or per component library, using soft color overlays (like low-opacity via styles) so it doesn’t interfere with design perception.I have seen a few benefits of it:Quickly identify inconsistencies (e.g., when a token is “official” but rarely used)Highlight potential access

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?

Right now, the “Update from main file” modal is the least helpful modal imaginable:No indication of what or where the conflict is. All I see is a zoomed-out view of my “Layout & Content” library page with nothing highlighted or listed out anywhere. And with this information, I have to choose whether to keep these changes or keep my branch. I manage a design system for a team of 10 designers, split up into 3 pods. This is a nightmare every time.Items with changes should be highlighted, and those changes should also be listed on the left-hand side.Edit: And would you look at that, I chose to keep the branch, arbitrarily, and the next screen actually shows me what the update involves! Why wouldn’t this be on the first screen? (I’ve edited out the content for NDA reasons) Now I actually have to go back to the previous screen and

There’s an issue I keep encountering every time I have to work with vector icons - you cannot have a flat, fully linear no-fill icon which has dots in it. You have to have two separate layers - one linear with just a stroke and no fill, and one which contains all the dots as filled circles without a stroke. This makes it hard to control transitions and is overall annoying. Please consider adding the option to create single-node dots that would be controlled by the stroke variable only, like a line of length 0, so that we wouldn’t have to add circles to linear icons. P.S.: or just make sure that the fill colors are preserved across instance swaps regardless of the amount of layers and aren’t reset to the inserted element’s default color, destroying my transitions. That would work too. At the moment instance swaps only consistently work with single-layer linear icons.

ProblemCurrently, Figma does not allow designers to create a reusable style for link-like or inline action text.Text Styles in Figma mainly control typography properties such as: Font family Size Line height Letter spacing However, common link or inline action properties like: Text color Font weight variation Underline / decoration intent cannot be defined as a reusable style and applied consistently across files.As a result, designers either: Manually restyle text every time, or Convert text into a component, which is not ideal for inline usage inside paragraphs or labels. ExampleA typical UI pattern:“By continuing, you agree to the Terms & Conditions.”

Add AHEX Color，eg：Color(0xFFF7F7F7)

JSON (JavaScript Object Notation) is a simple text format used to store and share data between websites, apps, and servers. It is easy for humans to read and easy for computers to understand. JSON is widely used in APIs, web apps, and mobile apps to send data like names, numbers, lists, and settings.OnlineJSONFormatt makes working with JSON easy by providing free tools to format, validate, edit, compare, and fix JSON errors online. It helps users quickly understand messy JSON, correct mistakes, and work faster without installing any software.

Intro There is an interesting concept in Figma that’s used and was presented by multiple people and has different names: Placeholder, Slots, Dummies, Layout Blocks, and so on: ❖ Placeholder component is the base one. ◇ Placeholder instances may be nested into another ❖ Component. ◇ Placeholder instances nested into ◇ Component instances may be swapped with any other component instances… More details in this video by @Adam_Ruthendorf-Przewoski. The next step of its evolution is Layout Blocks by

ProblemThe UI for viewing and editing text styles in Figma has a clear and well-structured hierarchy.Styles are grouped logically (e.g. body → size → role), which makes them easy to scan and understand.However, the UI shown while applying text styles to typography does not follow the same structure.All styles appear as a flat list with limited hierarchy, making it harder and slower for designers to scan and select the right style—especially in large design systems.Why this is an issue Designers rely on quick visual scanning when applying text styles. In large DSMs, flat lists increase cognitive load and selection errors. The inconsistency between Edit/View UI and Apply UI breaks mental models. Suggested ImprovementMake t

I would like to move into making my presentation decks in Figma, however my team does copywriting — my clients need to be able to copy text from my presentations, but I do not want them to have editing access to my Figma files, they should not be able to take the DESIGN of my presentation just to copy text.

Adding the ability to create basic charts in Figma Slides would be great. I rely heavily on displaying data in Google Slides to present to the team along with screenshots of our product. I would like to not use Google Slides anymore. Another great addition to add later would be to import a CSV with data or a Google Sheets integration to pull the data from Sheets.

Hey wonderful people at Figma, I love the new variables, absolutely love love them! Here’s just an idea, but when adding a numerical value variable, I wish I could include only “Paddings” as the supported property. Right now when I want to save paddings I have to use “gap (auto-layout)”. While usually these properties are the same value and I can see the though behind not separating them, I do want to play around with them and would like them to be separate, especially when changing modes for device sizes. Additionally, I’m not gonna start a new thread and I’ve already upvoted the ones I’ve seen, but I would also really like if I could use prototype interactions to change between modes. Thanks and have a lovely day!

Hi Figma!I’m a developer working with a team creating a design system and React component library. Our designers use tokens for pretty much everything, and a key part of our workflow is exporting the tokens as CSS variables, which can then be used in our React component library.To do this, we use a community-created plugin called Variables2CSS. It’s fantastic that someone created this plugin (thank you to the author!), but it presents us with one main problem: we need to be in Design Mode in Figma for the export to work correctly. If we’re in developer mode when we use the plugin to export the tokens, some tokens go missing.This is a problem within my team, as we need to purchase a designer license for each developer who needs to export the tokens. As my employer will only pay for one designer license for this purpose I am stuck being the only developer in my team who is able to do this. It’s a hassle for me, and if I go on holiday, or I’m off sick, th

As I am navigating in design and editing a lot of things hovering each others, I would like to fix parent element in order to avoid selecting or editing then directly. Locking all hierarchy is a bit cumbersome and does not help me working with all those elements properly and efficiently.Is there an option I don’t know or maybe a plan to make figma design evolve in this way ?

I have a slide with an embeded prototype. The prototype is an interactive logo which is supposed to have a surprise interaction on hover. But the prototype loading totally ruins the effect. There would be several ways to fix this:Allow for preloading of prototypes on previous slides Allow for fading in of a prototype after it has loaded Allow for a mask to go over the top of the prototype which fades out after a certain amount of seconds. (Currently this is not possible because prototypes are forced to top layer.)Image shows the context:Logo is actually a prototype where letters swap on hover 

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

Why wouldn’t a variable’s “description” from the details panel not be included in the variables export JSON data?

Figma has added percentages to text styles, which is fantastic. However, when the style is linked to a variable, the percentage is removed, and uses px units instead. I am trying to set up my design system using a scalable token system, and little features that don’t quite work are so frustrating. Please allow variables to support percentages! It will help us not need to use plugins like Token Studio. 

Description: The feature allows users to export local variables from Figma as a single file, making it easier to share design tokens and maintain consistency across projects. Current Format: Currently, local variables in Figma need to be copied individually or manually noted down, which can lead to errors and inconsistencies when transferring information between team members or projects. Proposed Enhancement: Implement an export option that allows users to select multiple local variables and save them as a single JSON or PDF file. This file can then be easily shared or imported into other projects or reviewed by developers. Benefits: Streamlines collaboration by ensuring all team members have access to the same variables. Reduces manual errors and saves time in the design handoff process. Enhances consistency across designs by providing a single source

Figma’s variables feature is a game-changer for design consistency, but what if we could take it a step further? Imagine a seamless connection between Figma variables and SCSS, enabling real-time updates across design and development environments. Here’s how this could work: Proposed Features: Export Figma Variables to SCSS: Designers can define variables (e.g., colors, typography, spacing) in Figma. These variables can be exported as an SCSS file with proper formatting. Example: scss $primary-color: #FF5733; $secondary-color: #C70039; Sync Updates from Figma to SCSS: Changes to variables in Figma automatically update a connected SCSS file. This enables design updates to reflect in development environments, at least in staging or development builds.