We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
🎉 Welcome to the Figma Forum! 🚀
Find solutions, get advice, help others.
Hello, it would be nice to have the option to insert floating components inside text (like Emojis). Use case would be for signs or infos in complex dashboards. Its a hustle to do this now manually and also set kind of boundingboxes to sync different heighs of text and component. Regards
Hello everyone, I’m having some issues with Figma Slides when trying to present both in presenter and audience view. In particular, the “smart animate” slides transition doesn’t work in the audience view but seems to work fine in the presenter view. I already tried to restart the presentation, open it in the app and on different browsers, I just can’t find a way to make it work. It’s driving me crazy, I’d 100% prefer to not view the smart animations in the presenter view rather than in the audience view.Do you have suggestions for solving this? It’s for my graduation presentation, I need to use 2 screens, one external for the audience view and my macbook screen for reading the notes in the presenter view:(
It would be great if the professional plan offered more than 4 variable modes. Right now I want to set up a mode for each component size-- XS - XL, 5 sizes all together-- which puts me over the 4 limit for pro, but well under the 40 limit for enterprise, which is a quantity I will never need. And there’s no use case for enterprise at all for a team our size. I think 10-12 modes for pro would be perfect to give small teams like mine room to grow before we reach the scale where an enterprise plan would be worth consideration.
I have paid two full seat last month, and want to downgrade one seat to Dev seat from next billing cycle. However, there is ‘Dev seat adjustment’ fee in the projected subtotal. What is this fee? Should I pay extra $7 to downgrade the seat? It does not make sense to me.
While prototyping in Figma, all connectors (nodes/links) are the same color, making it difficult to visually distinguish which frames are connected to each other. To improve clarity, consider adding an option for color-coded connectors or user-defined colors. This would allow users to assign different colors based on interaction types, flows, or personal preferences, making complex prototypes easier to understand and manage.
I’m working on a project with 2 files: the Design system, containing the entire component, style and variable library the Delivery file, containing the final mockups. I draft mockups from a “Sandbox” page on the Design system as a way to save time by limiting library publications & updates. Then once it’s ready, I copy/paste the final mockups from the Design system file to the Delivery file. Until now I had no issue. But today, I’m getting the following message: I don’t understand why I’m getting this message. Obviously I want to keep all variables attached only to the Design system file as the single source of assets. I’ve double-checked: the library in the Design system file was fully published and updated on the Delivery file before I copy/pasted the mockups into the latter file. I’ve done it multiple times. The Design system file contains a few hundred variables, and if I do click “Copy variables into this file” on the banner, the confirmation message says “21 variables pasted”. I’
I can't believe Figma is forcing this change on us. UI3 is, without a doubt, the most unfriendly design possible. It has made my workflow painfully slow and incredibly unproductive. What’s the harm in letting people CHOOSE which UI works best for them? I always thought switching to UI3 was a HUGE mistake, but I never felt the need to comment on it because UI2 was still an option. Now that you're FORCING this change, I have to speak up. This is NOT an upgrade. It’s a downgrade in usability, efficiency, and user experience. Figma was supposed to be about flexibility and user-centered design—so why ignore the feedback of those who actually use the platform every day? Give us back the choice. Let people stick to UI2 if they want. This forced migration is a slap in the face to long-time users who built their workflow around UI2.
Hello! Met plugin error in development process: figma_app.min.js.br:5 Error: in postMessage: Cannot unwrap symbol at Object.postMessage (eval at <anonymous> (eval at createScopedEvaluatorFactory (03b877b0-1906-4ddd-92e2-48a05c2b4ecd:1:6906)), <anonymous>:23:21) at figma.ui.onmessage (controller.ts:23:1) at uar.callFunction (figma_app.min.js.br:707:4755) at Lee.iframeMessageHandler (figma_app.min.js.br:1436:5769) at UNo.toplevelWindowMessageChannel.port2.onmessage (figma_app.min.js.br:1404:5229) at figma.ui.onmessage (controller.ts:23:1) I am using figma.listAvailableFontsAsync and have following code: figma.ui.onmessage = (msg) => { if (msg.type === 'parse-system') { figma.listAvailableFontsAsync().then((res) => { <<<< 23 line figma.ui.postMessage({ type: 'pass-systemFontNames', message: res, }); }); } }; I was testing this method inside my ‘playground’ Figma file. On newly created pages it works fine, but on pages that I created a year ago I see this error. How can I fix this? Thanks!
suggets me to hire developers in UK with expertise in Solidity, IPFS, and Ethereum-based token standards for an engaging marketplace.
Hi everyone 👋 I'm a daily Figma user and really appreciate how flexible and powerful Auto Layout has become.That said, there are still a few small but recurring pain points in my workflow that I believe many other users may also be experiencing — especially when it comes to Auto Layout default settings. Currently, certain Auto Layout options like Exclude strokes and Canvas stacking are always turned on or off by default. While this might suit some use cases, it can feel counterintuitive or inefficient in others. 1. Exclude strokes — A repeated manual step that can lead to dev/design misalignment Every time I apply Auto Layout, I find myself manually disabling "Include strokes."In web development environments, it's common to build layouts using border for visual separation — not stroke.Because of this, including strokes in padding calculations can often result in misaligned spacing between design and front-end implementation. If designers could set "Exclude strokes" as a default, it wo
When I need to use larger text, often to highlight something on the artboard, the text box that appears is much too small for the text. This has been an issue for at least six months now. And I can’t find any way to resize the textbox properly; the large text always sits outside of it. It’s ugly, but it also makes the element difficult to manage and manipulate. Any fixes?
Hello Figma Support Team, When I previously contacted your support team, I was informed: “Please reply directly to this email. Even if this ticket is closed, replying to this ticket (email) will reopen it on our end, allowing us to review the previous ticket details. Therefore, please respond directly to this email.” Following this guidance, I recently replied to the email. However, the ticket status remains “solved,” the ticket is still closed, and I have not received a response. If my request has not been reviewed yet, I would appreciate it if you could check and reply to my email. Thank you for your time. For reference, my main ticket IDs are #1285247 and #1306379. This message has been translated using a translation tool.
One of the best features I loved about Figma slides was the “adjust tone” capability. With the recent push out of beta I’m no longer seeing this feature. Anyone else notice that?
APIs, guides, plugins, and more.
Find a virtual event that speaks to you.
Find answers, learn more.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
