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.
Find solutions, get advice, help others.
in App on Windows: From time to time the commenting function locks up when an accidental comment is placed in the Commenting cursor. When try to exit the comment, the cursor locks up as moving hand and no more Commenting can be made. The App needs to be restarted to get out of the cursor lockup. Is this a known issue?
Hello All, I am not able to publish the custom website that I designed in Figma and pasted it in Figma sites.
I'm trying to publish my website but this error keeps returning:
I want make some element in frame just creating it in place where i want to see it, and during work i also use AL, and i always have to make element somewhere, because of AL and than add it to place where it have to be, and after it compare sizing and other visiuals elements Let me make element that already have absolute position by some shortcut, to quick add layer to layout without problems with override AL settings
Hi everybody – I’m using VS Code with Claude Code and I’m trying to setup my Access Token. Inside my Figma Settings panel, the token states it was used and appears to be connected, but Claude (via VS Code) is showing a failed connection when using prompt “/mcp” to see the Manage MCP servers readout. On the other hand, my Figma Dev MCP Server, directly from my Project, is showing Connected. I connected the API before I connected the Dev MCP, though – does that make a difference? Do I need to connect the Access Key for additional functionality or will just the Figma Dev MCP do the same thing? UI/UX is my primary field so I’m in the depths of this learning curve for back-end stuffs. Any insight is greatly appreciated!
It would be a great idea to add the ability to move annotations (сhanging the place). Right now, they’re fixed in place and can overlap other elements. And you cannot change it.What I mean is the ability to reposition an annotation freely while keeping the link to the target object intact.Annotations are a really useful feature—thank you! Previously, I had to create similar functionality using my own objects. Please do not move this offer to another discussion. 🙏 Can we move the Figma Annotations (in dev mode) from one Figma project to another? These are different questions.
Asking because I noticed it isn’t currently, which means every addition/substraction to my Guidelines.md needs to be managed elsewhere, outside of Figma.
I've been experimenting with the new Figma Make feature and noticed a recurring issue that's affecting usability: After about 8–10 successful prompts (each 1–2 lines long), Figma Make starts rejecting any further prompt with the message: "Try again, with fewer inputs." This happens even when the prompts are extremely short, e.g., "Create a dark-themed button component" or "Add a CTA section with three buttons." I’ve tested this across multiple projects and browsers. The issue persists consistently, and the only workaround seems to be refreshing the tab, which sometimes helps temporarily — but not always. Additional Context: Even though Figma Make is currently laggy while generating prototypes (which I can overlook), this input rejection bug makes it difficult to iterate quickly or finish design ideas. It feels like a silent rate-limit or session exhaustion issue that’s not clearly communicated to the user.
Would be great to have a native skew and shear tool in Figma. Even with plugins, I’m not finding a way to control the skew anchor. Just something simple like Illustrator’s Free Transform, where you can skew an object and choose where the effect starts from.
This feature is not working anymore on MacOS on the newest version 125.6.5 (I have this issue on my Macbook Pro M4 and Mac mini M2). Fortunately, my Windows PC is still working. If anyone has this issue, please help me raise this up to Figma!
Hello 👋, Our team is very enthusiastic about the Figma Buzz concept, we decided to try it out. I created templates, locked the layers that don't need editing, published them, shared them with my colleague and gave him editing permission. My colleague logged in but was able to edit every layer of the template, also the locked ones. And also if he uses that template in a new file. Could you help me find out what's wrong? Why Figma Buzz doesn't meet our expectations? In the first screenshot below, we see the layers are locked in design mode. And in image 2 and 3, we see the user the template is shared with able to edit the same layers, while in Buzz mode. I cannot find similar questions in the Forum. Are we the only team having this problem? 😔For now we've concluded that Figma Buzz's beta version is not sufficiently developed for our current collaboration needs. Because we did not experience the anticipated 'simplified editing experience.' Thanks a lot in advance!Marinske
I’ve had 2 problems with using team libraries with Buzz so far: Adding the libraries You have to manually reapply every single style or variable that was updated in the library. The first problem is more of a frustration that shouldn’t exist. Why change the method of adding libraries? It just makes it harder to find and use. (“Asset view” shows templates you’re using, and what would be called an “asset” in every other Figma app is now called an “insert”!? It boggles my mind that at least one entire product team thought that was a good idea. 🤯) The second problem is a deal-breaker. For a product that’s focused on brand, it should as easy or easier to apply and update styles and variables. If there’s a button to trigger the mass application of library updates, it’s hard to find. If there is no way to trigger a mass update, that’s a huge problem, because not only do you have to keep track of what was updated, you also have to reapply all of those updated styles and variables to each affe
Properties propagation is necessary to build and maintain a flexible , modular, and dynamic design systems. For example, I’m building a TableCell component in my design system, which should support inline editing. I’d like to crate a Value property on the TableCell master component, so both states (View | Edit) retain this value when switched. I’ll use different components to render out the cell value: View mode - Typography (text) component Edit mode - TextField (input) component I can’t implement this, unfortunately, due to the limitation described in this thread, so I have a few options: Use nested instances and lose the ability to propagate the master component (TableCell) Value property to the child instances (Typography, TextField), so once the state is changed, overrides (Value) are lost, and should be re-entered (manually) for each of the component states. Don’t use nested instances and instead put detached versions of them. In that case, I’ll need to re-implement a lot of addi
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.
