Get Solutions

Recently noticed that components search (Shift + I) results are a bit random.Sometimes before giving me the correct result, it shows a few absolutely different components that just doesn’t have any relation to my requested component’s nameAdditional info if it can help:Device: iMac M1OS: Sonoma 14.1.1 Figma: Desktop App version 125.4.9Searching components across different files/kits (our components each have a different published file)

With Figma Grid, I can’t longer find the previous Wrap feature that allowed me to create a reactive and responsive grid by applying a "min" element.

Hey,I have components in one library and now want to split on few separate libraries like “buttons.library”, “notifications.library” etc. and I have few files with designs. How to easily reassign components in these design files to the same components but in the new libraries?Thanks in advance! 

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!

Hello, I only use Figma on the web, I can’t use the desktop app due to my computer macOS version. I have installed the Figma Font Installer, and it says that I can use local fonts on the web, but this is not working. Any solutions? Best,

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/height to some random number and undo the change immediately. After this, the affected object is corrected. Fun fact: Figma seems to know the correct size of the affected object as when you select it, it is displayed correctly, and retains certain information of when it was correct, such as box-sha

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 

Okay, I’ve spent WEEKS problem shooting this with ChatGPT and today I finally found out what was wrong. It was a bug. Nothing I did wrong. So, I wanted to create a link navigation where the hover effect was an underline for the link text. First surpirse was that I couldn’t just do that inside my initial “Navigation button” component, because Figma overhauls text styles to be consistent within a component’s variants. Okay, easy workaround: create a Label component with an instance without underline and one with and use those inside the final button component using the underlined variant only in the “Hover” variant. I learned that interactions should only be done in the main component, not in the “Label” component. Okay, seemed to be working on the test layer, but moving it to the actual design page broke the interaction and nothing happened. Cue weeks of troubleshooting, creating and re-creating components, testing with background colour changes to see if at least the button hover insta

Hi,in some instance,i see a `fills[0].imageHash` to have a null value.fills[0] is of type `IMAGE`it’s attached to a node that i can see in the editor, and i can see the image.It seems to be that the image is somehow corrupted,it is a node that i transfered from one file to anotherhere’s a file to reproduce the issue, take a look at the root node (named “root”)it has 1 fill of type image with a null imageHashIs this a known issue ?should i let it gracefully fail ? or hope for a real fix ?Thanks in advance for your input

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? 

Does anyone know what Error ID: 537757b90d844b5f9f372ab9e9b333db mean?

I want to convert an elementor site into Figma designs because they want to use Wix Studio instead of WordPress. I can only find info to use Figma to create Elementor sites.  

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.

Hello,Would you like to downgrade my Education plan to Starter free plan, because I am soon graduating and I don’t need it anymore?

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.

I’ve built a hero component with an autoplaying background video. It has a button in the bottom corner that needs to be able to play/pause the video on click. My problem is that when i try to select the video, it’s greyed out and not selectable. Anyone know why this is and if there’s a way around it? TIA. video selection greyed out.component top level layering structure 

I have the Starter Plan but no Figmal AI button. According to the Figma website all paid plans come with Figma AI. I tried contacting support but they told me to ask here for some odd reason. So hopefully a kind soul can inform me if Figma AI is only available in higher tiers (if so, I wish Figma had said so in the first place).Thanks in advance!

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): P.S.: I take “Search before you post” very seriously, and found no existing bug report yet. But can say so only with limited certainty as your forum search is currently very limited and needs better search to foster more productive feedback/involvement.

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.