Share Your Thoughts

Since it’s now possible to upload WOFF files to a Figma Sites project, i wanted to ask if you can also embed Adobe fonts? This would be such an essential feature for any brand work. 

Our team uses Quasar Framework with Vue.js for all front-end development. Currently, Figma Make generates React-based code.It would be extremely helpful if Figma Make could generate code directly using Quasar + Vue.js, or at least provide an option to switch the output framework.

I just got here.  Obviously Figma has been around and I’m new… and good, because with a fresh pair of eyes, I have to ask: WTF, Figma? How many little “X”s will I have to close before I can finally use the app?  Boxes of propositions and I haven’t even gotten here.  Tip boxes to tell me things before I have even had time to click a single feature in the product.  I mean, there were like 4, or 5, just now!  And then when I was finally ready, the page refreshed to pop another product feature ad up at the top. Oi.  I just want to use the app. This is the kind of UX that makes people throw keyboards at the wall.  SO FRUSTRATING.

The help button blocks the prototype content, and it is suggested that the help button can be hidden or moved。

OAuth App does not have permission management functionality, so permission management functionality needs to be added, such as adding editors and readers-only.

As administrators, we are constantly annoyed by “false” licence upgrade requests.All users get different modals that urge them to ask for an upgrade, even when it’s not needed (eg. they’re invited to collaborate in an open session, hence can edit without licence upgrade). This leads us to have to re-qualify every single request to determine if there is a genuine need, or if it's just someone who clicked to get rid of the modal (90% of the time).Is it possible to disable these modals inviting users to ask for an upgrade? It is a real burden on a daily basis.

Hi everyone,I’m running into a strange shortcut behavior difference between my work and personal Figma accounts. Platform: macOS (Turkish-Q keyboard) App: Figma Desktop + Web (tested both) Mode: Design mode, Move tool active, not in Prototype etc. Issue: In my personal account, pressing ⌥ + ⌘ + ↑/↓ rotates the selected object. In my work account, on the exact same device and setup, the same shortcut correctly changes the layer order.  What I’ve tried (none fixed it): Cleared Figma cache (~/Library/Application Support/Figma) Removed and re-added both accounts The behavior persists only in my personal account, even in the web app. Switched keyboard layout between Turkish-Q and English (US) Disabled all plugins Tested in both Desktop and Web app Confirmed Move tool is selected and Prototype/Dev/Draw modes are off I’m stuck right now how to resolve this issue. I need a help.Thanks in advance!

I’ve been asked a couple of times if the font size can be made bigger by colleagues within the feedback panel because they can’t see it. We might be a bit older than most using this software but it would still be a helpful setting to include.

I’ve been building a project using Figma Sites and I’m running into very slow loading times when navigating pages. Even after compressing all images and simplifying the design, the performance hasn’t improved.I ran a network analysis and the issue doesn’t appear to be assets or images — it’s the initial page response from Figma’s server.Here’s what I’m consistently seeing across pages: Waiting for server response (TTFB): ~2.9 seconds Content download: ~3 ms Connection/queueing: negligible So the browser is waiting almost 3 seconds before receiving the first byte of HTML. Once the response starts, the page loads instantly.The request structure also shows that each page loads through: /_runtimes/sites-runtime.*.js /_components/v2/*.js /_json/{page-id}.json …suggesting that Sites dynamically assembles each page on the server. Combined with: cache-control: public, max-age=10 …it seems Cloudflare is forced to re-fetch the HTML from origin frequently, which might explain the slow TTFB an

I wanted to share an idea that’s been on my mind: I think Figma could benefit from a dedicated design staging environment. Developers have staging to validate functionality before production, but designers don’t really have an equivalent space to validate design behavior at a higher fidelity. A staging-like environment in Figma would let designers build and test more realistic flows, interactions, and states — something deeper than prototypes but lighter than full development. It could help teams surface UX issues earlier, experiment safely, and hand off work with more clarity. I also think it would make it much easier for developers to understand the design. Right now, presenting prototypes in Figma can get messy, especially on bigger projects. For example:– Sometimes the Figma UI can get in the way when sharing previews.– Prototype links end up long and awkward to share.– You usually need separate URLs for desktop, mobile, and tablet.– There’s no true responsiveness, so everything fe

Hi,I often need the super useful new “Translate to...” AI feature, it’s great, thank you!One way to make it even greater would be to save which language was used last and use it as the default selection. Now I always have to type “ger” to get “Germany” and press enter, bc “Arabic” is the default since it starts with “a”. Just like the cmd+P menu has a “Recents” with the last action on top, I would propose to introduce this for the language selection of the “Translate to...” tool :) Thanks for the consideration,Mikka

In Prototype, Conditional can be used when Trigger is set to None, enabling state monitoring.I believe this can lead to more convenient prototype design, reducing the extensive and cumbersome wiring in Prototype mode. At the same time, this approach will be more suitable for future AI editing, incorporating more code-oriented thinking. 

下面的figma，上面是mastergo，兩者的區別有一個新的分類，同一個大類裡面有不同的頁面作為區分。 figma 缺少此

I recently upgraded from a Starter seat to a Collaboration seat, expecting to gain access to AI features and the ability to share projects with clients.However, I'm experiencing significant limitations that are affecting my workflow:I cannot use plugins on any projects (both existing and new) I cannot share projects with clients Other essential features are also restrictedThese limitations are severely impacting my productivity and ability to gather client feedback. When I encounter these issues, Figma displays a pop-up suggesting I upgrade to a full seat. I wasn't expecting the Collaboration seat to have more restrictions than the Starter plan.I previously contacted support via email, but the response I received didn't clarify the situation or resolve the problem. Could you please help me understand:Why the Collaboration seat has these limitations What options are available to restore the functionality I need Whether there was a misunderstanding about what features are includedI appre

Has anyone found a way to copy, transfer or move the new local variables to another file or collection? Just created around 400 color variables manually in the wrong file and would hate having to re-create them in the correct one 😅

Hi Figma team and community! 👋 I've noticed several posts from users looking for a way to export Figma prototypes as video (MP4 or GIF). Right now, the only available solutions seem to be third-party plugins or screen recording tools, which work—but aren't always ideal when we need quick, high-quality exports to share with clients or on social media. I’m wondering if Figma has any plans to include native support for exporting prototypes to video in the near future. This would be an incredibly helpful feature for presenting flows, especially for marketing or stakeholder presentations. Would love to hear if this is something that’s on the roadmap, or being considered! Thanks 🙏

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 would like to be able to save the animations and motion graphics I create in Figma, such as intros and animated loading screens, as videos so I can use them in my projects and share them with the team. Currently, I have to screen record the animation, which results in lower quality than what's in Figma.

Here are my two first private messages after creating a figma community account. Can you implement bot protection?  

Hi everyone,I’m currently working on a prototype in Figma, and I’m trying to achieve the following keyboard-based interaction: When I press the A key, an overlay appears. When I release the A key, the overlay closes automatically. I noticed that Figma’s "Key" trigger only allows actions to be triggered on key press, but I haven't found any way to differentiate between keydown and keyup, like you would with standard JavaScript events.Is there any workaround or trick to simulate this behavior directly in Figma?Or would I need to use an external tool (like ProtoPie, Framer, or a coded prototype) to make this interaction possible?Thanks in advance for your help! 🙏

I’ve been using the Figma’s AI lately and it’s super useful. A useful feature would be the ability to change the image aspect ratio. Currently it’s using the default size, so If I want to expand an image This is How I should do it: ​​​​​A feature like “Expand Image” or “select aspect” ratio in edit image toolbox would be so useful.

Hi everyone, - please find below an alternative workaround to Figma 429 rate limits as well reducing weight on Figma infrastructure which helps the ecosystem ;). This as an immediate fix.The issue isn’t Figma’s limits themselves (which are more recently conservative and problematic), it’s the way large /v1/files/:key?ids=… calls pull entire subtrees (often megabytes), then trigger dozens of image requests when frames have 50-200 children. That burst pattern quickly hits Figma’s limits protection causing 4-5 day lockouts.A proposed solution is to stop fetching everything upfront and adopt a metadata‑first, prune‑first, fetch‑last pipeline:Fetch only component metadata. Pre‑filter locally to remove hidden frames, junk nodes and remote libraries. Fetch a pruned node tree with limited depth (depth=2–3) to keep responses <500 KB. Do code analysis and token extraction locally without extra API calls. Fetch images only for the final deduplicated list, in small adaptive batches with exponen

So I have created a simple form component and used MAKE to create a working version suitable for prototyping (This allows me to have full text entry and validation).The biggest issue is I am unable to tell the ‘Submit’ button to navigate to the next page in the prototype.Even if I tell MAKE to navigate to that page it just doesn’t seem to work.Does anyone have a work-around or solution to this problem?

Hi,Has the Figma team has ever considered a follow mode that allows followers to see the toolbars? I often show other designers how to do something in Figma, but I have to share my screen on Teams so they can see what I’m doing, and then they have to jump to Figma to edit and try what I’m doing themselves. They end up switching back and forth between the Teams and the Figma window.

I tried reaching out to the Figma Sales team back in July 2025 but haven’t received a response yet. I submitted another request today (11/24) through the “Contact Sales” form on the Figma website. We need Figma for our work, so it would be greatly appreciated if the Figma Sales team could get in touch with us as soon as possible.Thank you :)