Share Your Thoughts

Allow offline work on files through the Figma app. This is important because internet connections aren't always available—whether you're commuting, on a long business trip, or working at a client site without connectivity. Work continuity matters. Offline support is standard for professional production tools, even cloud-based ones.

The idea is to have “synchronized sections” (see Notion Synchronized Blocks) →I often need to have the same content in several files (maps, etc.), and synchronized sections would save me from having to maintain them all.  Notion Example:  

Of course it is easy enough to lock layers but I think that it would be helpful to be able to lock pages in a fashion similar to the layers. I often place root (master, main, og?) components on a separate page and it would be nice to be able to lock these pages to keep items from moving around without intention.

While there used to be a Copy to Figma sites button, it seems that this has been deprecated in favour of “send to Figma make”.  I would request for this feature to be added back in, as well as a way to copy an entire figma file into figma sites (rather than creating a new one and adding frames as separate steps)

Within Figma Sites, you are currently unable to provide “navigate to” as a type of interaction. I am aware that you can add a link, however doing so causes an issue if you have the goals ofDoing conditional navigation (i.e. if X== true Navigate to A, Else navigate to B) Changing a variable, and navigating through the same button (e.g. set Y to Z & navigate to C)1 because navigate to/link to is not available in the interactions (where conditional is found) & 2 because if you assign a link, then onclick is removed as a trigger for interactions In terms of both, I accidentally used a workaround by copying a frame from core Figma into Figma sitesHowever, this is not convinient/intended, and I worry that it may create issues with future versions of figma sties.

The corner radius tool is great if you want to make rounded corners but what if I wanted to make sharp, folded or clipped corners like in the shape below?The catch is that when resizing, the scaling and the angle for these corners should stay the same. If you simply create a shape like this, it doesn’t really scale well if adjusting only the height or the width - the angle of the corners suffer. Has anyone figured out a solution to this or is this something Figma could implement perhaps?

I often work across multiple pages within a single Figma file/project, and I’d love the ability to open different pages as separate tabs in the desktop app—just like I can open different files. Currently, I have to either open and close multiple pages many times to get what I need from other pages, use multiple windows or duplicate the file, which isn't ideal for managing design systems or multi-page projects.This would greatly improve workflow efficiency for designers managing large files or working across different sections (e.g., desktop vs. mobile layouts) simultaneously.Please consider adding support for tabbed views of multiple pages within the same file.

ProblemWhen using stroke-based icons inside nested components (e.g. button components), resizing behavior in Figma causes major inconsistencies:• If the icon is a component, it keeps its original size when the parent resizes• If constraints are set to Scale, the icon scales visually but stroke width does not scale, causing icons to appear heavier/darker• The only way to get correct proportional scaling is using Scale tool (K), which does not work with Auto Layout or component resizingThis makes it extremely difficult to build scalable button components using stroke icons.ExpectedResizing a component or instance should optionally behave the same way as Scale (K):• Stroke width scales proportionally• Corner radius and effects scale correctly• Works inside Auto Layout and nested components Proposed solutionAdd a global or per-object option sim

Use case: Once an advanced UI has been built , users want a way to quickly select nested components in order to modify their properties and attributes. In this stage of design, designers are less interested in manipulating sub-elements of a component, and more interested in selecting the component itself to modify properties and variables. Current challenges: the deep-select modifier (CMD/CTRL) is currently the most efficient way to access deeply nested items, however it is fairly indiscriminate and will often select the deepest nested element under the cursor. With complex components this often means a graphical element like a frame or a text element, requiring the user to step out of the hierarchy, often a number of steps, before arriving on the parent component, or they must use the mouse to then select the parent component from the Design properties panel. Recommendation / Request: Provide an optional modifier key to be used while deep-selecting to restrict sel

ProblemThere's no plugin or REST API that exposes a fresh view of which team libraries are currently subscribed to by a file. After a user adds or removes a library mid-session, every documented and undocumented signal continues to report the prior subscription state until the file is reloaded. This makes it impossible to write a plugin that correctly classifies orphan references (variables, styles, components from libraries no longer linked to the file) without asking the user to reload Figma after every library change.Use caseWe're building a plugin that scans a file for orphan references — bindings to variables/styles/components from libraries that aren't subscribed by the file. The orphan signal we use today is figma.teamLibrary.getAvailableLibraryVariableCollectionsAsync(): any remote collection whose key isn't in that response is classified as orphan. This works perfectly when the cache is fresh (after file load), but breaks s

Enhancing variables to have extra logic in place so that variables can be partially based off other variables e.g. Number new_variable = “{other_number_variable} + 4” String new_variable = “{other_text_variable} New Text” Colour new_variable = “{other_color_variable}, opacity 4” Boolean new_variable = “not {other_boolean_variable}”

I work for both desktop and mobile screens and I would like to save custom frame sizes and have them under a custom category. basic desktop sizes like 1366x768 is not available in the presets and the desktop category only has Mac screen devices as options.

Allow the users can move the new toolbar through the canvas, that today is fixed underneath the page. I liked the new version but I believe some extra flexibility on it would be welcome.

Figma is the most intuitive tool I have ever used and I would love for Figma to expand into web development! Publishing a website directly from Figma would be incredible!

When adding components to a Slot and attempting to surface nested properties I see a message that nested properties can not be surfaced with Slots. This severly limits their usefulness to us since we are creating multiple composable components using sub components with properties and having to drill in to each instance in a multi-item Slot is very time-consuming.

Just a thought, but the effect property in the annotation is very vertical. In general, when using variables/tokens, why are they not displayed in the annotation? Dev-team is referring to the token instead of the raw value. 

It would be great if I could use my right mouse button to drag the page like you can do in Miro. 

Hello,I’m really excited about being able to use AI to edit our app screens. It would make important stakeholders able to work by their own.However, for now, the results I get are far from being usable.First, despite the announcement, I have no icon related to this… strange.But it’s accessible through the cmd-k menu → “first draft” or “make a change”My first “first draft” was a banger. With only a vague prompt, it created a neat design with nice architecture (better than those of most of designers I’ve worked with ;-) )But as soon as I use the “make a change” menu, which is where the work begins, it’s really bad. Most of the time it doesn’t stick to the selection I gave and change something else. It doesn’t understand some basic command (selecting a menu, I just ask to add 2 entries… it renamed the others and change the colors...).So, am I missing or mis-using something? Do you have similar experiences or much better?Peace

I cannot understand the following. Figma Make makes a destructive mistake and uses credits. It then uses additional credits to fix the mistake it made. If it applies the wrong “fix”, it uses even more credits to address the issue. If it recognizes it’s addressing an issue caused by the AI, why does it continue charging a user to address the problem. This is my hugest pain point with this product and pricing model.

Since a couple of weeks Figma Buzz is auto-naming the frames it creates when BULK CREATEing. It simply adds 10 (or something) characters from each CSV-Tag and pastes them in.Please add the possibility to deactivate this feature. It messes with our current workflow and forces us to add additional steps. Would also be nice to be able to fine tune this to our needs (i.e. choose what tags should be used)Also: there seems to be no documentation in terms of release-notes for this.

As a user I want the text to auto-adjust: in this way I can write sticky notes different in length (without breaking them in height).

As described in the title, links are broken as soon as you cut a frame and paste it elsewhere (on the same page, in the same file).How to reproduce this issue:Copy the link to any selected frame Save the copied link somewhere Cut the previously selected frame and paste it elsewhere (same file, same page) Open the saved link The link no longer leads to the frameSuggested solution: When a frame is cut and pasted, the associated link ID should not be lost.

A lot of AI features in Figma so far seem to be generative, which IMO is mostly fruitless for the core auidence as current models are not capable of new problem solving, only generating variations of the combined knowledge of everything that has been observed before, without understanding the context of decisions made to implement design choices as well. Where I can see see value add is in other aras. QA for example - perhaps pointing a dev URL at the tool to see how front-end have developed the designs and comparing to what was in the original figma (visually, not comapring the code generated by Figma, which is often not all that helpful in established systems) - could help catch mistakes and also documwent intentional changes in the design to development process. 

The experience of Move to Page can be frustrating and inefficient. That's because when a user moves a frame/section to another page:there is no immediate feedback to where the element was placed user must manually go to the page and search for the moved element often, the element is placed using the same absolute coordinates, and that can result in it being placed on top of other elementsThis creates unnecessary hassle, especially in large files with many sections, frames and components. I can think in 3 possible solutions for this problem, I hope my suggestions can help y'all (and myself!):Auto-navigate after moving: after using Move to Page, automatically switch to the destination page and bring the moved frame into view, allowing the user to immediately position it (similar behavior in Apple Finder). Smart plac

Can somebody explain to me what is the point in having multiple stroke layers when they:SHare the same size Share the same offsetAnd another question is is there any way of doing offset to a stroke or drop shadow? I really need this for our focused state in our design system and what I found was only wanky workarounds...