Got a feature request or product idea? We're all ears!
Recently active
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.
Figma’s file browser always resets the sorting to Last modified, even after I select Alphabetical. This happens when I refresh the page, reopen Figma, or navigate between folders.This makes it difficult to create and maintain an intentional folder structure. For example, our folders are numbered to communicate a clear hierarchy:01 Websites02 Campaigns03 Pitch decks04 BrainstormsThis structure only works when the folders are displayed alphabetically. When Figma automatically switches back to “Last modified,” the order changes whenever somebody edits something, and the carefully designed structure is lost.Please either: Remember the user’s most recently selected sorting option, or Add a setting that lets users choose a default sorting method. Ideally, the preference could be saved globally or individually for each folder, since different contexts may benefit from different sorting methods.
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.
Great to see the addition of dividers. Would really love the ability to add a name for each divider, because this still doesn’t solve the issue where we need to create an empty page titled “{Section Name}” to call out what the divider is actually dividing.
Hello Figma! I was wondering if you could add this small feature called “Text on path” making bending much easy. It could also be better if it can merge with the frame so that it can add bg colors to it
I’m working on a complex product that has a lot of business logic and design decisions documented in Confluence.I’ve hand-picked and linked relevant documentation to components in Dev Mode, using the “Dev Resources” field. This can be used as context by coding agents accessing through Figma MCP, which is great. But now I found out, that Figma Design AI can’t see and use it. I have to make it find the documentation by adding a search step to skills and prompts or looking it up myself and linking it there. This feels wrong and like a waste of either my time or AI tokens.It’s already great, that Figma AI is able to access our documentation. But it would be even better if the actively curated context of “Dev Resources” was accessible to it.
When i move my design elements/frames/etc., I expect all the pinned comments to move with them – but they don’t. instead i’m left with a bunch of floating comments (that are not attached to anything), which requires me to manually re-read each comment and move it again to its correct place. this is frustrating and time consuming. but what’s worse is when another user forgets to move the comments after they move the design elements, so when i return to the Figma file it’s very difficult to decipher the floating comments because they are not pinned to anything so i have no idea what they’re referring to. please keep Comments pinned to design elements (so moving design elements automatically moves comments).
Sometimes, the smallest UX improvement makes the biggest difference.Here’s a small UX problem I came across while working with icons in Figma.When you have a large icon library with multiple styles and color options, scrolling through the list can quickly become confusing.You scroll down…You see a lot of icon styles…And suddenly, you don’t remember which icon style you’re currently looking at.💡 What if the icon style heading stayed sticky while you scrolled through that section?The interaction could work like this:→ Icon Style A stays pinned while its icons are visible.→ Once Style A ends, Style B takes its place.→ Then Style C.→ And so on.Just like sticky section headers in many well-designed interfaces.It’s a tiny interaction, but it provides something very important: context.Good UX isn’t always about adding more features.Sometimes, it’s simply about helping users answer:“Where am I right now?”This is a great reminder that even a small interaction can make a workflow feel significa
Enable Figma Links (page/selection/node) in prompts for Figma Make.Figma Make should be able to connect to our design files and reference the design instead of relying on an image. Using Figma URL into Make and it can read the structure and styling directly Figma Make should be able to detect Code Connect (like MCP) and use React components
Figma Make: From AI Generator to Trusted AI Product Development OSI’ve been using Figma Make extensively and thinking about what the next evolution of AI-powered product development could look like.First, I want to acknowledge that Figma has already made significant progress with Make, AI models, skills, design-system context, editing, code workflows and agent capabilities.My feedback is therefore not simply “add more AI features.”I believe the next major challenge is trust, control, verification and orchestration.Today, the basic experience is often:Prompt → AI generates → Designer reviews → Prompt again → IterateI believe the next evolution could be:Understand → Plan → Confirm → Design → Build → Verify → Test → UAT → Approve → Release1. AI Planning & Understanding GateBefore Make starts building, let AI first analyze the request and create an understandable plan.For example:AI UnderstandingProduct goal:What I believe you are trying to achieve.Users:Who I believe will use it.Requi
Please enable this feature in text links. Currently, to copy a link, you need to click on “Edit” and then press cmd+c.I suggest adding the “Copy to clipboard” action to the interface of the drop‑down window. This will eliminate unnecessary steps.
The UI can get over crowded with annoying frame/component names hanging off their top edges. I have not found a way to disable/hide these. Please tell me there is a way! 🙂
The blue interaction box is helpful for prompting which elements can be clicked in a prototype. All components with interactive states, even just hovers, now have blue interaction boxes - even when they don’t really do anything useful like navigating or launching a modal. I’d like some level of control over which variant interactions are visually prompted, or some smart defaults (which Figma is awesome at, thanks team!)
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
Hello Figma Team,I would like to suggest an affordable “Designer + AI” plan specifically for individual and freelance designers.Many individual designers mainly need Figma Design and AI features. We may not need multiple seats or extensive team collaboration features.It would be great to have a plan that includes: Full Figma Design editing Professional design features A reasonable monthly allocation of AI credits The option to purchase additional AI credits when needed No need to pay for unused team/collaboration features For example, a plan around $5–10/month could be very useful for freelance designers, independent creators, students, and small creative businesses.I currently use Figma mainly for design work, and I feel that paying $20/month for a Full seat can be expensive when my main requirement is Design + AI.A dedicated “Designer + AI” plan would make Figma much more accessible to individual designers and could encourage more designers to use Figma’s AI tools.Thank you f
BackgroundI am trying to build a mini wikipedia like website with lots of cross-linked articles.ProblemWhile I work in CMS editor, Figma Sites tab becomes very laggy, because of frames updating with things from CMS.Proposed solutionI feel like we could have a CMS editor separate from graphic editor.That could make editing experience faster,That Figma could also include this CMS editor in the Collab seat, as I have seen at my main workplace the need of analysts for such functionality (they want to edit texts, but full seat is too powerful and expensive for their needs). Or maybe this CMS editor could be as is now, but the graphic editor would not update frames, until you leave the CMS editor mode.It is for Figma’s great developers and designers to deside. So, what do you think, Figmates? Is it a good idea?
This is a feature in Keynote, and I believe it’s possible in PowerPoint as well. In Presentation mode, it would be useful to be able to use right-click to go back to the previous slide (in the same way that left-click advances to the next slide).I use a wireless mouse when I present. In Keynote, I constantly use right-click to go back, because I’m often not close to the computer. This is what prevents me from switching to Figma Slides.This is mostly a feature request, but I’m open to alternative solutions that would solve my problem.
Please can we get percentages for variables? We can use percentages manually, but we can’t create a percentage as a variable. This would speed up my design to dev process tenfold, and considering we can already use percentages in the design, why disallow it in variables?An example is I want store values for line height and letter spacing as percentages which behave responsively/dynamically, so when creating type variables I don’t have to do manual calculations, store 10+ letter spacing/line height values based on which font size they will be used with and hope I never change the font size variable in the future.
Dear Figma Team,I would like to suggest a small but very useful improvement to Figma’s Prototype interactions.Currently, when I select On click → Navigate to, the Destination dropdown displays the available frames, but there is no search option. As shown in the attached screenshot, the list can become quite long when a file contains many frames or screens.It would be very helpful to have a search field within the Destination dropdown, allowing designers to quickly type and find the required frame instead of manually scrolling through a long list.I hope Figma can consider adding this in a future update.Thank you for continuously improving Figma!
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.