Got a feature request or product idea? We're all ears!
Recently active
There are some fields that we would love to get included from the API, I know there’s a lot of data, but maybe we can add a list to vote between the most relevant ones. I feel that some missing fields make unusable the ones that you expose, for example: Constraints details contain the horizontal and vertical attributes but does not contain the option if the position is fixed when scrolling For reactions, although not documented, the API supports ON_KEY_DOWN, but does not specify which Key
I would like to do this programmatically through the Figma Plugin API, currently, there isn’t direct support for toggling the “Fixed Position When Scrolling” property. This is a manual setting that users must configure in Figma. The plugin API provides limited access to interact with the Figma interface and prototype settings. And would be a huge help in creating plugins to assist in prototyping.
Imagine if Figma and FigJam could find, open and show anything from a workspace (account), organization, or community from canvas and on the canvas. Think of it as a mini optimized LLM masked as powerful Super Duper search for Pro accounts. No need for folders, collection or anything else to organize resources in a hierarchical way. It can even suggest action based on search queries, like auto favorite files etc. This is a concept and it’s easier said than done right and implemented for our community. I’m sharing here after the prompt from Figma on Twitter. Curious to know what everyone thinks and how we can make this even better.
I noticed when adding multiple colors on a gradient that is very hard to distribute evenly. It would be great if we could distribute evenly across the gradient. Even better it would be nice to have a feature to add a specific value on the line… eg 50%, 75% etc.
When using a Figma prototype, there should be a way to disable the ability to navigate through screens via left & right keyboard buttons. Some research participants are inadvertently skipping through the prototype this way, rather than clicking hotspots. Is anyone using a plugin or workaround to help solve this?
when I want to add overlay on the autolayout, auto layout is cracked, overlay pushing existing autolayout I tried to place overlay on the autolayout, and found a way. First, make group with autolayout using ctrl+g Second, make another group with overlay and autolayout using ctrl+g Third, place overlay on the autolayout by dragging it. you should use Layers hierarchy of left siderbar
Could you please allow us to use Ctrl+W to close the preview window? Or could you at least change the preview shortcut to something less likely to be pressed by mistake? Ever since the Preview feature wasn introduced, there has always been this frustrating loop where I 1. press Preview shortcut (Shift+Space) by mistake and 2. press Ctrl+W by reflex ending up closing the whole design file.
Problem: Designers need a better way to organize the versions of their designs in order to keep a clear, organized history of the design process. Current Situation: Each time we receive feedback on the designs for a project, we create and label a new page. Depending on the project this could be 10+ pages with only slight variations and no where to leave notes. Not to mention depending on how the file is organized links can get messy very quickly. Proposed Solution: Leverage the existing Version History tool so users have a designated place for each iteration or round. Allow designers to share out a link that will allow stakeholders to comment for a certain period of time after a review. Once that time is up and all comments are captured, the entire team will have access to this version for reference. (Comments will remain with each respective version for reference).
We are currently moving away from multiple tools and would like to use FigJam. Currently in the stickers library there aren’t a lot of technical stickers like: Server Database PC Would be super helpful if they would just exist, makes life a lot easier instead of pasting them from the internet. Could be a small quick-win for you and us 😃 Cheers! 🍺
It takes a long time to choose a typeface, especially when you need to reject typefaces without Cyrillic support. Adding a filter in the font library makes work for Cyrillic users much faster.
What I wish for the future is that I am able to have a library component (external file) in a file and can perpetuate changes locally, but also inherits updates from the external file (i.e.: design system). Basically a blend of local component and library component. The use case: I take an asset library component and use it on my current file, I make some changes to text and style and re-use it across the flow of screens I’m designing. When I make a change to any of them, nothing happens, they are completely isolated from each other despite being a component, so I am left with two solutions: Detach to make it a local component and lose all the variables Do the hacky workaround and lose future updates from the design system file A nest component would perpetuate local changes, but receive updates from source file
Dear Figma Team, I hope this message finds you well. I am writing to share a feature idea that I believe would greatly enhance the user experience within Figma. As an avid user, I often find myself utilizing external tools like Loom for screen recordings while working in Figma. While Loom’s comment feature is helpful, I often find it more convenient to have comments directly within the Figma platform itself. My feature request is to introduce an integrated screen recording and commenting feature within Figma. Instead of a traditional video recording, this feature would capture a recording of my cursor movements within Figma, allowing other users to follow along as I navigate through the design file. This interactive recording would facilitate better collaboration and understanding within the design process. Furthermore, this feature would enable users to leave comments directly on specific screens or elements within Figma. By allowing contextual comments within the design file itself,
Users with high level of Figma’s forum trust can group / unit / format with adding your ideas topics with similar types of ideas, to make forum more readable
My team is a big fan of Figma, and we hope to add a time interval for permission control in the permission management window. When the time expires, the permission should automatically be revoked. This would prevent the need for manually toggling each person’s permissions. Additionally, it would be helpful to export a summary list of all current team permissions, making it easier to monitor who has access to projects. Thank you! ❤️
Hi! I have been using the FigJam for about 1 year for tutoring math and now it has become worst expirience. Because every digit & every symbol that I write convertes into random squiggle. I kindly request to revert this feature OR make two possible states: hardsmoothing and softsmoothing or somethng like this 🙏
For my use case we have multiple projects in Figma, these are used to differentiate the front-end device that we design for, also our differing brands. The issue is a lot of our files are named exactly the same as the features are shared between our devices and brands, and I’m hoping there could be a better way to differentiate these files by the project they belong to in the Recents gallery. I could add a prefix to the file name but this makes the file name in the top tabs unreadable.
Hi, in my team we use a lot the comments tool and we really appreciate the improvements. Still, we are lacking an important feature, wich is saying to who in the team we are refering the comment. For example, we have a design team and a developer team. We sometimes had the problem that we see there is a comment (aka, something to change or fix), but when we search for it, we see it’s only for the dev team (we are the design team). We can’t hide it because it would also hide for the devs, wich are the ones that need to see it (for example a note or an observation of how the database works with a particular component). It would be much easier if the comments has like a color or tag for each team, to improve the visualization. Maybe going further, such as giving tags more specifics (for example, a comment for the ui team inside the design team, or the animations team inside the design team).
It would be nice to be able to change default px unit to other units such as em or rem. When designing for web, having the option to use em or rem units on Figma would save a lot of coding time afterwards. 😀
Heya, I’m 'loving the high-five interaction on FigJam, but the hand position might be off. In the current version, my hand (white) suggests (based on the palm line, and thumb position) that it’s facing me, contrary to the real-life perspective — or the traditional hand cursor.
Ask: Please consider allowing share links to open in the native desktop app vs. the browser for users who have access to the desktop version. Problem: Often Figma links are shared multiple times throughout the day and in each instance of this a new browser window is opened using considerable amounts of CPU memory allocated to the browser window/tab. This is inefficient especially if a designer already has the file open in the desktop app.
I often place my work inside a parent frame, that is styled for presentations. I would like to link directly to a nested frame within. “Link to selected frame” only allows linking to frames that sit directly on the canvas. Please support at least one level deeper.
This has been an ongoing issue in my current job and my previous job (in Sketch as well, so to be fair its not unique to Figma.) I’m not sure it qualifies as a bug per se because it is “technically correct,” but that’s cold comfort because the font CSS we get from Figma has always been unusable. I can’t convince our website that it’s “technically correct” 😆 so I’m calling it a bug for our purposes! I’m hoping either Figma would consider allowing for some options to adjust its font CSS output, or the community could let me know if a plugin could possibly fix this (even if I had to commission someone to build one for me.) Its strange because the font CSS Figma outputs has always been incompatible with our webfonts, and yet I’ve only found a couple other people outside our company with this same problem. The issue is not unique to the “Motiva” font, we fought with another font in the past and the new font we want to implement in the future will still have this problem. I’m told th
Currently when I hit command + w to close a prototype it is currently shifting focus to the file in the tab to the right of the prototype, which is not the file the prototype is from, which is usually to the left of the prototype in the tabs. I guess it does this as default behaviour for closing a tab is to shift focus to the tab to the right, mirroring what web browsers do. I am testing how a layout looks with a video added, so I am opening a prototype up all the time to get a simulation of what it looks like, then closing it pretty frequently. It feels pretty annoying to constantly have to manually shift focus back to the correct file on the left.
I’m use this (AfterDelay 1ms)trick really often when doing basic smart animations/transitions…Default after delay value is 800ms and I never use it 🙂 May be in settings, or just shortcut button 1ms next to the value fill as an idea…
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.