Suggest a Feature

The Dev Mode Annotation feature released today is fantastic. However, I find it inconvenient that only one annotation can be added to one element. For example, if I want to explain a change in functionality in the same area of Mobile and Desktop, I may want to add a single annotation to multiple areas.

I often duplicate existing mocks to work on feature updates. Deleting previous annotations one by one is extremely tedious. It would be helpful if the tool could recognize when a frame has been duplicated and then allow bulk clearing of annotations.

An edge case however I’d love to see this update eventually. I have a segmented button component that contains nested button component variants. This segmented button component lives in many different places in my UI, utilising the different forms of the nest button component (text , icon, icon and text) I’d like to be able to set a min width to the nested button components inside my segmented button component instance WITHOUT having to set the min width to the master button component.

HiThe bottom toolbar feels a bit like an annoying appendix, always "in the way".Couldn't there be an option to put it on top [example bellow]?  This space isn't used that much, unless you have a lot of files open, which isn't a best practice anyway.And in larger screens, it's a lot of space.And these tools are mainly accessed via keyboard shortcuts.Thanks

I am using Figma from almost 2 years. It’s a great tool. Previously I was using Windows 10 yet recently switched to Linux(Ubuntu). Figma doesn’t have any official release for Linux. There are some Unofficial desktop versions but they are “BUGGY”. I request you guys to release an official Figma desktop app for Linux.

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)

One important feature is missing = Merging cells 😦 Is this feature included as an improvement in the near future?

In Finland, we have to attach the invoices to all card payments for bookkeeping. Now I need to every month to go to Favro and manually download the invoice. Please add a feature where I can define an email address for the invoice emails and automatically send new invoices in an email with the PDF invoices attached so that we can automate the download and processing of the invoices. The subject of the email should have the same structure each month ("You Figma invoice YYYY-MM-DD) and the PDF invoice name should be unique and contain the date of the invoice, for example, Figma incoice YYYY-MM-DD

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

Angular + Figma MakeSupport for Angular in Figma make:Whoever think it’s important - Vote. Thanks,Galit

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!

There are times when having sections free of constraints is nice… but my design team has become addicted to using auto layout with frames. In many cases when using sections, it would be amazing to perfectly space the inner sections out using auto layout.

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!

Since Figma does not support going back to previous views, it is quite frustrating to switch between pages. Would you ever allow the same file to be opened in another tab, but not in a new app window? This would become very handy to switch between pages in the same file.

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?

It would be a great idea to add the ability to move annotations (сhanging the place). Right now, they’re fixed in place and can overlap other elements. And you cannot change it.What I mean is the ability to reposition an annotation freely while keeping the link to the target object intact.Annotations are a really useful feature—thank you! Previously, I had to create similar functionality using my own objects. Please do not move this offer to another discussion. 🙏Can we move the Figma Annotations (in dev mode) from one Figma project to another?These are different questions.

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