Let us know what would make Figma better for you.
Recently active
Figma’s products have been developed to add value to users and we continue to want to hear what you have to say! That’s why we’ve created this category - a dedicated category where you can post your feedback, both positive and constructive. Here’s a few points to bear in mind in the Share Your Feedback category:Please keep the discussion constructive, and follow our Forum Guidelines and Code of Conduct Our team will merge topics with feedback on the same subject Inactive topics that are 6 months or older may be closed or archived. We’ll make sure that our product teams have seen the feedback though before closing the topic. Note: If you have product ideas or feature requests, head over to the category Suggest a Feature.
We’d love to hear what feature requests, ideas or improvements you have in mind for any of the Figma products you are using.Note: If you have feedback on an existing product or feature, head over to the category Share Your Feedback. Sharing product improvements and ideasOur teams look at ideas and feature requests across many different channels throughout the product cycle and it has truly helped make Figma a better product.With that said, we want to make sure we set some expectations for how feature requests, ideas and improvements will be handled in the forum.We cannot make any guarantees or promises that you’ll see your idea/feature request/improvement implemented into the product Our team will merge topics with the same/similar ideas to keep the forum organized Inactive topics that are 12 months or older may be closed or archived to help keep the community organized and healthy Voting on topicsAt the moment, it is not possible to vote on topics.This is a feature we are reviewin
When I write create long paragraphs with text tool on the Figma I get the unnecessary spaces on edges of the paragraph like below. But I think if there a hyphenation feature (like Adobe Photoshop) it could add dashes automatically on the texts and fix this issue. So, what do you think about this feature feedback?
Is there a plan to allow multiple values on variables soon?Its helpful to follow the way tokens are usually made on code, for example for padding:--button-padding: 12px 24pxIn Figma, this is important to allow, if not, we need to split the token into:--button-block-padding: 12px--button-inline-padding: 24pxAnd this gets more complex when you need border radius to be different in each corner (x4)Figma team, when will be this possible? Might be not relevant for a simple system, but it’s important for a multi-brand system where paddings are different, and already set with multi-values in the code side.
So I talked with the AI agent about this:- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -Hi! I'm Figma's AI Support Agent.Ask me a question. I'll help you solve it or get you to the right place.Why does Figma's Help (whether old-school or AI-assisted) far too often has no clue, or offers many vague or unrelated answers ? I asked for (literally) "insert slide number in Figma Slide" and it says: "no answer found". If I ask Google, it brings me right here [article explaining it], on the spot !That's a fair frustration, Peter — and the good news is Figma Slides does support slide numbers. [Answer and referral to the very article followed...]Why do YOU know that, but can't the Help Center (accessed through the big bold Question Mark button that's always in every Figma interface) provide me with that same reply ?That's a valid question, Peter. The in-product help and the Help Center search can sometimes miss specific queries due to how their search indexing works — they ma
I’ve been using Spec to write use cases and product requirements, and I love the idea of bringing product work into Figma, where design already lives. It creates a real chance for a closer exchange between product and design. Here are some suggestions from that experience:Integrations with FigmaSomething like a split view with the Spec and the prototype in Dev Mode. Let developers open a prototype with its connected Spec side by side. Even better if both stay in sync: as the developer navigates between screens in the prototype, the Spec scrolls to the flow step or rule that describes that screen. This way, devs always see the behavior and the requirements together, without switching tabs or searching for the right section. It would also work the other way around: from a section of the Spec, open the related frame or prototype screen. Embed a specific page or frame, not just a whole Figma file. Today I can embed a file, but pointing to the exact frame that matches a flow step would make
Why do credits in Figma AI (Figma Make) get used up so quickly? It can take up to 1,000 credits for a single prompt in a relatively large file—yet when I worked on similar files in the past, it only cost 200–300 credits, and the models were much faster (GPT 5.1 Sol was an excellent model). I could work for two-three weeks daily back then, now my credits last 1-2 days with the same ammount of work.
Storing credentials, secrets/tokens, in the admin panel so Figma and Figma Make can take advantage of paid features of the enterprise; Font Awesome Pro, organization level GitHub private packages, and other third party paid services.
One thing that has been time-consuming since auto layout has existed is fixing the automated changes Figma makes when auto layout is added or when resizing is manually changed for a frame. Sometimes the changes are necessary, but more often than not they seem randomly chosen; they don’t take into account the behavior/responsiveness intended by the designer.It would also be an improvement if new, child, auto layouts kept any gap variables that already existed between selected items wrapped in the new frame (instead of converting them to plain values). And it would be better if Figma didn’t add padding automatically to new auto layout frames (or at least allow designers to choose the default padding).
I absolutely love Figma Slides!! It’s so cool that slides automatically get grouped into bundles. However, I feel like if there was a way to label these groups, I can organize my rather large (100+ slides) presentation better. Thanks a lot for the amazing work, team! <3
Hello! 🤠I was very excited to see the addition of Auto Layout Grid today! Having flexibility for both Rows and Columns at the same time is a game changer.That said, I immediately ran into not being able to set a column width to “Hug” within a table, which is a bummer. In the attached video, I want the “Audited By” column to Hug to the longest table cell content. I show both the current solution today, and what I am trying to do with Auto Layout Grid.I can manually adjust the width of the column, I guess, but as you can see, it makes it hard to ensure correct padding without a lot of careful tuning of the width. Anyone have any solutions? Will this be coming as a fast-follow feature? Thank you!
Every time I exit Figma and come back, the previously selected sort order is lost, and it defaults to "Last modified" – "Newest first". Previously, the selected sorting option was always preserved.
Hi Figma team,I'd love to see sorting preferences persist across sessions in the Projects view. Currently, every time I navigate into a project and return to the home screen, the sort order resets to default.Our team numbers all projects (01, 02, 03…) to maintain a clear workflow overview. Having to manually re-apply alphabetical sorting every single time is a small but repetitive friction point that interrupts the flow.It would be great if Figma could remember the last used sort order, ideally per user or workspace. This seems like a relatively simple improvement that would benefit many teams who rely on consistent project naming conventions.If this is already possible and I'm missing it, I'd love to know how.Thanks for considering this.Best,Justin Eleveld
In regular auto layout, a layer set to Fill can end up smaller than its own content.It would be great if a layer set to fill could respect the content's size as a minimum. Grid already behaves this way, so I'm mostly asking for the two to be consistent.In css I think the term is intrinsic sizing.
When I undo, I want undo only changes that I’ve made to a document, not what I’ve selected. I find the existing behavior to be unintuitive and counter to basically all other applications. However, I realize some people like it the way it is, so we can we get a user option to only include document changes in Undo?
This makes it easier to use components in designs for different screen sizes. And then you don’t have to calculate every time what 40% or 60% of the width is. This also makes it easier to design scalable applications that grow with the width of the screen.
Hi Figma team!I'm a product designer working closely with developers on mobile and tablet app design.We've encountered a couple of challenges when developers inspect our designs in Dev Mode. Current challenges: Auto Layout is difficult to identify in Dev Mode. It's not easy for developers to tell whether Auto Layout has been applied to a frame. Unlike Design Mode, where Auto Layout is clearly indicated, Dev Mode doesn't make this obvious. Prototype connections are difficult to inspect in Dev Mode. Developers can't easily identify which screens or dialogs are connected through Prototype interactions. To check transitions, they need to use the Preview button, making it less convenient to understand the overall screen flow. Suggested improvements: Make it easier to identify which frames have Auto Layout applied in Dev Mode. Make Prototype connections and interactions visible and easier to inspect in Dev Mode, without having to launch Preview. These improvements woul
Our team uses Codex with Figma to build and maintain a shared component library. Multiple designers work with their own agents, each with different tasks and context. Developers may also have their own coding agents working on the corresponding implementation.We can already see other collaborators’ agents and their working status in Figma. That made us wonder: could these agents collaborate with one another around shared design assets, with their owners’ permission?The gap we encounterAn agent can inspect a shared component, but it may not know why another designer made certain decisions, which business constraints apply, or which questions remain unresolved. Today, we have to copy context and questions between separate conversations, relay the answers, and reconcile the results ourselves.A workflow we would find useful1. A designer’s agent updates a component and shares an approved brief describing the goal, changes, constraints, asset version, and open questions.2. Another designer a
My Figma training attendees often ask: can I see somewhere how many credits do I still have ?Of course, I know by now, it’s under the Figma menu in any application.But another very logical place for any one concerned in general about it, would be under the AI Credits section in the Account information. But it shows info about seats using AI, credit plans, reset date, and a vague blue/grey line with a number (e.a. “117/3000”) when you hover over it.That’s not very helpful.Why not display the accurate credits status over there also with clear wording like “used/remaining” ?One could test/check it before and after using an AI feature (seeing a number going up or down), but students always ask me on the spot: how many do I still have, right now ?
I'm paying for a Professional seat, and somehow I burn through my monthly AI credits after generating just a few screens.For roughly the same price, I can get way more done with Codex. Figma really needs to rethink these limits.
I really don’t understand why still no sharpness tool in picture settings. This would eliminate the need to go to the photoshop (or any other tool) to do this. I understand that it can be done with ai tool. But it seems too expensive for such simple job.
I've been experimenting with multiple video fills in a fairly longer than average Figma Motion composition (2-3min). Thanks to the workaround from another thread, I've managed to get videos playing in the final export by adding two rotation keyframes.However, video synchronization still seems to be an issue. For example, I have a 141s video that's supposed to start at 0:00 when its layer appears at 32.14s in the composition. Instead, Figma starts playing the footage roughly 32 seconds into the original video, as though it's following the overall composition timeline rather than the individual layer's timing. It also unexpectedly loops later on randomly somewhere you don’t wanted.I've tried adjusting layer duration, opacity (0% → 100% with Hold easing), and Position/Rotation keyframes without success.Of course, Motion is still in Beta, but having independent playback controls for video fills (at least a start time, offset, trimming, or looping) would be incredibly helpful for more compl
Hello, Lastly I faced a problem with the wrap mode. I need to be able to fix a max number of items per line before wrapping to the next line (with a min/max width per item of course). It’s for the sake of simplicity because I don’t want to remove wrap mode just for that. Should be clear enought, if you have any further question ? 🙂 Cheers, Xavier.
The library we are using in our company can be modified by several people in the team. When I want to publish changes to the library, sometimes I would see changes I didn’t make. Or sometimes it was a change I actually made that had an impact on another component, but it’s difficult to understand right away given that you can’t have a close look at what has changed exactly (the preview is so tiny!) It would be great to have some kind of before/after preview each time I hover one of the components in the “changes” list. It would reduce the risk of publishing wrong components that are not well built. Because right now I always have to ask my team if they have touched anything in the library which is getting tiresome to be honest. Thanks ✨
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.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.