Suggest a Feature

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.

I’m a designer at a large e-commerce company. I introduced Figma to a team that worked exclusively in Adobe, and I’m now leading an organization-wide shift to make Figma our primary tool—for web and print. We’re building a label-automation workflow entirely in Figma, and I believe there’s a big product opportunity for Figma here.The problemEnterprise security policies (ours included) often block Google/Microsoft data sharing, so external connectors aren’t viable. Yet modern print ops—labels, care tags, manuals, packaging—are data-driven at scale. Adobe tools have been hard to automate and to collaborate in; Figma is the only environment that fits our collaboration + automation needs, if key print/data features are native.The opportunity for FigmaA secure, file-scoped, on-canvas data + print-ready export workflow would let commerce, manufacturing, logistics, and retail teams run high-volume print production inside Figma, expanding usage beyond design into ops, QA, vendor management, and

I was super pumped to start using grids for my layouts until I learned of one fatal flaw that killed my excitement :(  The inability to set a row height to hug is simply a deal-breaker for me. Also no variables support for gaps? really?

Migrating over to Figma. Literally found a limit within 2 minutes. In Figma, you can’t end a line with an arrowhead on one end, and a circle or dot on the other. Illustrator has been able to do it for 25+ years. Sketch can do it. Even PowerPoint can do it. But Figma can’t? On the Figma dropdown menu, it mixes up caps with ends. Round and Square are caps. Line Arrow and Triangle Arrow are ends (or tips). Nothing else can be done except arrowheads. I make a lot of wireflows, so this seemingly small thing is actually a big annoyance for me. Has anyone else noticed this?

As a developer I want to be able to generate images based on the template of the designer. I want to be able to use the placeholders in Figma Buzz to dynamically add images to generate a design with variable content. 

Please make Dev Mode Annotations visible by all roles, not just Full Dev Mode seats. This can become costly for users needing context but not all the other dev-mode features. Here’s the scenario: We have a dashboard, with cards showing a customer’s account status. This status can be mapped from multiple back-end statuses, to show just one front-end status. For example, any of the following could be mapped to a single status known to the customer as “Completed”: canceled, terminated, sold, complete, etc. This is something that the developer needs to reference, but then also the PM needs to reference in writing tickets (who doesn’t need full dev-mode access), the QE needs to reference for testing automations, and various other individuals on our team. Placing it in a comment makes it less clearly attached to the specific piece of the design, and requires us to keep documentation dispersed among different tools (Jira, Confluence, Figma etc). Simply making Dev mode annotations visible to v

Hello folks,I do feel like we need to greatly power up the ways to organize styles specially when it comes to typography, specially thinking in terms of design systems and shared styles. Any improvements there are very welcomed, things like:Personalized order of styles per user ( maybe use AI to offer some help )  Nesting os styles beyond an exposed list, menu style with mouse tunnel and all would still be better in cases of more complex systems. Maybe add the another option like in variables: All, In this files, and than add list the sets for user to pick which one he wants to single out. More power here would be very good.Give us options, and I apologize bring this up but I feel like even Sketch at times gave us an easier to consume approach to this. Also:1-% and ems values for variables. WE BEG. 🙏🙏🙏🙏🙏🙏2-Component level tie up of component variant name to Mode ( Desktop/Mobile), so we don’t have to sync up a component property value to modes every time we reuse one. Best

Hi Figma team,I'm reaching out with a request on behalf of several developers on our team who use Linux as their primary development environment.Currently, the MCP (Multi-Context Preview) feature is locked behind the Figma desktop app, which is only available for macOS and Windows. This poses a challenge for Linux developers who are unable to access or use MCP due to the lack of a supported desktop app.We’d love to see one of the following: A Linux version of the Figma desktop app to unlock parity across development environments. An alternative way to run an MCP server without the desktop app, such as a standalone CLI or server binary that can be installed independently. This would greatly improve the development experience and make Figma’s workflow more accessible to cross-platform teams.Thanks for considering this request!

Hey everyone, I’ve been scratching my head trying to figure out how to download videos from Snapchat without running into trouble.I know the platform’s all about privacy, so I don’t want to risk my account or someone else’s content. Are there trustworthy apps or clever tricks that actually work for saving videos from snaps or stories?Also, does it matter if it’s a private snap versus a story?I’d love to hear personal experiences, tips, or even warnings about what not to do.

Seems you can only add numbers or strings to text layers. It would be great if you could output a color value as text. It’d be really useful for setting up a style guide template that can be updated to different themes.

Hello,At my company, we have an Organization license that allows us to save custom fonts directly in the admin panel.The problem is that my company is a multi-brand company, and its brands change over time.Because of this multi-brand management, the font admin panel is not well adapted to our needs. I need to create folders or categories to separate the different fonts by brand. We currently have more than 50 fonts to manage.When there is a rebranding, we have to remember which fonts and weights are used for each brand, which is very difficult, and delete those ones.Please consider to add folder management, at least 1 level of folder. Thanks  

Hi, I often work with complex components that need to be updated. Some are very complex. I would be very happy to be able to use the "Review updates" window in fullscreen.Or am I the only one? :)Thank you

Hey! How can I transfer the AI generated Prototype in Figma Make to Figma Design and continue editing it manually there?

… not fake elements that look like links. The reason why is because someone posted a link to a Figma file inside a Figma comment, and when I tried to open it in a new tab (making sure I’m holding Cmd in macOS, same as Ctrl in Windows), it just opened in the same tab as the Figma file I’m currently viewing. It’s also impossible to right-click the link and get a link-related context menu. It’s not possible to easily copy the link too. Right now what we get is a regular browser context menu. Worst parts are: The draft comment I wrote was completely lost because of this navigation. There was no warning, and it wasn’t saved to be restored later. The back button doesn’t work. It doesn’t take me back to where I was. It just reloads the linked page, and then the back button is fully disabled. I had to go find the previous location myself manually. PS: On that note: Please also reduce the label of long links to be truncated with ellipsis in the middle (max 2 lines).

Many people have said the same thing, but I’m here to recommend supporting percentages within auto layout. I’ve seen many people asking for the same thing.Percentage width auto layout would help us be more efficient. Auto layout “Fill container” is great for sections being sized equally (50/50 or 30/30/30).When we’re designing content with sections, the sections are generally not the same width as each other to indicate importance.Myself and many other designers would love to have autolayout support something like this:The main container has the same spacing all the way around Each section takes up a specifid percentage of the container (70% and 30%) When the modal grows and shrinks, those sections maintain their width of 70% and 30%  Without spacing With spacing 800px wide     1000px wide      This is what autolayout currently supportsIf we use auto layout, each section must be a specified width or the same width as the other sections.  It makes

Hi! I’m trying to create an “author credit” component to document a design system. The component has a link to the original resource. All text will be set using component properties. Is it possible to create a property so the link URL is filled in the instance instead of using overrides?

With all the new AI features in Figma, the only thing missing is generative expand. If we could reframe or crop images and have the tool generate the additional sections of the image—allowing us to freely change aspect ratios—it would be game-changing and bring Figma closer to becoming the true Photoshop killer.

Having a rolling slide deck always being the source of truth (without the need to create copies) makes it super easy for business use - however we are largely unable to actively work on slide changes in these existing documents because of the risk it’s currently being viewed or presented.Being able to create a hidden branch and merge back into the main document (same as Figma Design) would make handling changes a breeze.

With the new update, we have a great new feature, but unfortunately, it’s not usable with our component structure. Exposing all props of a nested instance also exposes props that we don’t want in the context of the consuming component. What if we could also select which properties to expose? This would lead to a cleaner sidebar with only valid props.

before 🤗Previously, you could generate a [no expire] tokennow 😔If users rely on tokens to access the figma open api, forgetting to replace expired tokens can cause serious problems.The expiration date of the limited period will cause the figma token to no longer have usage value. 

Managing local variables is pretty cumbersome and buried in menus. Bringing over the variable window found in Figma, would be big help in managing local variables.

Figma supports enabling/disabling some OpenType features from the UI.https://help.figma.com/hc/en-us/articles/4913951097367-Use-OpenType-features From the plugin API I can see which features are being enabled withhttps://www.figma.com/plugin-docs/api/properties/TextNode-opentypefeatures/but the property is read-only. How can I programmatically enable/disable some OpenType features?Also, is there a reason why it’s accessible on UI but not Plugin API?

HiAs a maintainer of our Figma team (not admin tho) I was wondering if there is any possibility to access Figma Make analytics to understand the following:How many Figma Make files have been created? Which designers/teams are creating Make files? How many prompts are being used in which Make file? Thank you

We need a way in the REST API to get a list of Team IDs. A previous post (Suggestion: API endpoint for :team_id) was moved to ‘share an idea’ and then marked as solved, so I’m reposting sans solution, in hopes that we can get some votes. With the new library analytics API, this feels more relevant than ever. I want my users to pick the team their library is in from a list, and then pick the library file from a list of files. Trying to get end users to figure out how to get the library file ID is needlessly complicated to start taking advantage of the new API, when I could set up a system to let them pick it from a list. Almost all of the endpoints require a Team ID… (or require a file ID, the list of which requires a project ID, which requires a Team ID… etc.) So adding a Team API would unlock improved usability for almost every other REST API endpoint. Let’s make it happen.