Suggest a Feature

To further enhance the AI capabilities within FigJam, Figma, Buzz, and other associated file types, we propose introducing project-level system prompt support.This feature would allow users to define a custom AI 'system prompt' at the project level, which would then apply as a foundational context for all AI interactions within any associated file (e.g., FigJam boards, Figma designs, Buzz documents, etc.) residing in that specific project.Key Benefits: Consistent AI Persona/Context: Ensure the AI maintains a consistent tone, style, and understanding of the project's goals, brand guidelines, or technical requirements across all files. Reduced Repetition: Eliminate the need for users to repeatedly provide the same background context to the AI within different files or individual prompts. Tailored AI Assistance: Enable more relevant and accurate AI suggestions, content generation, and analysis specific to the overarching project's domain or objectives. Streamlined Workflow: Accelera

As a passionate user, I truly love Figma for its powerful capabilities and the way it fosters creativity and collaboration. However, I am very frustrated with the current direction the platform is going, particularly with the added financial and administrative barriers for collaboration among paid users. To ensure seamless and frictionless cooperation among Figma users, we propose the following adjustments to the current collaboration and billing model: Unrestricted Collaboration Among Paid Users: Allow users with paid subscriptions (e.g., Professional, Organization plans) to collaborate on team files without additional costs. This means that if a freelancer or agency with a paid subscription joins a team project, there should be no need to pay for extra design seats, as all parties are already contributing financially to the platform. Temporary Paid Seats for Non-Paying Users: Continue offering the option to add temporary paid seats for non-paying users. This is a great solution f

Lately, I’ve been really missing the `Title` field for publishing changes. I’m surprised this was removed with UI3 now. BenefitsHelps break up Version History at a glance, instead of just having `Components published` down the entire list. Saves time later instead of having to edit version history changes with a specific title.RequestPlease bring back the `Title` field for the “Publish changes” window. Curious why this was removed? At the very least, maybe do what GitHub Commits do where the first line automatically becomes the Title, and the lines after (especially if bullets/hyphens are used), become the description automatically.

I’ve just seen that I can’t get back to the instance I was just working on by clicking on the “Return to Instance” button.

If you want to know ‘How to Cancel Crunchyroll Membership,’ this simple guide will get you there very fast. Before going with ‘how,’ let’s talk about ‘why.’ If a person has taken a certain membership and is using that service and suddenly wants to know how to cancel it, then it could be a serious issue. There could be several valid reasons, such as content limitations, multi-device streaming, support issues, subscription costs, and many more.Hence, these are the proven reasons why users usually cancel their subscriptions. Now, let’s dive into the how sections.Well, it is quite easy to perform;When you sign in to your account on the Crunchyroll website, you can terminate your current subscription.When you log in with your credentials, you can easily navigate to your account settings. After reaching out to the settings, you can find the option ‘Cancel Membership.’ This is the option from which you can easily cancel your subscription. During the cancellation, you will be asked why you wan

dear figma team , please add copy and pasting feature for animations with a shortcut to quickly copy and past pre made animation between components . thank you 

Actually if you give any option for changing the base domain link like custom link it will better

Hi guys, I've been sitting on this idea for a while now. Let me know what you guys think.The feature is called Anchor, and it allows users to drop an “anchor” on a specific location in the canvas, navigate freely to other parts of the file (to assist teammates, inspect components, etc.), and then quickly return to the anchored location with a single shortcut (e.g., pressing the space bar). This idea’s on the house… but I’ll leave my bank details here just in case you feel generous when you roll it out.😅 

I’ve been playing around with Figma Make for the last three days and I wonder if it would make sense to have an option to pause after reasoning for the user to read and recommend changes or suggestions to their thinking. This feature will be off by default. Either you let it continue after reasoning, or suggest small changes in its reasoning or you stop and re-prompt.

Please create a feature where the nodes can be collapsed. I’m on the brink of migrating from Mindmeister but FigJam can’t collapse nodes, so my large mind map will look so messy. I only tackle one subtopic at a time in my group meetings. Thanks in advance

I can’t seem to find a way to Hide all lower levels of my mind maps. I click on the arrows, and nothing happens. It’s making a mess. I can’t use it for practical reasons, presentation-wise it’s kinda frustrating. Is there any viable way already for me to do it? If it’s yet to come, please do it 😍 it’s a game changer for me and many others who are still waiting for it

Hi, Apologies if this question was asked before. How do we expand/collapse the nodes in a mindmap? Will be ideal to be able to do so, otherwise the mindmap gets too big thus having to constantly scroll left/right/top/down breaking the flow of the presentation. Thank you.

In short when you are building a library there are times a specific piece gets updated or we need to pull it from the library to reconfigure. To do that right now, we have to unpublish the WHOLE library and then go back in and re-publish each piece. As our library expanded that “republishing” of pieces becomes more and more tedious. If we just had the ability to “unpublish” a section (like how you can publish) that would make building and scaling a lot easier.

I’d like the possibility to automatically post an update message on Slack every time an update to a library file is published. Ideally the message includes: Name of the library Changelog (user submitted text in the publishing dialog) List of the impacted components This would make it easier for other designers and developers to notice and discuss such updates.

When working in figma in a tight laptop screen, it would be very helpful to have the figma UI be adjustable to be smi transparent like a frosted glass effect adjustable to the degree of how forsted/transparent it is. this will provide designers with more peripheral vision of the screen.

It would be nice if you could conveniently copy and paste from Figma to illustrator. I often create my own icons and custom shapes and it’s really annoying that I have to export these elements to files and import them in another program to fix or modify them.

TL;DR Link to frame breaks when it is moved to another file/frame In a big company with many designers, IT analysts and developers, we found out that best practice for developer handoff is to link Figma frame to Jira ticket, so developers don’t need to search through dozens of files, pages and frames to find what needs to be implemented. No problem till now. But as designers, we have many versions of different screens in a different state and after a while, it becomes quite a messy place. So we want to clean up the space, group workflows and move it to other pages or to other files (i.e. designed workflow is small at first so it is laid within bigger group, but it grows in time so we need to move it to another page/split it into multiple files). But when we do that, we break all links in Jira, so either developers can’t find the right screen when needed, or we need to invest excessive time to change all links in Jira, which can vary from tens to hundreds of screens. Does anyone else ex

When exporting variant names, the file name becomes a combination of all the variant properties. There is no way to control the variant export name, which is especially difficult for developer hand-off. In this example, I have a back icon variant group (Named “Back”) containing both an Apple and an Android variant of the back icon. If I then go to export the Apple variant as an SVG, The variant export name then defaults to “OS Type=Apple.svg” It would be even worse if I had multiple properties. For example, having two more properties could result in a variant name export as “OS Type=Apple, Direction=Left, Style=Line.svg” This is a very poor naming convention, especially for icons. What I would like to have is the ability to control the name given to each variant export. In the above example, I would like the Apple icon to export as the name “back.ios.svg” and the Android icon to export as “back.android.svg”. This way, our developers can export assets as needed directly from Figma wi

Z-index, the order in which layers are stacked, is missing in Figma. I would so like to have tooltips, dropdown menus, etc. get on top of all content, no matter where it is put in the layer list...

Currently there is a huge limitation in prototyping possibilities because any dropdown menus appear underneath the following element in the autolayout flow. I can’t remove autolayout because it would break designs across all useage of design system components and we can’t properly demo prototypes. Anchored by the lack of a customizable z-index property.

For an product I’m working on, the design team has a system used by all designers. We hand-off designs both in english and arabic. So all components and pages need to support switching the initial english (left to right alignment) design to arabic design (right to left).Currently, I handle this in the following way:English font is [x] and arabic font is [y] → add the font names as typography variables to switch between Text direction, english [ltr] and arabic [rtl] → manually handle or use a plugin like RTL layout Components for english [ltr] and arabic [rtl] view → eg list, checkbox, header → add layout direction variants to change multiple elements direction to right for arabicThe problem with all of this is that it’s a lengthy process which is not scalable. The ideal solution would be that when a language is identified and set as a property/variable/setting, then on each element/frame figma smartly set the right rtl expectation → text direction right aligned, set font and it’s sizin

As the title suggests, it would be terribly useful to be able to reset just the padding override for a specific component instead of having to hit reset all just to be able to set the padding to “inherited from master component” and remove any overrides.

If I apply a color style to an object as a fill (or stroke), I can’t apply any additional fills to that object. I also can’t change the opacity of that fill when it’s tied to a style. Example: I have a button that is a frame with a blue background which is tied to a color style. I want to create a hover effect for that button by adding an additional 10% black fill on top of my blue color. Currently to accomplish this, I have to detach the blue from it’s color style, then add an additional fill black on top of it and reduce the 2nd fill’s opacity to 10%. See example screenshots below. This not only breaks my blue color style, but if I have black as a style in my design system, I can’t use that color style either. Has anyone found a workaround for this that I’m missing?

I was playing around with the idea of using variable modes to easily switch between using Latin script and, say Arabic, but where I think I’m let down is having to manually change the text left-right-center alignment. Thanks!

It would be very helpful if we could accept library updates per page, so that we can exclude some pages from being updated (ready for dev) while accepting the updates for other pages (design WIP pages). In our Figma files we have separate pages ‘Ready for dev’ to which no changes should be made after handoff. But we want to continue designing on other pages in the same file (working on new iterations), so we want to be able to accept component updates from the library. But these updates are automatically applied to every page in the file, which means the ‘Ready for dev’ designs are also modified and sometimes even break. I do not want to have to make a separate file for every time I hand over a design, because I want to keep all designs for a specific feature together in 1 file. A solution would be to be able to accept library updates for specific pages rather than all pages. What do you think about this? Similar (closed) topics that I’ve found: Component updates limited to a page Exc