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’d love to suggest a small but potentially powerful feature:a local clipboard panel inside the canvas. Think of it as a lightweight, always-visible spot where I can quickly drag elements I create during a session and reuse them throughout the file — like a mini asset shelf, but temporary and personal. 🎯 Use case: While working on complex screens, I often create utility elements (buttons, arrows, highlights, etc.) that I need to reuse across multiple frames. Right now I either copy-paste from frame to frame or scroll back and forth.With a built-in clipboard panel, I could drop those elements in one place and simply drag them out when needed. That would seriously reduce navigation time and context switching — especially on large-scale design systems or messy exploratory files. Attaching a quick visual mockup of the idea for clarity.Would love to hear what you think!
Hey Figma Heads! I’ve noticed that some of my icons have holes in the circles where they’re not supposed to (e.g., in images). Does anyone know how to fix this issue while keeping everything in a single vector and maintaining a consistent stroke size? It seems like the problem might be caused by the stroke breaking into negative space when overlapping itself. The last image shows what it’s supposed to look like. Any help would be greatly appreciated! How the icon is suppose to look like
There seems to be a bug where the Min and Max values do not show up on component instances? The values do get applied, but they do not show up in the W (width) and H (height) fields, so there is no way to see that’s where the width is coming from, or to clear the min / max when an override is needed. NOTE: this seems to happen only with nested components. In my example I have a button component, inside a “Button Group (Save or Cancel)” component. An instance of the button shows the Min width, but the button in an instance of the button group does not. Possibly related: Can’t remove min and max height when the component is nested
before 🤗 Previously, you could generate a [no expire] token now 😔 If users rely on tokens to access the figma open api, forgetting to replace expired tokens can cause serious problems. The expiration date of the limited period will cause the figma token to no longer have usage value.
I upgraded to a Figma education plan, and while I am a current student, I do not plan on using Figma anymore and would like to cancel in advance, non-paid users cannot contact support.
Polygons and stars are currently drawn off-centre: there’s noticeable extra whitespace at the bottom of the frame while the top edge almost touches the bounding box. When we depend on precise alignment, auto-layout, design tokens, or plugin-driven positioning this uneven padding forces messy work-arounds. Flattening the shape fixes the offset, but that breaks scalability and makes later edits harder. A small change would solve it: Draw polygons and stars truly centered within their frames or Expose a simple “internal padding” control so we can zero-out that bottom margin. Either option would make these shapes far more dependable for automated and component-based workflows.
Please searDue to my mistake, I increased the number of seats in Figma, I want to reduce it, I only need 10 seats, now it has increased to 17 seats, my annual fee will be updated tomorrow, can anyone tell me How to deal withch for existing topics before posting! Press 🔍 at the upper right to search.🥺🥺🥺
Hello everyone, I’ve stumbled upon a rather frustrating issue when exporting frames to JPG — and I wonder if anyone has experienced the same, or has a clue where to dig. When I export a frame to JPG (doesn’t matter whether it’s @1x, @2x, or @3x), I keep seeing strange artifacts. Specifically: it looks as if some pixels shift places — like tiny glitches — and what’s most odd, they appear in different places depending on the export scale. All positions of my artboard and all the objects inside the frame are aligned to whole numbers (e.g., 2412 instead of 2412.54). I double-checked all coordinates — no fractions hiding anywhere. Yet, the exported JPG shows these random pixel-level misalignments, and it’s making me a little… poetic with frustration. Has anyone else encountered this? Could this be a rendering bug, or am I missing something subtle? Looking forward to your thoughts and wisdom — and may your pixels stay aligned. Thank you! upd. I noticed this problem on Windows, but not on Mac
Recently I got an intrusive notification above the tray and it does not disappear, but always reappears. How to remove it?
Hi, I’m having an issue with the variables. I created a design system with all the relevant variables and then published. I made sure all variables are with the correct scope details and all are NOT hidden from publishing. After enabling that library in a new design file, i tried to use a color variable on a new shape and it simply doesn’t load the colors in the small thumbnail squares. They just stay forever with the default color variable icon. I tested this with new files and new libraries and variables but the issue keeps happening. It seems like it is stuck in a forever loading stage. Other colleagues of mine can use the library and see the variables in their square thumbnails, so im guessing its my issue. After this i made sure my figma was updated and even uninstalled it and installed again. I’ve also tested this with both app and web browser. Interestingly, when i do select a color from the variables on the right panel, the color appears! Has someone had this issue? I’m really
When designing for the web, I often use effects like background blur, blend modes, or advanced layering techniques. However, not all of these are fully supported across all browsers or devices. I’d like to know if Figma has any tools, plugins, or best practices to help flag these kinds of compatibility issues early in the design process — or if this kind of consideration needs to be managed entirely outside of Figma. Any tips or workflows from others dealing with this would be appreciated.
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.