Report a Problem

Hi, everything is in the title,by release, i mean when executing the public plugin which is available to everyone,and by development, i mean my local copy.I have tested it on the exact same file and conditions, so i know it’s not related to something else.Do you know about that ?What could be the possible reasons ? It seems to be the case in any context, in development, a complete re-render of my algorithm would take 0.5 to 1 sec in average, and it takes from 2 to 3 sec in release.For context, my plugin is  :https://www.figma.com/community/plugin/1504087347056471789/10x-html-design-to-clean-responsive-code-10x-fasteran HTML exporter that runs vert fast,It is a big problem because my plugin shows a preview which allo

Hello, all the designs in Figma are showing the shadows incorrectly. This had been corrected and it is happening again. 

I am using material UI. I have a switch. I want to bring that switch into another component I’m making on a different page. Because of micro-interactions, material UI switches got like 4 states. I like them like that. Now… Those 4 states, in this switch are just for “lights off”; “lights on” has another 4 states. I don’t want to copy 8 instances into another page and then create a new component group that nests the OGs just so I can prototype this button behavior to do what I want it to do. @figmahelp; people… How do y’all deal with this. I have to be missing something right? I got my main component. I don’t want to assign attributes to it that aren’t universally applicable (change variable mode). Is there really no other way to manage this other than duplicate duplicate duplicate?

i cannot upgrade from my expired educational plan to a professional. i have tried everything i found googling stuff. i need help. I submitted a complaint ticket, here is the number: 1382307

Hey, my company’s social/ad template is set up with various artboards ready for export. But in the past week, ads that used to export as 300x600 are now 301x600 for example, which our ABM platform doesn’t allow.Is this caused by a figma update/glitch, and is there a solution? Thanks!

Hello everyone, today my Figma updated and now I can’t seem to find the old beloved “Layout/Autolayout” section, someone can help?  

In our company, we use font variables for our three types of branding. We build components using the font variables to make sure everyone uses the correct branding and components. Recently we discovered that - when resizing a component - the font variables are fixed to the branding of ‘Mode 1’. It can’t be switched back on, except when you Detach the Component. Is this expected behavior? Can it be looked at? 

My team recently transitioned from Professional licenses to an organization Figma Government plan. As directed, we exported our component library and design documents to local files, then imported them into our new account. Unfortunately, the components and variables in the design documents are disconnected from our design system component library. We’ve tried the Repair Component Connections and Repair Variables Connections commands, but they don’t seem to do anything. Is there a way to fix up these connections with recreating entire design documents?  

I am working on a library and some design files in parallel. Meaning, the library is not yet mature or stable, and updates are published very regularly. In addition to the ‘real’ updates, Figma keeps throwing in a bunch of ‘phantom’ updates for components that I havent’t touched.Plus, the ‘review updates’ preview thing is so slow that it mostly just never loads. I’m sitting on a pile of dozens of updates, some spanning back weeks, and I’m too afraid to just press ‘update all’ in case something breaks in my design, but it’s also impossible for me to go through all of these one by one because the preview never loads. And this whole problem multiplied by 6 files. Is this happening to anyone else? How are you dealing with it? I don’t know what to do.

Hi!Has anyone encountered this issue: some of our components had text properties so the text could be set directly in the properties panel. Some time later, we decided to delete these text properties. As a result, after publishing the library, in all instances of SOME components (not all, SOME), the text that was linked to the variable gets reset to the default. But this doesn’t happen in every component that had a deleted text variable.Is this a bug or expected behavior? Has anyone run into this? How did you deal with it?We have a large library used by 50+ designers, and what seemed like a tiny update that didn’t break anything during testing ended up resetting values to defaults in some components after publishing.

Thanks for launching this new feature!I’m not sure if it is a bug, but I figured I would ask here. Let’s say you have a parent container, with a child element called “Instance A” with a width that is set to autofill width.When you swap out the Instance A (aspect ratio of 4:3) with another Instance B that has a different aspect ratio (16x9), and both components have ratio lock,  Instance A’s aspect ratio overrides that of the B’s.To me, this isn’t to me, the B’s ‘locked’ ratio value should take priority. (personal opinion)Now, there are two ways to restore B’s ratio.Right click into B, and reset. Resize parent container temporarily.  This will reset B’s ratio to 16x9.  And then you hit undo.#2 feels like a bug to me.But again, B’s locked ratio should take priority. (or give user control to set priority)Thanks!

Hi everyone,since we’ve used our branching/merging options in our Design System we are facing an issue, that keeps on giving the weirdest visual outputs.The issueWhen we merge a branch back into main, some frames appear to be smaller/larger than they actually are. Just last time, when we updated our icon collection and changed default size from 20x20 to 24x24px, some icons kept their visual appearance at the previous 20x20 after the merge. This is also weirdly reflected in the instance swap menu thumbnails for said icons.A similar issue, just reversed, has already been raised here:  How to fixThe easiest fix so far, that I have found, is to enter the affected frame, shape, etc., change width

At the very first time I open the Figjam file, the Generate AI beta will Opened in default but I accidentally closed that tab, How can I open it again to use. Is there any short cut to open that tab.

FigJam一直报错啊今天，我还挺喜欢这个工具的，其他画流程图的工具都不怎么爱。能尽快修复吗！errorid：910f3e45b3fe4ae192921241ae1c038f 

Hi everyone,I've encountered an issue that I can't resolve on my own, so I'm reaching out for help.Our team is researching the prompt-to-code feature on Figma Make and we have a shared Make File. However, the Preview feature doesn’t seem to work for me, even though it works for my colleagues. I can only prompt and see the code generated by the system, but I can't see any preview. I've tried switching to different browsers (Edge, Chrome), using the Desktop App, clearing caches, restarting my Mac, and re-signing into Figma, but the preview screen remains blank. Please help me with this issue.Thank you all!

I have a hard time finding the corresponding Chinese fonts in Figma. I think fonts in other languages ​​have similar problems.Can we add the ability for the software to read font names? 

Hi everyone,We're currently facing an issue with webhooks in the project context.We've created a webhook to listen for FILE_COMMENT events on a project. The webhook was successfully created, and we’ve confirmed that the PING event is received correctly.However, when testing with multiple users posting comments on files within the project, no comment events are being triggered. We’ve verified this by checking the webhook logs using the GET /v2/webhooks/:webhook_id/requests endpoint — only the initial PING event appears there.Is there something we might be missing regarding webhook configuration for project-level comment events? Are there any known limitations or permissions issues that might prevent comment events from firing in a project context?Any help or insight would be appreciated!Thanks in advance.

Steps to reproduce: Create an instance of any component. Apply a scale transformation to it. Modify one of its dimensions in the right panel. Observe how the other dimension changes.  

The base background layer that I have in all of my artboards is a satellite map image that’s part of a library component. It has multiple backgrounds in the component that I can switch between (via visibility toggling).I opened Figma this morning and all of the images within that component have been cut down to a thin horizontal slice of their proper height. I can paste a new image into the component and it’ll properly display that, but the images already in the component have been corrupted. If I copy the component and try to paste it into another file the corruption comes with it.This is occurring only on Desktop, though. If I go to the web the images still appear properly. 🤔I’m running 125.2.3 on a Mac running 15.4.1.

Well I’m wondering what is happening here because this is the first time I see this problem:I changed the height of my “lg” buttons from 48px to 56px I also changed the radius from 16 to 24px I published my library and updated it on me design file   What is happening:The radius updated on all buttons The height of the buttons did not change I’m wondering if I did something wrong or if this is a known bug? Thank you

Currently, the translation to Portuguese shows two options: "ramo" and "rascunho".I believe that the translation "rascunho" does not accurately represent the concept of "branch" in the context of design and development. The term "ramo" is more appropriate, as it better reflects the idea of branching and versions within the workflow.I suggest that the translation team consider keeping the term "ramo" or potentially not translating it at all, to maintain clarity of the concept for users who are familiar with the term in English. Thank you for addressing this adjustment that could enhance user experience on the platform.

In Figma Sites, the icons I used from Font Awesome Pro 6, display properly while designing, but appear as their text counterpart when doing a preview.

Reproduction:1) Parent frame with horizontal auto layout holding chips which have rounded edges Clip Content: OFF ✅ Looks fine on Canvas and Preview on all screens (@1x and @2x) 2) Parent frame —“— —“— Clip Content: ON a) ✅ Canvas looks fine b) ✅ Preview looks identical on @2x high-res display (internal screen, MacBook Air 15’’ 2024) c) ❌ Preview has rendering glitch on @1x normal-res display (external 24’’ display) The top few pixels of the container are “shaved off”. As a consequence the top of chips are also shaved off, and they appear irregular, not regularly rounded anymore. Suspicion: Some sub-pixel rendering or anti-aliasing function has rounding errors when clipping. Screenshots (from my @1x display):

Hi there,I tried to change permission settings so that a prototype could be shared out to a client, but I kept seeing the red banner “An error occured...”. After further investigation, I believe it’s because this file has branches, because I didn’t encounter this problem on other files without branches.Can you have someone look into this please? Using branches to have different versions of prototypes is crucial to our workflow. Prototypes for clients, vs internal often have different things that are interactive, so that the narrative can be controlled.In the end, I was still able to conduct the user testing session, but had to ask my participant to create a Figma account, which isn’t ideal.Thanks.