Share Your Thoughts

The Check designs tool is really useful but I have one big problem with it. In some cases I have used items or colors outside the design system by intention, (annotations or information to the developer or business as the built in annotation is not visible for all). I would need to be able to ignore some design suggestions. Right now I can not use the check design function as only some of the suggestions actually applies. So, my suggestion is to either be able to ignore suggestions that aren’t correct or select those that you want to apply.

User groups in the admin panel currently get an auto-assigned icon (a generic people silhouette) and a randomly assigned background color. It would be great to have the option to customize both, similar to how workspaces already support custom icons and colors. Why it would help:- Makes groups easier to identify at a glance, especially for orgs with lots of groups- Lets teams align group visuals with their internal branding or team identity (e.g. a "Design" group with a design-related icon, a client team with the client's brand color)- Reduces the confusion of having group names and colors feel disconnected (a "Blue Team" showing up with a green icon, for example)

Hi Figma developers! It turns out that exporting Figma fonts in JSON format provides the result that looks smth like this: "style": { "fontFamily": "Quattrocento Sans", "fontPostScriptName": "QuattrocentoSans-BoldItalic", "fontSize": 72, "fontWeight": 700, "italic": true, "letterSpacing": 0, "lineHeightPercent": 100, "lineHeightPx": 84.375, "lineHeightUnit": "INTRINSIC_%", "textAlignHorizontal": "CENTER", "textAlignVertical": "CENTER" }, for a page like this: And we face the necessity to invent some special algorithms for knowing the actual style name (that is “Bold Italic” in the ex

Here’s the translation of your text into English: "The page and layer separators need improvement. Even though I create a lot of pages, every time the client wants to review the designs, they don’t realize that more pages have been created below. For example, maybe a slight fade effect could be added to the bottom of the pages to indicate that there are more pages below. Additionally, the separator between pages and the separator between pages and layers look very similar, making them hard to distinguish from one another."

I’ve run into a limitation with auto layout when working with components that use slots.Currently, the auto layout direction (horizontal/vertical) defined in the main component seems to be locked for any instances. When content is placed into a slot, it inherits that direction and there’s no way to override it locally at the instance level.This becomes restrictive in cases where the same structural component needs to adapt to slightly different layout contexts.Is there a technical reason why auto layout direction is fixed this way? For example, is it tied to how slots are implemented under the hood or how layout calculations propagate from the main component?It would be very useful to allow overriding the auto layout direction per slot.

hey Figma fam, so, we’ve been going on about this for ages, but seriously, when are we getting the “lock guides” feature? it’s 2024, and we’re still nudging guides by mistake 🙄 we all know the drill - you’re in the zone, designing away, and then oops, there goes your guide. it’s like playing a game of ‘spot the difference’ trying to get it back in place. super annoying. i mean, how many times do we need to ask, right? it’s a no-brainer feature that would make our lives so much easier. locked guides = no more accidental shifts. simple. let’s give it another shot. maybe if we all shout about it (again), Figma will finally listen and add it to their to-do list. who’s with me? catch ya later! flo

With the new beta introducing AI and the left rail, move the help fob in that left rail, and get it out of the way of the properties right panel.

Hi! I upgraded my Figma account from using the free version to the basic plan. Since I did that I can no longer switch to design mode when I could do that with my free account. Please can someone fix this asap. Otherwise I will downgrade my account.

Hello everyone at Figma, could you please fix very small alignment/sizing issue? because it just might make me blind.Thank you in advance.

Hi Figma, please add a feature where users can create a special type of frame within a component, so they can create instances of the component and then magically insert other instances or content into the special frame placement. Swapping instances works if we need to change one instance to another instance, but it is very limiting and essentially cripples Figma’s drag-n-drop design mentality. This feature would open up a world of opportunity for design systems to be much more scalable and effective.

I know UI change takes time to get used to, but I am desperately missing the previous Files/Assets setup in the lefthand nav (pictured below). There is an agent trigger on every single frame on my workspace...I really don’t need a dedicated lefthand nav option for it as well. I don’t need Agents often enough to justify it being the second item in my lefthand nav, in addition to being on every single frame. What I do need, multiple times a day, every single day, is my assets panel.  

Hi everyone, I’m a teacher using Figma in a design class. We’re currently working on retro-engineering design prompts. For example, “design Spotify on Game Boy Classic”. The “pixel preview” option is perfect for that while in design mode, however, it doesn’t seem to be available on prototypes. This is 1980, we don’t want super smooth x4 retina anti-aliasing here! Any idea how to enable “pixel preview” in prototype mode? Thanks so much in advance!

I’m having trouble exporting PDFs of frames. Do you know if the export functionality embeds the fonts? I will import the generated pdf frame into another work that requires to be PDF/A compliant, so I need the font embedded in the frame in the first place. I tried with Adobe Reader, and it does not say “embedded”, which is usually a sign that it’s not. I tried with another software (Okular), and it does say “fully embedded”.

When sharing, I would love to be able to specify a specific slide to link to. This will allow more fine tune sharing. If the url was appended with something like “slide-1” it would allow for us to create dynamic and easily editable links in our Airtable as well. We are using slides as a creative review workflow and this would help us tremendously!

Hi Figma team, I’d love to see more ways to organize tabs in Figma desktop app. I often have 10–15 tabs open, but I’m usually only actively working in 1–2 files and frequently jumping into a few design systems. The rest of the tabs are useful, but mostly for quickly checking something. When many tabs are open, it becomes hard to find the files I actually use all the time. It would be great to have more control over tabs — for example, pinning important files, marking current working files, grouping tabs, or showing design systems as compact icons instead of regular full-width tabs. Right now tabs feel a bit like browser tabs: they are just open, but I can’t really organize them around my workflow. Some simple customization would make it much easier to navigate between active files, design systems, and reference files. Thanks!

If it’s not broken, don’t fix it. The recent change that places component variables above X/Y and H/W settings, though well-intentioned, creates friction for users dealing with complex components and multiple variants. This shift results in vital inputs being moved around, and their location becomes inconsistent based on the number of variants. As someone who frequently optimizes design systems, I often manage components with up to 12 settings, including both the component and its children. I use X/Y and H/W inputs 3-5 times more frequently than I touch variants, making this new arrangement inefficient for my workflow. Returning to the previous, consistent logic would greatly improve usability. After all, consistency is key in design, and it’s especially important in a tool meant to empower designers.

   First of all, the new Chrome extension is amazing. One issue I've run into is with popups, dropdowns, notifications, tooltips, and other UI elements that disappear when you click elsewhere on the page.For example, I'll open a dropdown menu or notification panel that I want to capture, but as soon as I click the Figma extension's capture button, the popup closes before the capture is taken. This makes it difficult to capture many common UI states that are important when recreating or analyzing interfaces.It would be great if the extension could support something like:A keyboard shortcut to trigger capture A short capture timer (e.g., capture in 3–5 seconds) A way to freeze the current page state before capturing

We often need multiple versions of a single design that just have a different images. To do this in bulk in Figma Buzz currently, we would need to add the images to a spreadsheet, export to .xlsx and upload to Buzz. This is not faster than just adding each image to a Figma design.We would like to see added functionality built into Figma Buzz so that we can upload multiple images at once in the ‘bulk create’ section in order to create multiple iterations of the same design just with different images.We can see this working for designs that require multiple images as well – in the same way that Buzz allows us to assign columns of a spreadsheet to elements of a design, each image in a design could have its own multi-image upload button.This would speed up SO many tedious tasks!

Every time I open a file, comments are visible and I have to hide them manually with Shift+C. There's no way to set this once and forget it. A simple toggle in account preferences — just like the light/dark theme switch — would be perfect. Set it once, and comments stay hidden by default across all files.Also, visible comments noticeably slow things down, especially on older machines. Hiding them by default would make Figma feel much snappier day-to-day.

Figma, you guys are really cooking with the AI features. It's making workflow really, really special and I've been waiting for this moment for a long time. As I'm using it though, I'm seeing that there are some bottlenecks. I have a couple of ideas. I have a simple idea and a more complex one maybe for the future. The first one is simply just a prompt history where after you generate an image, you can see somewhere the original prompt that you used to generate that image. Many times when I need to iterate on a generation and I go back to edit the prompt, I can't find the prompt anywhere. I’ve started to copy the prompts that I write out and paste them into a text box every time I generate an image because I don't want to lose the prompt. I feel like it's a simple thing that would really improve the workflow. The second idea, and this one is a little bit more complex, but I think it's right in line with what you're moving towards, is prompt components with variables. So just like we hav

Figma once tried a Minimalist or hovering left & right panels in a beta version and then rolled it back. I loved the sensation of it because, sometimes, I feel trapped in the square of the canvas, and that layout made it feel freer while working. Yes, you can hide the UI, but you will need to show it again every time you need to click on a page/layer and edit something with the right panel. If people didn’t like it, make it optional, so we can decide our preference, as simple as that.

ProblemSlots are a powerful way to make components flexible, but today they are too open. Even when using Preferred Instances, designers can still insert any component or element into a slot. This flexibility often leads to misuse and breaks design system consistency—especially in large teams.Example:A Button component has an Icon slot.We want designers to use only approved icon components, but currently they can insert:Any other component Any vector or frame Any custom elementThis results in inconsistent UI, broken behavior, and extra review overhead for design system teams.Proposed FeatureAdd an option to restrict slot content to specific components or component sets.When creating or editing a slot, allow authors to:Define a restricted list of allowed components / component sets Prevent adding any elements outside this list Optionally show an error or warning when invalid content is attemptedHow this differs from Preferred InstancesPreferred Instances → Suggests what should be used R

When you delete an element in a nested structure, you lose all selection. This means if you want to continue working around that level, you have go dive again to that level (double-click, double click, double, click, double click…) Deleting an element should auto select the immediate upper level to stay where we’re currently working Or auto select the previous element in that hierarchy maybe, or the next one. But staying around there, not going back to root level.

Title: Figma Make GitHub connection flow does not clearly indicate organization-wide repository accessDescription:When connecting GitHub to Figma Make, the setup flow does not clearly communicate that the GitHub integration operates at the organization level and that repositories may be shared across users within the organization.As a result, repositories can receive content from other organization members' Figma Make projects, even when those projects are unrelated to the repository owner. Steps to Reproduce: Connect GitHub to Figma Make. Select a repository during setup. Create or work on projects within Figma Make. Observe content being pushed or appearing in the selected repository from projects created by other users in the same organization. Expected Behavior: The setup flow should explicitly state that the GitHub connection is organization-wide. Users should be informed that other organization members may be able to push content to the selected repository. Repository o

Chad Bergman announced in November 2025, during the Schema by Figma 2025, that the Figma tokens export is “completely aligned with the design tokens specification.” However, we later discovered that most composite tokens such as typography, gradients, and shadows are not yet supported, despite being in the stable revision of the specification in Design Tokens Format Module 2025.10.No clear future plans or roadmap for the export feature were communicated during the conference, which leads us to believe that we won’t receive any updates until the next keynote.Is support for composite token export planned in the near future, or do we have to stick to third-party plugins for now to obtain production-ready design token exports?