Share Your Thoughts

Whenever I create a arrow line, it always defaults to black color with 3px stroke. I often use the arrow line (Shft + L) to indicate any notes/guidelines. Applying default properties like as we do for the text will greatly help with the stroke and color properties for the line aswell. Do you expereince the same thing ? Is there any workaround you could suggest ?

If I add an instance of a component that in its master form is set to fill, and I am adding it to a frame with auto-layout, I want that instance to be automatically set to fill. That instances are always added as fixed width when the master is set to fill is an annoying inconvenience, especially when nested components also get set to fixed, thus requiring a whole process of fixing widths.

tldr; Please add improved user management features which allow quick access to a list of all users who have access to any team file, regardless of how that access is granted, along with the ability to remove or edit that access. This list should include users who show up in the share list of a file with the ‘anyone with a link’ permission selected. Please also add a view which shows all files, across all projects, and their link sharing setting. In addition the list should include the ability to edit those share settings one by one and in bulk via multi-select. the details; It is currently very difficult to audit what files or projects a given user has access to or to see all of the users who have access to your files. Similarly there is no way to view what the sharing settings (anyone with link, only invited people, ect) are for your files without individually viewing each one. I reached out to support to ensure that I wasn’t missing something but they confirmed my fears and asked m

Implement variable font property in plugin API and rest api Unfortunately it is not possible to get the complete properties for variable fonts via API access. Please implement the CSS property “font-variation-settings” for “wght”, “wdth”, “slnt” … “opsz” Or have I overlooked something, how do I get the information via the APis?

I was very excited to hear that grids were coming to Figma. CSS Grid was introduced years ago and brought with it many things that flexbox was incapable of doing, so I was hoping for a similar level of new capabilities here, and I genuinely cannot believe that this feature is being shipped in its current state (even as a ‘beta’). This is a very long post, but I feel like this feature has been implemented so poorly that it legitimately sows doubt in Figma’s capabilities to deliver features in the future.Inability to ‘hug’ contents Both rows and grids themselves are unable to resize themselves to match their contents (‘Hug”). Row heights must be either “Auto” (1fr) or a fixed height, meaning that if you want your rows to be sized per their elements, you’ve now manually defined each row height in px (not even a variable value), and instead of getting a clean CSS output, now you have however many rows defined in exact values, destroying any chance of scalability. This alone makes this fe

I’ve already started using the new slots and I find them amazing, but I think it’s very limiting to prevent the use of grid layout. 

When reusing Auto Layout across different frames or components, there is no way to copy and paste only the Auto Layout settings. Users have to manually recreate spacing, padding, alignment, and other layout properties, or use Paste Properties, which also applies changes they may not want. SuggestionIntroduce a dedicated Paste Auto Layout action that copies only Auto Layout properties. When pasting, a small dialog could let users choose which settings to apply, such as Direction, Spacing, Padding, Alignment, Wrap, and Clip content. This would make it much faster to reuse layouts while avoiding unwanted changes to fills, effects, typography, or other design properties.Addition!This could also work to fills, strokes, effects. ExampleRight click an Auto Layout → Copy Auto Layout → Paste Auto Layout on another frame. A dialog appears where users can select exactly which Auto Layout properties to apply before pasting.  

Describe the problem your experiencing and how your idea helps solve this Every time I enable Auto Layout (AL), the detail setting is set to Hug Contents. I realize that in some cases, it makes sense, but not always. We use the fixed width/height quite often, and changing it manually every time to fixed is pretty annoying. Probably introduce a user setting for default AL behaviour or remember the last setting used. Meaning that if I used Fixed the last time, it would be the initial setting next time I enable AL. Add as much context as possible (screenshots, Figma files, mockups, etc.) AL is a versatile tool, and more flexibility would make it even more user-friendly. Ask questions to bring the community into the conversation (e.g. Does anyone else experience this? Is anyone using a plugin or workaround to help solve this?, etc.

Hi! Please add support for video files in Figma Motion.It would be helpful to import video files, use them in compositions, and animate their properties directly within Motion. Video support would make it possible to create richer prototypes and motion designs without relying on external tools.

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

I think this annotation feature is great, but the documentation isn’t well written. It gives the impression that users with view-only access can see annotations, which is not the case. It would also be very useful to extend this feature to viewers such as PMs or clients, so I can easily show them how a button or function is supposed to work. 

Let us multi-select folders, to more easily re-organize after the new “Folder” implementation. Trying to sort all customers into “A” “B” “C” etc.. folders, and having to drag one-a-time is.. well.. not optimal. (this regards both click and drag + right-click and “move” option) While viewing “all folders” in list-view: Sorting gets refreshed everytime I move out and back in to “All folders”. From alphabetical to “Last modified”. Annoying. After moving x-amount of folders, it stops working. I need to go to “draft” and then back to “all folders” view and then “sort by alphabetical order” to start sorting them again. (bug?) First thoughts and experience with the new feature. Really glad to see folders introduced to Figma( finally! :) )

Hello there, I am currently having issues viewing the guides on my design when the brand colour is pretty much the same as the guides. Take a look at the screenshot. A suggestion for the guides colour:

Hi Figma team, It would be great to add the ability to ‘Reset playhead’ in the ‘State’ section of a prototype interaction. I’m currently working on a prototype for a carousel banner. I’m already using the ‘After delay’ and ‘On click’ interactions to make the carousel change slide automatically, and to allow the user to manually change slide. The transition of slides is animation, so it’s not possible to set the playhead to 0 on these triggers as it would be visible during the transition.  Each slide have a motion animation that should restart when landing on the slide, but since I’m already using the ‘After delay’ trigger, it’s not possible to add this at the beginning of each slide (eg after delay of 1 ms). 

I lack functionality. When I paste a link to a board, I expect to see a preview card, not just the link text. Alternatively, you could make the context menu either a preview card or just the link text when you insert it. I also want to post a link to external sources in conjunction with any FigJam element Thank you. All in all, everything is super!

When I’m zoomed way out, it would be nice if I could press “M” or some other key on my keyboard while hovering on something, and then a 2-3 inch diameter circle would appear next to my cursor, showing a magnification of what I’m hovering on. Then I could let go of the key on my keyboard and I’d instantly be back into clicking and dragging mode. This way, I can zoom way out and organize a bunch of things that need to be lined up next to each other in a grid or some other arrangement, without needing to constantly zoom in and out and find my place again every time. 

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?

Would Figma consider supporting Variables for variable font axes in the future?We're using Google Sans Flex and switch between two visual modes:Formal - `Rond = 0`Friendly/Cute - `Rond = 100`Example of the ROND (Round) axis in Google Sans Flex. We use this setting to switch between formal and friendly typography styles.​​​​​Currently, font axis values such as Round (ROND) cannot be controlled by Variables. Because of this, we have to maintain two separate text-style systems even though everything else is identical.after add rondIf variable font axes could be bound to Variables, we could switch typography modes through Variables and maintain a single text-style system instead.Example concept: Variable Font axes such as Weight and ROND could be connected to Figma Variables, allowing typography modes to switch automatically.This would be especially useful for design systems that use variable fonts to express different brand personalities across themes or modes. 

The Problem:When designers work on a long-term project, using the Figma Agent creates too many separate chat windows. This causes a loss of context over time. Designers get confused about which chat to use. Also, teamwork is harder because different designers do not share the same chat memory for the same design flow.The Solution:Figma Agent should link its memory directly to specific canvas elements, like Frame IDs or Section IDs, instead of linking it only to a single chat window.Key Features:Cumulative Memory: No matter which chat window a designer opens, the AI adds all new information to the history of that specific design flow. Distilled Summary: The AI constantly updates a short summary of the work done, decisions made, and next steps for that flow. Team Sharing: Any designer who clicks on that frame or section can instantly read the AI summary and continue the chat with the exact same background context. Why It Helps:This stops chat confusion, keeps long-term projects organized

Fractional units and hugs are definitely a welcome addition to Grids, but what’s still missing is the ability to assign both the number of columns/rows and colspan/rowspan to variables.We’ve defined our website breakpoints as modes so we can build components that automatically adapt to the viewport (for example, a 50/50 layout that stacks on mobile). Right now, the only way to achieve this is by storing fixed column-width values for each breakpoint and use them in combination with horizontal auto-layout. It works, but it defeats the whole purpose of Figma’s grid system.Assigning variables directly to the grid would allow every component using that grid to automatically adapt based on its current mode (breakpoint). This would make creating mockups across different breakpoints significantly faster and more efficient.

Problem:When a Figma frame contains a video, GIF, or prototype animation, exporting it as PNG/JPG loses the motion. Currently, designers often need to use external tools or screen-record the prototype.Suggested feature:When a frame contains video, GIF, or animated interactions, add MP4 and GIF as export formats.Export options:PNG JPG SVG PDF MP4 🎬 GIF 🔄Suggested UXWhen clicking Export, Figma could automatically detect whether the frame contains animated content.Export as:○ PNG○ JPG○ SVG○ PDF○ MP4○ GIFFor MP4/GIF, provide:Duration: Entire prototype / Custom Resolution: 1× / 2× / 3× Frame rate: 24 / 30 / 60 FPS GIF: Loop / Play once MP4: Include audio / mute⭐ Extra opportunityA particularly useful option would be:“Export prototype flow as video”Instead of exporting just one frame, designers could select a prototype starting point and Figma would record the entire interaction flow as an MP4/GIF.That would be extremely useful for portfolio case studies, presentations, social media, desig

New UI for viewing library filesOur 5-person design team relies heavily on a color-coded visual system for project identification. Each project project uses a distinct color scheme on file cover pages (for example, green for Analytics files and blue for Finance files), enabling designers to instantly recognize and navigate to their active workspaces visually.The recent UI update collapsed project folder views into compact text-based blocks, removing the cover page preview that displayed the most recently modified file. While this compact view displays more folders on a single screen, forcing designers to rely exclusively on reading text labels adds cognitive friction and disrupts fast switching between active files.For me as a design lead and as someone also managing multiple concurrent projects, visual recognition is critical for maintaining focus and speed. Having to read through text links introduces unnecessary pause points when scanning the dashboard.I request that Figma introduce

When using variables, the container below the variable is too narrow,making the content difficult to read and preventing users from distinguishing between text that matches the beginning of a fuzzy search query.  

Allow users to mark fonts as Favorites so they can quickly find and reuse frequently used fonts without searching through the entire font library.How it could work:Add a ⭐/♡ icon next to each font in the font picker. Clicking it adds the font to Favorites. Add a “Favorites” section at the top of the font dropdown. Favorites sync across files and devices. Optionally allow users to reorder favorites based on usage.Even better UXAdd a “Recently Used” + “Favorites” structure:Font picker⭐ Favorites 🕘 Recently Used All FontsThis would be particularly useful for designers who repeatedly work with the same 5–10 fonts across projects. 

I don’t know why did figma launched sites if they wanted to bury it somewhere in the corner and not look at it as a product. I have gone through multiple reviews of people from Reddit to Youtube and everyone is saying that the product is super immature right now from SEO to CMS to animations. So the question is when is the team going to improve it to a point that people that work on Figma can stay on Figma for other work as well?