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.
I would love to be able to do more in Slides via the API. Specifically it would be great to be able read and write text in the slides via the API, so we can convert other content into Slides easily or update our Slides decks easily.
Getting the “Publishing failed: Please reload the page to publish” error when I try to publish. I’ve gone through the older treads but haven’t found a solutions beside Figma sent out a fix. I’ve tried everything I can think of including the obvious solutions like reloading tab and restarting computer. I’ve tried deleting all new components and even restored earlier versions, from the version history panel, that were previously published. Yet still no luck. My other libraries will publish, but my main library will not. 🙄
I keep receiving the error: “Something went wrong. Please refresh or try again later.” I have tried to remediate the issue by: trying again a day later duplicating the file and trying again clearing app cache trying desktop vs web reverting back to previous builds No luck on any of the above. Any suggestions? Have I hit a max amount of prompts? Frustrating as I’ve reached a point in my prototype that needs fixes and it is locked up.
So this is just something I hit my head on all the time. I have some components which are meant to hold a list of instances of another component. The solution I always use is to create like 20 instances inside and then hide all the ones I don’t need for a given design. Many of these designs contain far fewer than 20, but other designs can get close to that number. It just depends. Having all this unused junk in my layers is just irksome. A related problem is that the interior elements cannot be reordered without a lot of work. Ideally, it should be possible to create a component, which can have an arbitrary number of a particular instance (like "list row"s in a “list”) and those instances would be reorderable and removable in the layers panel. It seems like this should be doable with a special component property applied to the embedded instance that I want to have arbitrarily many, freely reorderable copies of. Other posts make a similar request, but I wanted to add my own to emphasize
Hi Design Community! 👋 I recently completed a 3-day design sprint focused on improving the apartment search experience on OLX (desktop web). The goal was to solve common user frustrations like multi-city search, long filter forms, lack of comparison tools, and more. I've applied user-centered design principles, competitor benchmarking, and modern UI patterns to enhance usability and visual clarity. I'd love your thoughts! 💬What’s working well? What could be improved?Any suggestions to push this further? 📎 link to Figma : Case Study : Case Study - OLX Apartment search category Thanks in advance for your feedback 🙏 #UXDesign #UIDesign #UXFeedback #ProductDesign #DesignCritique #CaseStudy #UXResearch #UserExperience
Why are the previews of the project displayed equally to the editable?How many features are blocking the discovery of what I am searching for? Why can I render forza in hd and web-ui drops fps?
Hello, i’ve created a simple button, with text, padding and autolayout. I’ve turned it into a component. I now want to make the stroke a property for all the variants, that i can turn on and off with a boolean. However, there is no diamond icon next to the stroke in the right hand panel, so i cannot figure out how to tie it to a prooperty. Is it because the stroke is not a nested item? .
We just wrapped the big announcements at Config , and we know there’s a lot to take in. This thread is your space to share reactions, ask questions, and let us know what you're excited about (or still curious about) with regard to Figma Make. Our team will be actively reading and sharing relevant takeaways with the product team. What we’d love to hear from you: What aspects are you most excited about — and why? Where do you still have questions or want more clarity? Anything that didn’t quite land for you yet? A few quick reminders: If you need help with a specific account or file issue, please get in touch with a specialist on the Support Team. A note on Community Guidelines: Posts that veer off-topic or become unproductive may be moderated to keep the focus on the product at hand. Keep feedback focused on Figma Make — this helps everyone follow along.
I have created a component which, while hovering, animates a little. Even after sharing the dev mode to the developer, my developer is asking me to share the lottie file for the same, to which i am unable to generate and share cause currently i cannot afford the lottie subscription. Suggest some way through i can share the animated component (with it’s variant state) with the developers.
Hi everyone!I've been running into a recurring issue when exporting SVG assets from Figma. Everything looks perfect inside Figma, but when I export as SVG and use it on a website, the design sometimes breaks — fonts don’t render correctly, alignment shifts, and sometimes fills or strokes are missing entirely. I’ve tried: Flattening layers before export Converting text to outlines Exporting with and without "Include ID attributes" Comparing in different browsers (Chrome, Firefox, Safari) Still seeing issues! Is this just how SVGs work or am I missing something in the Figma export process? Would love to hear your tips, settings, or best practices when exporting clean and browser-safe SVGs from Figma
I was going to praise how neat the new Annotation feature is, when I realized the content is only visible to Dev Mode accounts. Are you serious? I understand you want to limit creating annotations to certain seat types, but viewing annotations should be a viewer-level feature. Come on Figma, there are better ways to convince your users to pay for a subscription. This is such a crooked move.
Hi, I am trying to complete Stripe onboarding to sell community resources on Figma but it keeps giving me this error (attached) I’ve been chatting with customer support for the last few days and I was first told it could be an issue with the Postal Code (The UAE doesn’t have postal codes so we normally just use 00000). A couple days later I was told that the issue is because I need to submit it from a user account not a team account (keep in mind that this is a user account not a team account). Now I’ve finally been told that it’s because my country is not supported. I live in the United Arab Emirates and Stripe is supported here (https://stripe.com/ae/global). Figma’s articles say that it accepts paid resources from countries where Stripe is supported (https://help.figma.com/hc/en-us/articles/12730712101783-Activate-your-Stripe-account). I've spent the past 11 months designing and building this resource to help Figma users streamline their workflow. As you can imagine, I’m really hopi
I have a few prototypes I’m working on, and whenever I scroll in the prototype presentation view, it will jump either up or down and totally glitch in terms of the scroll amount. I’ve tried all sorts of things like wrapping any components in Frames, removing any fixed position elements, and simplifying it as mush as possible — it’s still happening. Is this a known Figma bug that others are encountering? Thanks!
I can’t seem to find a way to turn off the red measurement tool. If I go to View > Hide UI it does remove it, but it also removes other side navigation components that I need available.
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.