Suggest a Feature

Mapping out flows as part of UX design is critical. There are plugins for this, and we can copy shapes and connector lines from FigJam into Figma… but they can be much more accessible than they are today. In current state, I need to open a FigJam file every time I design so I can copy stickies, shapes, and connector lines into my Figma file for annotation and user flow mapping. It would be great to just have this toolbar directly accessible in Figma files, too!

When creating hand-off documents I like to showcase user flows by using arrows between different UI elements. I have to use plugins to create these arrows at the moment. When playing with Figjam I notice it had a connector option - this is great. I would love it if we could also have this connector option inside Figma as it would be a HUGE timesaver for hand-off. I would like to think this would be a super easy update given that we can already edit connectors inside Figma. We just need a connector button in the toolbar like so:

Currently, if you copy + paste a figjam flow into a Design file, the Connector Lines stay fully functional – they stretch and adapt as you move their origins and destinations around the canvas, and you can move their origins and destinations to your frames, components, etc. I’ve been using this to show user flows within my UI designs, not only for ease of sharing with other teammates (no need to give in-depth walkthroughs), but also for easily identifying missing states within a flow. It would be great if a) the Connector Line was added as a tool to Figma Design, or b) basic lines and pen vectors had the option to act as connector lines – attaching to anchor points on objects and components, scaling when the endpoints were moved, and able to be adjusted with mid-line handles.

At Fill color, we have solid-gradient-pattern-flat image-video-shader 😀 Please add a 360 panorama image. 🤓 And please add features specifically for viewing panoramic images. For example, a minimap with a marker and a radar that rotates based on the viewing directionThanks

Our workflow is to decline all license requests that users make in the app.We require all users to create a ticket in Service-now and after getting approval from the appropriate Finance Director to manually approve the appropriate license (Full, Dev or Collab).I’m requesting a way to set all license requests to “decline” and tailor the email response to detail how to open a ticket for the license request.

I think Figma should let users customize the color of a strikethrough independently, rather than automatically matching the color of the text. This would give designers more control over how the strikethrough is visually presented.

Hi there.I create a new thread because this one is closed: Like many, I do my resumé with Figma. And I’ve seen that the text exported PDFs have undesirable spaces inside the words.Example:Copy/paste this text and you get:“with 2 0 + years of e xperience”, which is wrong!! Of course, the MKitFPDF plug-in solves some problems but brings some others, without to say it’s not free.Did someone got a real fix for this?

what about having lines to represent if the colors are accessible or not in color picker, so it’s easy for designers to check for accessibility before even choosing the colors, and when getting colors from styles there a filter in the dropdown for accessible ones

Hi there!I embeded Figma prototypes into a SharePoint Teams website. I successfully hid the Figma UI, but I’m noticing some white padding around the prototype. Is there a way to adjust or remove this padding by tweaking the iframe code, or is there another method I could try?The extra white space is affecting the website layout, especially on smaller screens. I appreciate your help with this!Thank you! A

What problem does this solve?Kiro (by AWS) is already listed on the Figma MCP Catalog as a supported client for Figma Design and FigJam. It connects to the remote MCP server at mcp.figma.com and works great for the design-to-code direction using get_design_context, get_screenshot, get_variable_defs, etc.However, the generate_figma_design tool (Code to Canvas) is currently restricted to only Claude Code and Codex by OpenAI. This means Kiro users can pull designs from Figma into code, but can't push generated UI back into Figma — breaking the bidirectional workflow that makes Code to Canvas so powerful.What's the use case?Developers using Kiro generate HTML mockups and UI prototypes as part of their development workflow. Being able to send those directly to a Figma Design file would let designers review, iterate, and refine without manual recreation. This is the same workflow Claude Code and Codex users already enjoy.What's the ask?Add Kiro to the approved client list for generate_figma_

Type sizing consists of mainly dropdown presets, and manual input (type the size) There is a 3rd option, but it so difficult to select, and that is resizing using drag. When placing the mouse over the border to the left of the type size, a double arrow appears and you can drag up and down on the size, but the active area is only about 1px wide and it’s almost impossible to use. Can you widen the active drag area like on the layout width box?  This is particularly useful when a selected work can be resized dynamically to match the width of a different word above or below. 

I have been playing around with Figma Motion since it launched, and I am really enjoying it. It already feels like a solid first release, but there are three features that I wish it had.Voice-over recordingBeing able to record voice-overs directly in Motion would make creating walkthroughs, presentations, and design reviews so much easier. Right now, you have to export your animation and finish it somewhere else.Audio importI would also love to import audio files into the timeline. Whether it is voice-overs, sound effects, or music, audio is a huge part of motion design. Keeping everything in one place would make Motion much more practical for demos and marketing content.Morph animationsMorph animations do a lot of the heavy lifting in presentations and motion graphics. They are probably one of the biggest reasons PowerPoint is still the go-to tool for so many presentations. They make transitions feel intentional, help tell a story, and add polish without requiring complex animation sk

Dear Figma Team,I am a designer who regularly works with 750px-based design files (a common standard in mobile design, especially for iOS @2x/@3x export workflows).Currently, when I need to export assets at different scales, I have to manually add export settings in the Export panel each time. This is time-consuming and error-prone, especially when working with many assets.Feature Request:I would like to suggest adding Plugin API support that allows plugins to: Programmatically add export settings to a selected node's Export panel Set custom suffixes (like @2x, @3x) for each export configuration Configure export scales and formats through the API Use Case:When working with 750px design files, I need to export: 0.5x scale (375px) with @2x suffix 0.75x scale (562.5px) with @3x suffix If plugins could modify the Export panel, designers could create custom plugins to automatically set up export configurations based on their design file dimensions, significantly improving workflow eff

https://developers.figma.com/docs/rest-api/library-analytics-intro/ I’m a sole PIC of design system, I’m conducting quarterly Design System Health Score to determine whether the design system actually works and used by the design team, it helps us quantitatively measure the impact of our design system. Currently my team uses organization plan and I think I can’t access the library_analytics:read permission in this plan, while the organization plan supposedly mature and big enough to actually uses analytics data as primary data, so my suggestion is to open the library_analytics permission to organization plan.

Hi Figma team,My team and I have been experimenting with slots recently. I'd like to propose a feature enhancement: when a component with properties is added via a slot, those properties should be accessible directly from the main component.Ideally, these nested properties would surface automatically, eliminating the need to click deep into the component hierarchy to make edits.

It would be really great if can add tools like Eraser, Pencil tool supports to illustrating(current one does not support when customizing existing elements). Basically tools from Illustrator. Figma is way more easy than using Adobe illustrator, but with the current tools its limited.

I think Figma's Brush tool has a lot of potential, but currently feels quite limited compared to dedicated painting tools.I'd love to see a more advanced Brush system that could include features such as: Adjustable brush size, hardness, opacity and flow Pressure sensitivity Stroke smoothing Spacing, scattering and rotation controls Custom brush shapes Eraser and smudge/blending tools The ability to create, save and organize personal brushes Brush presets and custom brush libraries Community Brush LibraryI think the biggest opportunity would be connecting custom brushes with the Figma Community.Designers could create their own brushes or brush packs and publish them to the Figma Community. Other users could then discover, install and use those brushes directly in their Figma projects.This could create a whole ecosystem around brushes, similar to other Community resources.For example, the community could create: Texture and grain brushes Ink and pencil brushes Pixel-art

I would like to ask: are there plans to introduce such a feature (tool) for Figma Draw as an eraser in the future? For example, it could easily erase unnecessary vector graphics down to the smallest detail. That is, I mean the eraser, which is have for example, in Adobe Photoshop and MS Paint.

Working in Motion I have to click back into Design to then get to Prototype but I work closly with Motion and Prototype so it would be great if I could stay in Motion and just click a Prototype button on the top to switch back and forth like I can when in Design mode. 

When presenting in Figma Slides, I would like the smart animate transition to be played even when going back to previous slide. Currently smart animate is only played when advancing to next slide, but not when going back to previous (then it’s just an instant change). This behaviour would not have to be the default, but having the option would be nice.

Hello! Is there a way where we can cherry-pick which changes made in the branch are going to be merged in the main file?

Since Figma introduced vector Pattern fill, it works pretty nice, yet there are some limitations and missing features. API/MCP supportClaude does really good work generating lots of patterns, yet it doesn’t understand well the underlying mechanism around it With further investigations, it looks like the API doesn’t support generating fill type `PATTERN`node.fills = [{ type: "PATTERN", sourceNodeId, tileType, scalingFactor, spacing, ... }] throws a discriminator validation error. PATTERN is absent from the accepted set, which currently lists SOLID, SHADER, the four gradients, IMAGE, VIDEO. Reads work fine, so the type round-trips as data but can't be written back. Even re-assigning an unmodified pattern paint read off an existing node fails. createPaintStyle() accepts the call and silently stores a SOLID instead. The silent degradation is arguably its own bug and worth mentioning separately, since it fails without erroring. clone() preserves pattern fills correctly, which shows the unde

A great feature to have is text styles not breaking when a designer is using Cmd + B to bold a word or phrase. Currently it unlinks the text style and applies the bold to the underlying font. It would be great if there was a feature where when I use Cmd + B, it swaps to that text style in the library (where the style already exists) and updates in the property panel as well.

So, with the new beta implementation of shaders, I had a question since, you know, typically shaders are coded (which I assume is the work that the figma agent is replacing in this case) Is there any plans to make the Figma shaders coded instead of generative?

The current seat upgrade request process does not provide users or organization admins with enough information to make informed decisions or manage temporary seat requirements efficiently.Three improvements would make the process more transparent and significantly improve license governance: Make the request explanation mandatory Users requesting a paid seat upgrade should be required to explain why they need it. The request should not be submitted if this field is empty.Ideally, the mandatory explanation would cover: The project, client, or internal initiative The functionality for which the seat is required The relevant team or responsible project lead This would give admins the business context required to assess the request and reduce the need to contact users individually for clarification. Explain seat functionality and cost implications The upgrade request interface should clearly explain what each available seat type enables before the user selects it.For every seat type, F