Share Your Thoughts

I was surprised to notice today that the long awaited Connected Projects is now available in Figma but also very disappointed to see the absurd limitations on how many connected projects each plan can have. I can somewhat understand the limitation of being able to connect with one company at a time for technical/admin reasons in the first release, but WHY do we need the limitations of how many connected projects we can have if all parties are already paying for their licenses? The max 3/6 in Professional and Organization is ridiculous, as it also counts the projects that are shared our way. Please remove these artificial limitations, or at least make them a lot bigger like 20 / 40 / 80 so they make some sense in the real world.

When working with multiple shapes, you currently cannot edit the anchor points of multiple shapes at once whether they are unionized or not. At my studio, we are working on incredibly complex UI for vehicles, and products, and this feature would be much appreciated, and would greatly increase the speed of our workflow.

Please vote this up!We really need to be able to drag and position lock annotations and connect to any layer within a nested layer or instance. This has been asked for many times (Examples below) and would eliminate designers time making their own local components and ignoring the use of the built in annotations. and 

I spend far too much time deleting that blurb when all I want to do is point Claude to the correct URL from the MCP. I have better prompts.Either make that bit go away, or let me copy just the URL.

Fundamental to using any digital whiteboard, is being able to hyperink image elements.Please consider adding this to the pipeline! It’s a huge setback to using Figjam and lags behind competitors for a basic requirement. Community, I’m not alone. Please chime in! 🙏

It appears as though the higher resolution a Figma Motion export is, the more compression is applied, which greatly affects color reproduction. Without being able to set a consistent compression, color is constantly changing in exports, which makes the exports unreliable for evaluation and deliverables for production. If the compression is indeed adaptive, targeting a certain bandwidth cost or file size limitation, it's a big flaw in Figma motion exporting. We need a way to maintain the color space consistency in exports.

Hello, I will mention the problem to solve, then I will explain how my idea could solve it. Please vote for it if you need it as well, thanks. 1) The problem to be solved The precise Creation Date of a file is a key information for many users. It is not easy to find, and not available for every plans… Currently, the only way to find it is through the “History version”: The mental model of the user has to be “Thinking: Past version” instead of “Thinking: Metadata of the file”, which is an incoherent mental model for many users. Because, if the creation date is indeed a past version, it is actually the pillar version, not just a past version. This model is incoherent with many users’ habits as well, because a lot of softwares and OS include the Creation Date in basic metadata, often under the same Properties menu than “Author”, “Modified Date”, “Extension”, etc. A Paid Plan is often needed to scroll through many revisions. Though, this basic metadata should be available for every plans.

I have a shape element (a message bubble), I cannot flip it against it’s vertical axis to create a simply dialogue visual for my project. 2 people having a conversation….the message bubble has to be flipped.I don’t understand the logic of principle with building a tool like Figma that is highly precise and detailed, but then building it’s sister app “FigJam” with bare bone features.As designers, I still want the ability to manipulate elements. Why is there only 2 thick levels for lines?This type of experience makes me want to abandon FigJam entirely and make my documentation in Figma original or use a different tool like Miro.I understand and respect wanting to simplify the workspace, but believe you guys have over-optimized in this direction and consequently limiting the creative aspect of designing visual documentation for teams. 

Currently, the only ways to run plugins in Figma are by searching for their names in the plugins section of the actions panel or using their shortcuts in the right panel. I suggest adding the ability to run Figma plugins via a direct link. This would be a significant time-saver for heavy Figma users. For example, I use a Stream Deck for shortcuts, and being able to launch plugins with a link would streamline the process, reducing the effort needed to set up hotkeys or macros for newly used plugins. Thank you.

In Dev Mode, when selecting an image, you can see the original filename of the placed source image and download it by 1) clicking on the name in the layer properties, or 2) in Assets.However, when downloading, a strange filename is suggested that doesn't match what we see in the layer properties.Question 1: Is it possible to fix this so that the source image is downloaded with the original name?Question 2: Is it possible to bring this functionality into the main editing mode? It's sometimes very useful when working with designs, and it's sorely missed.

Designers should be able to define different column counts, gutters, margins, and potentially span values across variable modes or responsive breakpoints. For example, a grid could automatically use 12 columns on large screens, 6 on medium screens, and 4 on small screens.This would bring Figma's Grid Auto Layout closer to how responsive grid systems are implemented in frontend, while allowing designers to maintain a single responsive layout instead of creating separate desktop, tablet, and mobile frames. 

I can’t tell you how many times I’ve spam clicked on frames repeatedly as I’m playing around with my designs. It’s a messy process. Because of that, I would love it if Figma could automatically skip needless parent frames and let me access their child frames so design feels more actionable. The main way I think this could work would be ignoring nested frames (with 0 values, etc). Another potentially-useful addition could be that if you quickly click repeatedly it jumps deeper into nested layers. Maybe users could customize it like a nudge.

When I’m just ideating on a new design and don’t want to use auto-layout yet, it would be really nice if there were a button that allows me to quickly move an object to butt up against another object. Something like the alignment buttons, but I don’t want to align the object to the sides of the frame. 

I would like a feature in Annotations like double click in annotation to zoom to the design piece they are attached to (or some other avenue if double click allows edits for the annotation maker)When I use the shortcut to zoom to the design it often just focuses on the annotation and the screen stays small and it’s somewhat frustrating when I am just trying to show the developer the screen we want to change or what the annotation refers to.

Figma, please add connectors as a standard feature in Figma. I am willing to pay for it as a separate feature.  

My Figma Learning Journey 🎨✨I’m starting my journey of learning Figma and exploring the world of UI/UX design. My goal is to understand the fundamentals of design, improve my creativity, and learn how to create clean, modern, and user-friendly interfaces.Throughout this journey, I’ll be sharing my learning experiences, design experiments, challenges, and progress with the Figma community.I’m excited to learn new skills, connect with fellow designers, get feedback, and grow as a designer one step at a time.Let’s learn, design, experiment, and grow together! 🚀#Figma #LearningJourney #UIDesign #UXDesign #DesignCommunity #FigmaCommunity

Can I edit the variables defined in a published library locally? There is a library file (Say File A) with a collection of local variables defining some string and numbers shown on a component. The component is published (with all variables too) I added this component to another file, say File B, but when I want to edit those strings and numbers locally in this File B, I can no longer see the these variables, nor editing them. Seems like I can only edit the published component in the library File A (if I have edit access) and this will change all the instances too. Can I instead edit it locally, meaning edit the values of these publish variables only in File B?

Hi folks! I’ve seen the posts regarding text overrides with nested interactive components but I’m seeing a similar issue with non-interactive components as well. In the example below, I’ve set my text layers to all use the same layer name and have the same hierarchy structure but if I swap one of the nested components it resets everything. Everything works perfectly if each atom component is used individually and not nested in another component though so I’m left 🤔. Any thoughts?

The Problem: Lost in the Canvas WildernessWhen working on large, sprawling Figma files (especially design systems, deep user flows, or complex prototypes) with hundreds of frames, the canvas becomes a massive workspace.We frequently need to pan or zoom away from our current focus—the frame we are actively designing—to: Reference a component in the design library on the far left. Check colors/styles on the style guide at the bottom. Look at a distant flow branch for context. The pain point: After checking that reference, returning to the active working frame requires slow, tedious, and imprecise manual scrolling/panning, which is a significant flow breaker. This effort grows exponentially with the size of the file.The Proposed Solution: "Go to Working Frame" ShortcutWe need a dedicated keyboard shortcut to instantly snap the viewport back to the frame the user was most recently editing.Implementation Options (Figma-Specific) "Last Active Frame" Shortcut (Simpler): The shortcut (e.

These are new and improved color formats that replace hex and rgb. They will soon become the standard in web browsers. They open up more colors than are currently possible. The Expanding Gamut of Color on the Web | CSS-Tricks - CSS-Tricks

Summary: Add an automatic, togglable "Viewport Fold Line" on extended device frames so stakeholders can instantly see what sits above the fold directly on the canvas—eliminating scroll height confusion during design reviews.The Problem When frame heights are stretched downward to fit long scrolling pages, Product Owners, clients, and non-design stakeholders often mistake the total frame canvas for the initial viewable screen. During reviews, they assume lower content will be immediately visible without scrolling, causing miscommunication around layout priority and above-the-fold real estate.Source of Inspiration Adobe XD solves this natively: when you choose a preset viewport (such as an iPhone or MacBook preset) and stretch the height downward, it automatically displays a dashed horizontal guide marking the original viewport height. This clearly marks the boundary between the default view and scrollable content directly on the working canvas.The Solution Introduce an automatic "Scroll

Thanks for adding annotations to Design Mode. I have been spending the last day annotating some new design ideas. People who have access to the Figma file love that they can read come design rationale and interaction behaviors. For others, who do not have access, or do not use Figma it would be great if I can export the annotations associated with objects inside a frame.  Thanks, K.

Feature Request to Resolve Ongoing Library Problem: Allow Swap Library to Replace Local Variables with Published Library Variables I would like Swap library to support replacing local variables in a file with variables from a published library when the collection structure and variable names match.
Today, Swap library only supports library-to-library swaps, which means local variables cannot be migrated directly to an existing published library.
This creates extra overhead because the workaround is to publish the local variables as a separate library first, only to swap them afterward.
 Since variable replacement by matching names already works within a local file, extending that behavior to local-to-library swaps would make migration to standardized library variables much easier. Example:A file has local variables in a collection called “Module 1 Semantic Theme.” That file also has layers using local variables like “Color / Text / Primary” and “Color / Background / Default.” Your publ

Add richer descriptions to variable collections, groups, and modes Figma currently allows us to add a description and scope to an individual variable. However, the description field is a relatively limited text input, and documentation cannot be added to the broader structures that give variables their meaning.Proposed Description LevelsIt would be helpful to support descriptions at multiple levels of the variable system: Variable collections: Explain the collection’s purpose, intended use, architecture, and relationship to other collections. Variable groups: Document how a specific category of variables should be applied and distinguish it from related groups. Modes: Explain the context represented by each mode, when it should be applied, and any important differences or limitations. Individual variables: Retain variable-specific guidance, but provide a more capable description experience comparable to component documentation. Ideally, these descriptions would support multiline

Hi there, I’m struggling with text boxes which are not trimmed horizontally. I’m trying to create single speech bubble with limited width. When the last word in the line doesn’t fit the bubble goes to maximum width and then jumps to another line. I wish to trim it to the actual text width. Do you know a solution which is not manually set every single bubble?